glm-5.1
84f16d66e7
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
2.2 KiB
2.2 KiB
id, name, status, depends_on, scope, risk, impact, level
| id | name | status | depends_on | scope | risk | impact | level | |
|---|---|---|---|---|---|---|---|---|
| architecture/spec-flowgraph | Create flowgraph.md architecture spec (or stub referencing crate docs) | pending |
|
narrow | low | component | implementation |
Description
Create docs/architecture/flowgraph.md — an architecture spec for the alknet-flowgraph crate, covering FlowGraph<N,E>, operation graph construction, call graph population, and type compatibility checking.
Like storage.md, this can be a contract-level document if the crate will have its own docs later. The key contract point: OperationSpec and CallNodeAttrs types must match alknet-core's definitions, with serialization as the bridge.
Source: docs/research/flow.md (472 lines, straightforward port of TypeScript design)
This is the lowest-risk new spec — pure computation crate, no I/O, no external state, straightforward petgraph port.
Acceptance Criteria
docs/architecture/flowgraph.mdexists with YAML frontmatter (status: draft)- Follows spec format: What, Why, Architecture, Constraints, Open Questions, Design Decisions
- Documents
FlowGraph<N, E>generic graph overpetgraph::DiGraph - Documents
NodeAttributes/EdgeAttributestraits - Documents operation graph construction from
OperationSpecs - Documents call graph population from
EventEnvelopeevents - Documents type compatibility checking (jsonschema)
- Documents cycle detection, topological sort, reachability queries
- Documents serde serialization/deserialization
- States crate dependencies: petgraph, serde, serde_json, jsonschema, thiserror
- States crate does NOT depend on alknet-core, alknet-storage, or alknet-secret
- States interface back to core: OperationSpec and CallNodeAttrs types match alknet-core's definitions; bridge is serialization
- References ADR-027
docs/architecture/README.mdupdated to include flowgraph.md
References
- docs/research/flow.md — full FlowGraph, operation graph, call graph design
- docs/research/integration-plan.md — Phase 2.3 (alknet-flowgraph)
- docs/architecture/decisions/027-crate-decomposition.md
Notes
To be filled by implementation agent
Summary
To be filled on completion