Renames the written-usage rule into practice across the contract surface: docs/ (architecture, research, plans, sdd), tasks/ (all 43 task files, taskgraph validate passes), AGENTS.md, README.md, CHANGELOG.md, and the .opencode/agents/ prompts. Every replacement is a sense-preserving rewrite (colons, semicolons, commas, parentheses, sentence splits, varied), never a mechanical swap; no spaced hyphens were substituted. Enum fields, frontmatter, tables, wire data, and cited identifiers survive verbatim; en dashes inside numeric ranges keep their meaning. Verification: taskgraph validate (43 tasks), repo grep clean (single exempt hit: the verification command's own search pattern in AGENTS.md), cargo test, clippy --all-targets -D warnings, fmt --check, doc all green.
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; it tracks whether the unblocking condition has arrived.
Work
Transition check only: when a concrete consumer use case exists, either 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.