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
This commit is contained in:
54
tasks/architecture/spec-update-overview.md
Normal file
54
tasks/architecture/spec-update-overview.md
Normal file
@@ -0,0 +1,54 @@
|
||||
---
|
||||
id: architecture/spec-update-overview
|
||||
name: Update overview.md — add crate structure, Layer 3, services, identity
|
||||
status: pending
|
||||
depends_on:
|
||||
- architecture/adr-027-crate-decomposition
|
||||
- architecture/adr-026-transport-interface-separation
|
||||
- architecture/adr-033-operationenv-irpc-call-protocol
|
||||
- architecture/adr-029-identity-core-type
|
||||
scope: moderate
|
||||
risk: low
|
||||
impact: project
|
||||
level: implementation
|
||||
---
|
||||
|
||||
## Description
|
||||
|
||||
Update `docs/architecture/overview.md` to reflect the expanded scope from the integration plan. The current overview documents the alpha scope (SSH tunneling). It needs additions for:
|
||||
|
||||
1. **Crate structure** — alknet-core, alknet-secret, alknet-storage, alknet-flowgraph, alknet-napi, alknet (CLI). Per ADR-027.
|
||||
2. **Three-layer model** — Transport (Layer 1), Interface (Layer 2), Protocol (Layer 3). SSH is an interface, not a transport. Per ADR-026.
|
||||
3. **Service layer concept** — irpc services for in-cluster communication, OperationEnv for composition. Per ADR-033.
|
||||
4. **Identity as core type** — Identity struct and IdentityProvider trait in alknet-core. Per ADR-029.
|
||||
5. **Updated dependency table** — new dependencies (irpc feature-gated, bip39, rusqlite, honker, petgraph, jsonschema)
|
||||
6. **Updated ADR table** — add ADRs 026-034
|
||||
7. **Updated architecture constraints** — add: Interface as Layer 2, OperationEnv as universal composition, event boundary discipline, static/dynamic config split
|
||||
|
||||
The existing content (purpose, SSH tunneling, transport pluggability, etc.) stays. We're adding, not replacing.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] Crate structure section added: the six crates and their brief descriptions per ADR-027
|
||||
- [ ] Three-layer model mentioned in architecture constraints per ADR-026
|
||||
- [ ] Service layer concept mentioned: irpc + OperationEnv per ADR-033
|
||||
- [ ] Identity and IdentityProvider mentioned as core types per ADR-029
|
||||
- [ ] Updated dependency table with new crate dependencies
|
||||
- [ ] ADR table updated: ADRs 026-034 added with correct titles and status
|
||||
- [ ] Architecture constraints updated: add Layer 2 interface concept, OperationEnv, event boundary, static/dynamic config
|
||||
- [ ] All new references to architecture specs link correctly (identity.md, services.md, interface.md, configuration.md, etc. — even if those specs are still being written)
|
||||
- [ ] `last_updated` in YAML frontmatter updated
|
||||
- [ ] No hub/spoke terminology remains
|
||||
|
||||
## References
|
||||
|
||||
- docs/research/integration-plan.md — expanded scope, dependency graph
|
||||
- docs/architecture/overview.md — current content to update
|
||||
|
||||
## Notes
|
||||
|
||||
> To be filled by implementation agent
|
||||
|
||||
## Summary
|
||||
|
||||
> To be filled on completion
|
||||
Reference in New Issue
Block a user