Contributor guide

Contribution Workflow

issue/discussion → bounded proposal → implementation/evidence → pull request → automated checks → review → merge → release qualification where applicable

Good contributions

A reproducible failure, counterexample, unclear specification, portability problem, test improvement or documentation correction is useful. You do not need to understand every subsystem before contributing.

High-impact areas

External clean-room implementation.
Linux/macOS/Windows reproduction.
Canonicalization/signature review.
Authority/provider-capture counterexamples.
BTDU exact reconstruction and scale qualification.
Onboarding/documentation usability.

Claim discipline

Do not label BTG-controlled evidence as independent. Do not upgrade a skipped or partial result into PASS. Changes affecting identity, authority, signature meaning, recovery, portability, evidence semantics, rights/settlement or wire compatibility require architecture/governance review.