Files
glm-5.3-flash 8f73da5d12 docs(architecture): phase 1 bootstrap — specs, 9 ADRs, OQ tracker
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.
2026-09-21 03:55:33 +00:00

34 lines
693 B
Markdown

---
id: architecture/oq-05-sha256
name: OQ-05 unblock — sha256 ecosystem need arrives
status: pending
depends_on: []
scope: narrow
risk: trivial
impact: component
level: research
tags: [external-trigger, deferred-oq]
---
## Description
Tracker for OQ-05 (`deferred(scope)`): sha256 support policy. Not
actionable work — tracks whether ecosystem need arrives (a real
client/repo requiring sha256, or upstream gix sha256 maturity worth
testing). On trigger: mark completed, OQ-05 transitions to `open`.
## Work
None by default.
## Verification
- OQ-05 status matches `docs/architecture/open-questions.md`.
## Out of scope
- sha256 implementation.
## Summary
> Filled on completion.