Architecture documentation structure per sdd_process phase 1: - README index (doc table, ADR table, lifecycle), overview with crate map, dependency rules, and security invariants - Component specs: storage, transport, http, ssh, alkgitd (all draft) - ADRs 001-009: crate decomposition, front-door-blind core, V2-first protocol, pack pipeline (data::output generation / data::input ingestion), session substrate types, http adapter composition (proposed, OQ-01), ACL-before-advertisement, registry-resolved repo identity, bounded-resources budgets - open-questions.md: OQ-01..08 with two deferred(scope), one deferred(unclear), door-type definitions, blocker tracker tasks in tasks/architecture/ - v1 ssh-door decision recorded: russh terminates wire SSH in alkgitd; alkcall channels stay the internal substrate (OQ-03 partially resolved) Two review rounds (fresh-context subagent): 4 critical + 17 warnings fixed in round one; zero critical + 4 warnings + 5 suggestions fixed in round two. All ADR/OQ cross-references verified resolving.
1.2 KiB
1.2 KiB
id, name, status, depends_on, scope, risk, impact, level, tags
| id | name | status | depends_on | scope | risk | impact | level | tags | ||
|---|---|---|---|---|---|---|---|---|---|---|
| architecture/oq-04-receive-pack | OQ-04 unblock — receive-pack walkthrough/POC arrives | pending | narrow | trivial | component | research |
|
Description
Tracker for OQ-04 (deferred(unclear)): receive-pack (push) design
validation. This task is not actionable work — it tracks whether the
investigation has arrived. When a receive-pack design walkthrough (against
real git push captures) or a validation push POC is scheduled, mark this
completed; OQ-04 transitions to open. The investigation scope is in
docs/architecture/open-questions.md (OQ-04): capability advertisement
set, request-line parsing + shallow policy, thin-pack acceptance, CAS
timing, status report, http framing.
Work
None by default. On trigger: set OQ-04 to open in
docs/architecture/open-questions.md and spawn the focused session that
works through the push state machine.
Verification
- OQ-04 status matches this task's state in
docs/architecture/open-questions.md.
Out of scope
- Actually designing/implementing receive-pack (that is the follow-on session's work).
Summary
Filled on completion.