Exchange Contribution Paths
Exchange Contribution Paths
Section titled “Exchange Contribution Paths”Different contributions need different evidence and review.
Documentation correction
Section titled “Documentation correction”Use this path when a page is unclear, stale, inconsistent, or disagrees with an authoritative contract.
Include the affected page and the evidence supporting the correction.
Executable example
Section titled “Executable example”Use this path when a concept would benefit from a minimal runnable demonstration.
Prefer examples that include both expected success and expected failure behavior.
Reproducible issue
Section titled “Reproducible issue”Use this path for implementation problems that can be reduced to steps, inputs, environment, and observed result.
Integration feedback
Section titled “Integration feedback”Use this path when an external application consumes DigiEmu results, bundles, receipts, or evidence.
Document the contract version and integration boundary.
Research note
Section titled “Research note”Use this path for exploratory work that is not yet a stable contract or production recommendation.
Mark research status explicitly.
Contribution principle
Section titled “Contribution principle”A contribution should become more specific as its claim becomes stronger.
A production recommendation requires more evidence than an exploratory idea.