Build the website using BOUND principles.
The website should progressively become an instance of the methodology it documents: explicit domains, boundaries, durable contracts, independent execution, and continuous verification.
Project surfaces
- Governance — change categories, contract-change discipline, decision ownership, and current governance status.
- Contributing — bounded contribution workflow and repository verification expectations.
- Roadmap — completed foundation and future implementation phases.
- Changelog — factual record of repository changes. \n
- Website BOUND Map — machine-readable documentation domains, boundaries, and verification targets.
Current implementation
The repository is a static GitHub Pages site with an engineering documentation layer. The current CI validates required documentation files, artifact-schema JSON, HTML titles, and local links.
BOUND reference-implementation direction
The long-term direction is to make the website itself an executable example of BOUND: documentation domains have explicit ownership boundaries; important structures have durable contracts; contributors and automation execute bounded changes; and CI provides continuous verification.
Current rebuild sequence
- Documentation and information architecture
- Method and Quickstart
- Canonical artifacts and reference
- Practical examples
- Agent integration and security
- Research and benchmark design
- Governance and contribution surfaces
- Website-as-BOUND verification and machine-readable project structure
Important distinction
Roadmap items, proposed schemas, proposed benchmark dimensions, and future agent/plugin integration are not current runtime capabilities unless an implementation and verification artifact says otherwise.