Project update: 15 November 2026. GitHub change #6: merged into the repository. The underlying protocol remains draft and unaudited.
A 20-page illustrated guide explains Secure Net's architecture, private communication model, technical building blocks and limitations.
Why we made this change
Documentation is not a finishing touch for an open-source protocol. It is how someone outside the original development work can understand the choices, challenge assumptions and build a compatible client. The guide uses approachable explanations alongside detailed notes for developers, helping both audiences without hiding complexity.
The engineering record
The original pull request records the following technical scope and evidence. Some forward-looking notes in the record reflect the state of the work when the request was opened, rather than its status today.
Adds docs/guide/: a 20-page guide to Secure Net (PDF, plus the single HTML file it is printed from) that explains what the protocol is, how it is built, how it works and how to use it. Each section starts in plain words and adds a "For builders" box with the exact construction.
- Describes main (0.4.0). The open pull requests (#3, #4, #5) are covered in one section and marked "Proposed" throughout.
- Seven diagrams, drawn as inline SVG.
- States the limits plainly: no independent audit, no human cryptographic review of the newest parts, no formal model, one implementation.
- Technical statements were checked against
spec/and the code (signed bytes, key ids, relay suite, safety number, ledger ids, limits).npm install github:Comutability/secure-netwas tested from a clean folder.
Documentation only; no code changes. Please read it for accuracy before merging: it was prepared by an AI assistant and has not been reviewed by a person.
The wider direction
The Comutability approach is open source with human accountability. AI can help research, design, write code and test it, but a merged change is not the same thing as an independently audited product. Secure Net is explicitly described as a draft in its public README. Its use in a sensitive situation should wait for qualified cryptographic review.
What happens next
Maintain the guide alongside the standards, ensure any experimental parts are labelled correctly and welcome accessibility and technical feedback.
