- 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.1 KiB
1.1 KiB
id, name, status, depends_on, scope, risk, impact, level, tags
| id | name | status | depends_on | scope | risk | impact | level | tags | ||
|---|---|---|---|---|---|---|---|---|---|---|
| architecture/oq-13-alkfs-sftp | OQ-13 tracker — alkfs landed (sftp implementation unblocks) | pending | single | trivial | isolated | research |
|
Description
External-trigger tracker for OQ-13 — the sftp feature's implementation waits for alkfs (family ADR-002, paused for alkforge). The sftp feature ships declining (tested decline contract on both directions) until this unblocks.
Work
Transition check only: when alkfs reaches an implementation-ready state (its spec/implementation exists), mark this task completed and move OQ-13 to open for the sftp mapping design (client+server halves; alkforge CI artifact deploy is the consumer).
Verification
- OQ-13 status in
open-questions.mdmatches this task's state. - The
sftpdecline contract remains tested until that point.
References
docs/architecture/open-questions.md(Theme E)docs/research/reverse-runner.md(the deploy use case evidence)
Out of scope
Any sftp mapping design.
Summary
Filled on completion.