mirror of
https://github.com/wweir/sower.git
synced 2026-10-20 00:15:34 +00:00
wweir
5dc57bc234
Review of the anti-probing hardening found no code defects; the fixes are documentation: - docs/security.md: authoritative threat model, the three camouflage layers, unknown-SNI certificate fallback rules (whitelist source, error surfacing, capability propagation, concrete first entry), the client_hello fingerprint knob, rejected directions (QUIC, h2) with evidence, and residual accepted signals. - Promote the plan doc to a non-authoritative historical record per AGENTS.md docs rules; index security.md from docs/README.md and ARCHITECTURE.md. - config/sowerd.toml: document cert.domains; the first entry answers unknown-SNI handshakes.
27 lines
1.3 KiB
Markdown
27 lines
1.3 KiB
Markdown
# 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](../ARCHITECTURE.md) | System boundary, layer responsibilities, data flows, design decisions |
|
|
| [security.md](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.
|