← ProjectGitHub
GOVERNANCE

Make changes visible, reviewable, and verifiable.

BOUND governance should apply the same principles used by the method: explicit ownership, durable contracts, independent execution, and verification before integration.

Current governance status

The repository is currently a static GitHub Pages project. This documentation does not claim a formal governing body, committee, standards organization, or ratified specification process that is not documented elsewhere in the repository.

Change categories

  • Documentation: wording, navigation, examples, and explanatory material.
  • Method: changes to BOUND concepts, terminology, lifecycle, or normative guidance.
  • Artifacts: changes to proposed schemas, examples, or machine-readable structures.
  • Verification: changes to CI checks, validation rules, and acceptance evidence.
  • Project: contribution process, roadmap, release notes, and repository structure.

Change control

Changes that affect the meaning of a contract or artifact should be explicit about compatibility and version impact. A “contract freeze” means that changes are visible and governed; it does not mean that the contract can never change.

  1. State the affected domain and boundary.
  2. Describe the contract or documentation change precisely.
  3. Identify affected consumers, examples, schemas, or verification rules.
  4. Update the relevant tests, examples, or documentation.
  5. Run repository verification before integration.
  6. Record material releases or changes in the changelog.

Decision ownership

Domain ownership should remain explicit. Contributors may execute work within an agreed boundary, but changes that cross boundaries should identify the affected owners and interfaces rather than relying on implicit assumptions.

Future governance work

As BOUND becomes more formalized, this page can be extended with a versioning policy, specification status model, decision records, maintainer roles, compatibility policy, and a formal proposal process. Until those exist, they should be treated as future work rather than established project policy.