V12.0 BASE CONTRACT

Community + contribution

Move from reader to contributor without weakening source, fixture, release-boundary or proof discipline.

01 source + issues§

The tagged release README points to repository contribution, conduct, security and template files. Those repository files remain authoritative for GitHub mechanics. This page adds the project-level evidence workflow; it does not replace CONTRIBUTING.md.

02 report a bug§

VERSION / COMMIT
HOST + TARGET PROFILE
EXACT COMMAND
MINIMAL .dby SOURCE OR FIXTURE
EXPECTED RESULT
OBSERVED STDOUT / STDERR / EXIT STATUS
ARTIFACT SHA-256 (WHEN BYTES MATTER)

Remove secrets and unrelated machine state. Prefer the smallest reproducer that still fails. If a binary artifact is involved, keep its hash and say whether it came from the frozen release package or a workspace build.

03 add or change an example§

State whether the example is RUNNABLE, ILLUSTRATIVE, or COMPATIBILITY.
Include the exact command required to run/build it.
Include expected stdout, file bytes, size or SHA-256 when the result is deterministic.
Link the example to the contract it demonstrates; do not promote an example into a language guarantee.
If the public docs mirror release bytes, verify the mirror is byte-for-byte identical.

04 change a contract§

A semantic/native contract change is not a documentation-only edit. Identify the normative source, intended version boundary, affected target/profile, failure behavior and proof that must change. Historical documents keep the version of the thing that produced them.

CONTRACT CHANGE
  normative source
  old behavior
  new behavior
  version / milestone
  affected fixtures
  verifier update
  negative / failure cases
  release-note impact

05 run the appropriate proof§

REPOSITORY SOURCE · WINDOWS POWERSHELL · V12 HIR PROOF

powershell -ExecutionPolicy Bypass -File scripts\verify_native_v12_hir.ps1

The v12 release documentation names this repository-source verifier. The published Windows release ZIP does not contain the full repository verification suite, so do not claim release-ZIP-only reproduction for this command.

For a small hosted change, also run the narrowest relevant check first:

dbyte check path\to\case.dby
dbyte run path\to\case.dby
dbyte run --vm path\to\case.dby

REPRODUCE PROOFS · DIAGNOSTICS

06 pull-request evidence packet§

INTENT
SCOPE
FILES CHANGED
CONTRACT / NON-CONTRACT
TESTS / VERIFIERS RUN
OBSERVED OUTPUT
KNOWN FAILURE RISKS
WHAT IS NOT CLAIMED

Keep the change surgical. Do not include unrelated generated build output merely to make the diff look complete. A report is a claim until the commands, fixtures and observed results support it.

07 chat§

DISCORD COMMUNITY

08 governance boundary§

The supplied release material does not define a formal standards body, RFC council or stable governance constitution. This manual therefore does not invent one.

SOURCE POLICY: source + contract + fixture + observed verification outrank prose. Repository contribution files define current submission mechanics.