Make contracts and architecture docs match settled behavior #55
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem and evidence
Current documentation repeats superseded or stale statements:
docs/DESIGN.md:22-26still depicts OIDC, Postgres and an outbound port-443 tunnel, while DECISIONS §§24 and 29 defer OIDC, settle on SQLite and describe the direct port-7443 tunnel.docs/contracts.md:2477says the generic-to-v1 failure adapter is not connected;crates/server/src/resources.rs:2095,2240,2325,2422now call and implement it.docs/contracts.md:2705points installation idempotency at §1.3; the relevant section is §1.5.crates/agent/PROVIDERS.md:75says generic network RPC remains disabled. Current provider RPC code and contracts include negotiated list/detail/action calls, while production defaults still start throughLegacyProvider. The same document says collection-time bounds are unfinished; that remains true for the legacyEnginelist path, whileprovider-bollardhas a bounded factory path. The docs need to distinguish those states.docs/PLAN.mdretains a long, superseded pre-approval step table in addition to the active plan.Recommendation
Shrink
docs/contracts.mdto wire/security invariants as the owner decided. Correct stale status and references, accurately separate legacy-default and factory-path status, remove or relocate the superseded plan/handoff text, and make the current entry point obvious. Keep behavior requirements in code and tests; do not add a second prose requirement-to-test system.Payoff and estimate
Reduces contradictory instructions and repeated reconstruction of current behavior. Estimate: 0.5–1 engineering day for the initial cleanup.
Priority: Now (≤1 day).
2026-10-04 owner decisions: The recommendation to add a requirements-to-tests index conflicts with the owner's decision that code and tests are the spec and contracts should contain invariants. This issue follows the owner's direction while keeping durable decision reasoning in DECISIONS.md.
Report: arch-review report
Source: arch-review 2026-10-04