mirror of
https://github.com/wweir/sower.git
synced 2026-10-20 00:15:34 +00:00
wweir
6e22cf42a2
Another session identified the driver of the connection burst: any proxy request naming sower.wweir.fun forms a self-sustaining r6c<->kr chain (measured 155->601 connections on r6c, 311 dials / 649 fds on kr). sowerd's cap and write-stall bound it; the client-side self-target guard is the real fix and stays open, as does the conns relay defect. Also records that v1.7.2 never published (its Windows build failed) and kr now runs the v1.7.3 release artifact (sha256 74b34fd9..., vcs.modified=false).
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.