- decisions/001: pins alk/ssh to one contract — raw vanilla-SSH byte stream, endpoint = SshAdapter::handle; payload-blind relay restated per alkcall ADR-042; phase 1 serves edge termination only; relay/ browser legs stay compatible by construction (consumers deferred, OQ-01). Status Proposed — ledger-rule-1 acceptance pending review. - open-questions.md: 13 OQs seeded from POC findings (3 resolved by evidence: username disposition, vault role split, reconnect policy; 4 deferred with blockers: relay consumer, cert auth, env allowlist, sftp/alkfs); deferred/failed trackers filed under tasks/architecture/ for each deferred(scope) OQ (taskgraph validate: 4/4 valid) - README.md index: current state, doc table, planned docs, lifecycle
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-01-relay-leg-consumer | OQ-01 tracker — alk/ssh relay/browser-leg consumer | pending | single | trivial | isolated | research |
|
Description
External-trigger tracker for OQ-01 — "does an alk/ssh relay/browser-leg consumer emerge?" (deferred(scope)). Not actionable work; tracks whether the unblocking condition has arrived.
Work
Transition check only: when a concrete consumer use case exists — a browser-WASM route landing in an assembly (alkcall ADR-009 sketch) or a hub deployment needing SSH-in-relay — mark this task completed and move OQ-01 from deferred(scope) to open in open-questions.md (directly to resolved if no decision remains, which would be an ADR-001 amendment since the pin is one-way).
Verification
- OQ-01 status in
open-questions.mdmatches this task's state.
References
docs/architecture/decisions/001-alkssh-alpn-pin.mddocs/architecture/open-questions.md(Theme A)
Out of scope
Any actual relay/browser-leg design — that work would be new ADR/spec territory once the use case exists.
Summary
Filled on completion.