Architecture
Project boundaries, data flow, status semantics, and ledger expectations.
Read architectureResearch Notes
ProofX documentation records what the engines check, how candidates are ranked, and what should not be inferred from a negative search.
Core Documentation
Research Standards
Claim levels, verified run artifacts, public-copy rules, and wording that keeps results honest.
Read standardsLean Boundary
Root Lean package scope, bounded certificate rules, and acceptance criteria.
Read Lean notesFalsificationEngine
Shared scoring, ledger schema, and directed-search assumptions.
Read engine notesContent Strategy
Guidance for keeping the public site sober, specific, and traceable.
Read copy guideCollaboration
Useful collaboration starts with review: run commands, ledgers, failing tests, assumptions, and better candidate-generation ideas.
- Review scoring assumptions and documentation.
- Reproduce a run from its command and ledger.
- Contribute tests for engine behavior and edge cases.
- Suggest clearer ways to separate search evidence from proof claims.