alknet/tasks/architecture/spec-storage.md at 84f16d66e79e19dbdbddb9e25bbb3254ef0be760 - alknet - Gitea: Git with a cup of tea

alkdev/alknet

Files

glm-5.1 84f16d66e7 tasks: decompose Phase 0b spec documents and Phase 0c review

Add 15 new tasks under tasks/architecture/ for Phase 0b (spec writing)
and Phase 0c (review):

Phase 0b — New specs (6):
  - spec-configuration: promote from research, cleanup, align with ADRs
  - spec-identity: carry from auth.md + services.md, canonical Identity
  - spec-secret-service: from research/services.md SecretProtocol
  - spec-storage: from research/storage.md, contract-level
  - spec-flowgraph: from research/flow.md, pure computation crate
  - spec-interface: new Layer 2 spec (highest risk new spec)
  - spec-services: irpc service layer + OperationEnv (broadest scope)

Phase 0b — Spec updates (6):
  - spec-update-overview: add crate structure, Layer 3, services
  - spec-update-auth: IdentityProvider vs AuthService relationship
  - spec-update-call-protocol: OperationEnv dispatch paths
  - spec-update-server: DynamicConfig, ForwardingPolicy, IdentityProvider
  - spec-update-napi: reload API, call protocol references
  - spec-update-open-questions: resolve OQs per ADR decisions

Phase 0b — Assembly (1):
  - spec-update-readme: add new docs and ADRs to tables

Phase 0c — Review (1):
  - review-spec-foundation: validate consistency checklist

Generation structure (6 total):
  Gen 1: 6 independent ADRs (parallel)
  Gen 2: adr-027, adr-028 (depend on adr-029)
  Gen 3: adr-033 + 6 spec docs + open-questions update (parallel)
  Gen 4: adr review + interface/services specs + 4 spec updates
  Gen 5: call-protocol update + readme update
  Gen 6: spec review

2026-06-07 09:01:01 +00:00

2.9 KiB

Raw Blame History

id, name, status, depends_on, scope, risk, impact, level

id

name

status

depends_on

scope

risk

impact

level

architecture/spec-storage

Create storage.md architecture spec (or stub referencing crate docs)

pending

architecture/adr-027-crate-decomposition

architecture/adr-029-identity-core-type

architecture/adr-032-event-boundary-discipline

moderate

low

component

implementation

Description

Create docs/architecture/storage.md — an architecture spec for the alknet-storage crate, covering the metagraph data model, identity tables, ACL graph, honker integration, and StorageProtocol irpc service.

The integration plan notes this could be "a new spec or reference alknet-storage's own docs." Since alknet-storage doesn't exist yet as a crate, we need an architecture spec here to define its contract — especially the interface back to core (StorageIdentityProvider implementing alknet-core's IdentityProvider trait).

If the crate will have its own detailed docs later, this spec can be a contract-level document: what storage provides, what it depends on, and how it connects to core.

Source: docs/research/storage.md (460 lines, comprehensive)

Acceptance Criteria

docs/architecture/storage.md exists with YAML frontmatter (status: draft)
Follows spec format: What, Why, Architecture, Constraints, Open Questions, Design Decisions
Documents metagraph data model: GraphType, NodeType, EdgeType, Graph, Node, Edge
Documents identity tables: accounts, organizations, peer_credentials, api_keys, audit_logs
Documents ACL as metagraph: PrincipalNode, DelegatesEdge, access control graph
Documents encrypted node type: bridges to alknet-secret's EncryptedData format
Documents honker integration: stream_publish/subscribe, notify/listen, queue/claim
Documents System DB vs Tenant DB separation
Documents StorageIdentityProvider: implements alknet-core's IdentityProvider trait (queries peer_credentials + ACL graph) per ADR-029
Documents StorageProtocol irpc service with key variants
States crate dependencies: rusqlite, honker, petgraph, jsonschema, irpc
States crate does NOT depend on alknet-core (implements core's trait by depending on alknet-core types, not the full crate — or via the trait definition only)
Event boundary per ADR-032: honker streams stay within storage service, StorageProtocol serves as internal boundary, call protocol events are projections
References ADR-027, ADR-029, ADR-032
docs/architecture/README.md updated to include storage.md

References

docs/research/storage.md — full metagraph, identity, ACL, honker definitions
docs/research/integration-plan.md — Phase 2.2 (alknet-storage)
docs/architecture/decisions/027-crate-decomposition.md
docs/architecture/decisions/029-identity-core-type.md

Notes

To be filled by implementation agent

Summary

To be filled on completion