Skip to content
BANG

Common journey evidence

This page is generated. Program outputs come from each canonical expected.txt; the logger evidence label and claim come from the validated serialized docfact. The page does not contain a hand-copied terminal transcript.

canonical source → check/query → env | oracle | compiled → expected output
MomentCanonical sourceExpected on env/oracle/compiled
Thunk/forceexamples/thunk-force/main.bang7
Effect arithmeticexamples/effect-op-arith/main.bang70
Counting handlerexamples/logger-counting/main.bang3
Silent handlerexamples/logger-silent/main.bang0

The executable journey additionally checks 1 + 2, exact check --json output, the query dump schema, and that the two logger programs differ only in the handler clause.

Serialized logger evidence

Differential-tested — The counting and silent programs differ only in the handler clause; the env, oracle, and compiled engines produce each committed expected output byte-for-byte, and check --json plus query dump succeed for both.

Sources:

Validating commands:

just test-docfacts-logger

Complete common-journey gate

nix develop --command bash -lc 'just check-examples && just check-examples-env && just docs-check'
nix develop --command bash -lc 'just check-examples && just check-examples-env && just docs-check' --json --require-clean > /tmp/bang-onboarding-journey.json

The machine artifact records the source SHA, binary hash, every required step result, and explicit pass/fail/skip counts. --require-clean refuses dirty provenance.