Planwright documentation is split by purpose. Start with the README for user-facing installation and usage then use these documents for project boundaries, architecture and maintenance details.
- ../README.md, installation, current scope and command overview
- ../examples/aws-webapp-basic/README.md, canonical AWS web application proof path
- compatibility.md, compatibility levels and current format support
- roadmap.md, version gate sequence and deferred work
- architecture/design.md, product boundary and engine shape
- architecture/threat-model.md, current trust boundaries and controls
- architecture/decisions/, Architecture Decision Records
- development/fixtures.md, compatibility fixture metadata and review rules
- development/standards.md, coding and documentation standards
- development/testing.md, testing expectations and fuzzing policy
- releases/README.md, release notes, release assets and integrity model
- project/GOVERNANCE.md, project governance
- project/MAINTAINERS.md, maintainer duties
- project/DCO.md, Developer Certificate of Origin sign-off requirements
For a quick project review:
- read ../README.md
- run or inspect ../examples/aws-webapp-basic/README.md
- read compatibility.md
- read architecture/threat-model.md
- read roadmap.md
For maintenance work:
- read development/standards.md
- read development/fixtures.md
- read development/testing.md
- read architecture/decisions/
- read releases/README.md