mirror of
https://github.com/wweir/sower.git
synced 2026-10-20 08:16:35 +00:00
wweir
93ffaec848
The sowerd bounds plan still described the recursion driver as unfixed and carried a deploy log that the board receipt already holds; the client plan duplicated deploy pitfalls that live in the skill. Both now state what was verified, point at each other, and keep the regression lesson (the guard must ask the upstreams, not the system resolver) without restating the mechanism twice.
Documentation Index
This directory contains long-lived design documents. Per AGENTS.md rules:
docs/root holds only finalized, authoritative design documents (product, architecture, protocol, security, deployment, data model, test strategy, etc.).docs/plans/holds draft proposals and in-progress implementation plans — not authoritative.docs/reviews/holds review records, issue lists, and retrospective summaries — not authoritative.
When a plan or review produces a durable rule, it must be written back to the relevant root-level design document and referenced from this index.
Cross-document references must point to root-level design documents only. Never reference protocol, field, security, or deployment rules from plans/ or reviews/.
Root-Level Documents
| Document | Description |
|---|---|
| ARCHITECTURE.md | System boundary, layer responsibilities, data flows, design decisions |
| security.md | sowerd edge threat model, anti-probing layers, unknown-SNI certificate fallback, rejected directions |
Plans
Historical plans live under docs/plans/ and are not authoritative. Durable rules from completed plans are reflected only in the root-level documents listed above.
Reviews
No reviews yet.