The website is itself a BOUND example.
The documentation architecture is represented as explicit domains, boundaries, interfaces, and verification targets. The machine-readable map is proposed and versioned separately from the prose.
Why this exists
A methodology site should demonstrate the same engineering discipline that it teaches. Making its own structure explicit creates a concrete test case for BOUND without claiming that the website is a complete runtime implementation.
Domains
- Method — owns core terminology and lifecycle semantics.
- Guides — owns application and tutorial guidance.
- Reference — owns artifact structures and schema references.
- Examples — owns illustrative system mappings.
- Agents — owns bounded agent participation and security guidance.
- Research — owns research methodology and evidence presentation.
- Project — owns repository process, roadmap, and status.
Machine-readable artifacts
Verification
CI currently verifies file presence, JSON syntax, HTML titles, local links, and basic structural requirements of the website boundary map. The next level is to derive more checks from these declared boundaries and interfaces.
Scope
This is a proposed reference representation. It does not establish a formal specification, runtime, plugin protocol, or autonomous governance mechanism.