- 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
1002 B
1002 B
id, name, status, depends_on, scope, risk, impact, level, tags
| id | name | status | depends_on | scope | risk | impact | level | tags | ||
|---|---|---|---|---|---|---|---|---|---|---|
| architecture/oq-04-openssh-cert-auth | OQ-04 tracker — OpenSSH certificate auth use case | pending | single | trivial | isolated | research |
|
Description
External-trigger tracker for OQ-04 — whether an OpenSSH-CA-trust use case ever arrives for auth_openssh_certificate (deferred(scope)). Not actionable work; decline is the standing disposition (ADR-004 territory).
Work
Transition check only: when a consuming assembly presents a concrete CA-issued-certificate requirement, mark this task completed and move OQ-04 to open for a design pass (the decline disposition itself would be revisited by ADR amendment).
Verification
- OQ-04 status in
open-questions.mdmatches this task's state.
References
docs/architecture/open-questions.md(Theme B)
Out of scope
Any certificate-auth design.
Summary
Filled on completion.