Card Commons welcomes corrections, implementation feedback, interoperable examples, research, and carefully scoped proposals.
- Read the executive brief and decision log.
- Open an issue for changes that alter a normative contract, product scope, or governance rule.
- Separate verified evidence from hypotheses. External claims require a source entry and a claim-ledger update.
- Do not add personal correspondence, private research notes, or generated assets without provenance and usage rights.
- Keep the canonical idea in one document and link to it elsewhere.
- Update JSON Schema fixtures whenever a contract changes.
- Add an architecture decision record for material changes.
- Run
npm run check. - Describe compatibility and migration impact.
Breaking protocol changes increment the minor version during the 0.x
series. Editorial changes do not. A proposal becomes accepted after:
- a public issue states the problem and alternatives;
- at least one maintainer approves the decision;
- schemas, examples, documentation, and tests agree; and
- the decision is recorded in
DECISIONS.md.