Current documentation
Modern Architecture Principles
Provisional engineering principles that will guide evaluation of revival proposals.
This is a requirements framework, not a final system architecture.
1. Interoperability
- •Prefer documented open standards.
- •Test against independent implementations.
- •Publish compatibility boundaries and extension behaviour.
- •Avoid unnecessary protocol invention.
2. Security and privacy
- •Define the threat model before selecting cryptography.
- •Minimise trusted infrastructure and retained metadata.
- •Use maintained cryptographic libraries.
- •Require review before making end-to-end security claims.
3. Maintainability
- •Start with a narrow component.
- •Automate testing and release production.
- •Keep dependencies explicit and reviewable.
- •Support migration and operational diagnosis.
4. Historical continuity
The revival may learn from SIP Witch, ZRTP, ccRTP, Bayonne, and the GNU Free Call vision, but it will not preserve obsolete architecture solely for branding continuity.
Interested in helping before the public repository opens? Contact TwoSquares with your area of interest or any historical material you can verify.