No description
f3ab842cc2
Add comprehensive implementation notes based on sender client development: - Detailed cryptographic primitive specifications (Curve25519, XSalsa20-Poly1305) - Memory safety patterns (move semantics for plaintext) - State machine enforcement strategies - Unicode and character counting considerations - Cryptographic property documentation (randomness, overhead) - Design decisions with rationales - Additional open questions discovered during implementation - Updated constraints with actual size calculations |
||
|---|---|---|
| src | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| README.md | ||
| SPECIFICATION.md | ||
About
A simple little protocol for a "message box" where people can send me messages that are sealed "on site" in their local client (most likely
their web browser). Read SPECIFICATION.md for more details.
Purpose
This is intended to test a workflow using LLM pair design and programming. I've found LLMs to be great at dumping code that is annoying to read and understand, but mostly works. I would like to design systems that are pleasant and easy to understand, with the essential components displayed to the human in a way that is abstacted away from noisy implementation details, which are handled by the LLM.
Goals
- Complete specification in informal markdown
- Implement concretely in code
- Apply standard code tests
- Complete specification in formal language (P, Quint, etc.)