Flow Agents delivery bundle

In plain language

What this receipt says

Everything it claimed came back supported.

What was checked

16 separate claims, each one a single assertion this run makes about itself — not one summary verdict you have to take or leave. The kinds of thing being claimed:

• workflow.check.command
• workflow.check.policy
• workflow.acceptance.criterion
• workflow.critique.review

How they came out

12 verified, 4 proposed.

• verifiedevidence supports it and a verification event confirmed it
• proposedrecorded, but nothing has confirmed it yet

What backs them

11 evidence records captured while the commands ran — 11 reporting a pass, 0 reporting a failure. 4 claims carry neither an evidence record nor a verification event, which is why they can't come out verified.

What's still open

The validator finds no transparency gaps in this file. It does list 4 high-impact claims as unsupported — spelled out below.

What it doesn't tell you

Whether the code is correct, or whether the checks that ran were the right checks. A receipt records what was asked, what was run, and what came back. It narrows what you have to take on faith; it doesn't get it to zero.

Check it yourself

Recompute this exact file

Download the raw .bundle above and run it through @kontourai/surface — our implementation of the Hachure trust.bundle format, an open spec we publish schemas for but don't own the definition of. The command prints the same status row this page shows, and exits non-zero if the artifact isn't a well-formed trust.bundle.

Want a second opinion from a different codebase? The hachure reference CLI reads the same file against the spec's own schemas and reaches the same verdict. Both are still maintained by us — the implementations are independent, the organization behind them isn't yet.

Prefer the library directly? The CLI just calls it:

Open questions

What this receipt leaves open

Straight from the validator's own transparencyGaps and high-impact-unsupported lists — the same lines the command above prints. Not a count this site works out for itself.

0 transparency gapsNothing contradicts anything else, no policy went unsatisfied, and no evidence has aged past what its policy allows.

Provenance

Where this file came from

Committed by the Flow Agents delivery pipeline with kontourai/flow-agents#277 (the @kontourai/surface 2.0.0 migration) and taken verbatim from delivery/trust.bundle at that merge commit on main.

Repository

kontourai/flow-agents

Source path

delivery/trust.bundle

Pinned commit

573b45ec28453392bc11286ef7378b6627c790e0

Bundle source

flow-agents/workflow-sidecar;statusFunctionVersion=2

Recomputing tells you the file is internally consistent and hasn't been edited since. It doesn't tell you nobody rewrote the evidence before publishing — that's what the pinned commit is for. Follow it and compare.

Evidence

What actually ran — 11 passing, 0 failing

• validationtest_output

  npm run check:content-boundary --

  surface-2-facet-migration/evidence.json

• validationtest_output

  npm run validate:source --

  surface-2-facet-migration/evidence.json

• validationtest_output

  npm run context-map -- --check

  surface-2-facet-migration/evidence.json

• validationtest_output

  bash evals/run.sh static

  surface-2-facet-migration/evidence.json

• validationtest_output

  bash evals/integration/test_veritas_governance_kit.sh

  surface-2-facet-migration/evidence.json

• auditabilitypolicy_rule

  true # package.json declares "@kontourai/surface": "^2.0.0" (npm view @kontourai/surface version => 2.0.0)

  surface-2-facet-migration/evidence.json

• auditabilitypolicy_rule

  true # npm run build (tsc -p tsconfig.json) compiles cleanly with no errors

  surface-2-facet-migration/evidence.json

• auditabilitypolicy_rule

  true # npm run test:unit -> 35/35 node --test pass (also exercised inside Static eval suite's test_unit_helpers.sh)

  surface-2-facet-migration/evidence.json

• auditabilitypolicy_rule

  true # re-grep of src/, scripts/ci/, kits/, evals/ for Claim.surface write sites (.surface, surface:, "surface") found zero remaining sites outside the documented hachure@0.5.1-constrained veritas-governance adapter exception

  surface-2-facet-migration/evidence.json

• auditabilitypolicy_rule

  true # bash evals/ci/run-baseline.sh (all 3 required lanes, 37 checks) ran clean locally (0 failed, 3 expected skips) and independently in CI: PR #277 'Runtime and Kit' (https://github.com/kontourai/flow-agents/actions/runs/28610346124/job/84840941025), 'Workflow Contracts' (https://github.com/kontourai/flow-agents/act…

  surface-2-facet-migration/evidence.json

• auditabilitypolicy_rule

  true # node scripts/ci/trust-reconcile.js --bundle delivery/trust.bundle exits 0 locally against the small reconcilable-claim set above, zero divergences

  surface-2-facet-migration/evidence.json

The artifact

Every claim, raw

The unedited claim list as it sits in the file. The wording is the pipeline's own note-taking — written for the next run, not for reading — and it's here so you can check that the summary above didn't quietly skip anything.

Next