Threat modeling
Clarify assets, adversaries, non-goals, and practical user risk.
For builders
LeftLevel is built to be inspected, questioned, and improved.
Developers and reviewers need clear boundaries, architecture notes, working links, and contribution paths.
Build philosophy
Understandable design beats impressive complexity.
A privacy-focused system needs components that can be reasoned about. LeftLevel favors small modules, clear documentation, explicit tradeoffs, and visible review points.
- Document what each layer protects and does not protect.
- Keep cryptographic choices explicit and replaceable.
- Separate research, prototype, and production language.
- Make testing and review part of the public identity.
Initial repository map
leftlevel.org Public website and docs protocol-notes Architecture records and threat model prototype-lab Small proof-of-concept experiments brand-assets Logos, social cards, and visual system
Contribution areas
Useful work starts with clarity.
Documentation
Improve explanations, diagrams, decision records, and setup notes.
Prototype review
Test small experiments, report findings, and challenge assumptions.