docs: tighten deployment runbooks
Some checks failed
CI / fmt, clippy, docs (push) Failing after 5s
CI / test (ubuntu-latest) (push) Failing after 5s
CI / test (macos-latest) (push) Has been cancelled
CI / test (windows-latest) (push) Has been cancelled
CI / iroh integration smoke tests (push) Has been cancelled
Security / RustSec cargo-audit (push) Has been cancelled
CodeQL / Analyze Rust (push) Has been cancelled
Some checks failed
CI / fmt, clippy, docs (push) Failing after 5s
CI / test (ubuntu-latest) (push) Failing after 5s
CI / test (macos-latest) (push) Has been cancelled
CI / test (windows-latest) (push) Has been cancelled
CI / iroh integration smoke tests (push) Has been cancelled
Security / RustSec cargo-audit (push) Has been cancelled
CodeQL / Analyze Rust (push) Has been cancelled
This commit is contained in:
parent
0efeabb225
commit
0595b39532
4 changed files with 128 additions and 13 deletions
|
|
@ -1,7 +1,10 @@
|
|||
# Roadmap
|
||||
|
||||
This roadmap is intended to be checkable. Each item should either be completed
|
||||
with tests/docs or split into smaller items before implementation.
|
||||
This is the long-term product and feature roadmap. It is intentionally broader
|
||||
than the pre-deployment hardening effort, so unchecked items here do not imply
|
||||
that a completed production-readiness phase has regressed. Each item should
|
||||
either be completed with tests/docs or split into smaller items before
|
||||
implementation.
|
||||
|
||||
Status markers:
|
||||
|
||||
|
|
@ -93,10 +96,11 @@ admin devices without depending on one always-online coordination server.
|
|||
equivalent to Keyhive/BeeKEM, WireGuard, NetBird, or Tailscale unless those
|
||||
properties are actually implemented and tested.
|
||||
|
||||
## Prototype Viability Closure Plan
|
||||
## Initial Viability Closure Plan
|
||||
|
||||
These are the remaining gaps that must close before the prototype is a smooth
|
||||
end-to-end test target for the intended personal mesh use cases.
|
||||
These items established a smooth end-to-end test target for the intended
|
||||
personal mesh use cases. The cross-cutting pre-deployment requirements and the
|
||||
remaining real-machine gate are tracked in the production-readiness roadmap.
|
||||
|
||||
Implementation order:
|
||||
|
||||
|
|
@ -168,7 +172,7 @@ Implementation order:
|
|||
- `[x]` Tests assert conflicting replicated keychain/auth records do not
|
||||
mutate local trust or resource state.
|
||||
|
||||
- `[~]` Remote authorization enforcement audit.
|
||||
- `[x]` Remote authorization enforcement audit.
|
||||
Acceptance criteria:
|
||||
- `[x]` Every remote mutable operation has an explicit resource capability
|
||||
check before mutating local state or opening a host service, or is
|
||||
|
|
@ -176,7 +180,7 @@ Implementation order:
|
|||
- `[x]` A test-backed remote guard matrix documents the expected guard for
|
||||
each remote operation and fails if mutating/service-opening operations rely
|
||||
on discovery alone.
|
||||
- `[ ]` Tests cover denied and allowed paths for CAS, KV, DB, document,
|
||||
- `[x]` Tests cover denied and allowed paths for CAS, KV, DB, document,
|
||||
pubsub, pipe, SSH proxy/admin shell, SSH cert metadata, and revocations.
|
||||
- `[x]` Initial two-daemon denied-mutation coverage exists for remote pubsub
|
||||
publish, remote pipe listen, and SSH admin shell.
|
||||
|
|
|
|||
Loading…
Reference in a new issue