Contribute through explicit boundaries and evidence.

Before changing the repository

• Identify the documentation domain you are changing.
• Check existing method terminology and artifacts before introducing new terms.
• Keep examples consistent with the documented concepts.
• Do not present proposed schemas, benchmarks, integrations, or future capabilities as implemented facts.

Contribution workflow

1. Define the intended change and its boundary.
2. Make the smallest coherent implementation.
3. Update affected documentation, links, examples, and machine-readable artifacts together.
4. Run the repository's documentation validation.
5. Open a pull request describing the change and its verification evidence.
6. Integrate only after the change is reviewable and verification passes.

Documentation quality

Every documentation page should have a meaningful title, working local links, terminology consistent with the method, and a clear distinction between current behavior, proposed artifacts, research hypotheses, and future roadmap items.

Agent-assisted contributions

AI agents may assist with bounded implementation work. The governing boundary, permitted change surface, contracts, and acceptance evidence should remain explicit. An agent's ability to edit files or call tools does not by itself grant authority to redefine the boundary or acceptance criteria.

Verification

The current CI validates required documentation files, JSON syntax for the artifact schemas, HTML titles, and local links. More verification can be added as examples, schemas, and the website's own BOUND representation become more formal.

What this page does not establish

This page is contribution guidance, not a substitute for a future formal contributor agreement, code of conduct, security policy, or specification governance process. Those should be added when they are actually defined.