Kontour Veritas Governance Kit — readiness adapter

Governance Kit readiness — ready verdict

A Veritas Governance Kit readiness evaluation with no blocking failures, projected into a Hachure trust.bundle whose software-readiness-verdict claim derives to verified.

1 verified

Download raw .bundle schemaVersion 5 · 1 claims · 1 evidence

Provenance

Produced by running the kit's readiness-to-trust-bundle.mjs adapter (commit 1948639) over the committed readiness record above; the projection is deterministic and re-runnable.

Repository: kontourai/flow-agents
Source path: kits/veritas-governance/fixtures/readiness/ready.readiness-report.json
Pinned commit: 7a083966db47672ea552f13264ea3111e08fa06b
Bundle source: veritas-governance-kit/readiness-adapter

Claims

What was gated, and how it landed

Each row is a claim the pipeline recorded — its type, the facet it belongs to, the field or behavior it covers, its recorded value, and the trust status the kernel derived. Read straight from the downloadable artifact.

Status	Subject / field	Type · facet	Value
verified	working-tree:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 mergeReadiness	software-readiness-verdict veritas.readiness	{"verdict":"ready","sourceRef":"working-tree:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855","blocking…

Evidence

What supports the claims

auditability policy_rule

Veritas readiness verdict is ready (run veritas-1783001685088); no blocking requirements or evidence failed.

veritas:readiness:veritas-1783001685088

Open questions

Gaps this receipt does not hide

No disputed claims, unsupported high-impact claims, or transparency gaps were derived from this bundle. Every recorded claim carries linked evidence.

Verify it yourself

Recompute this exact file

Download the raw .bundle above, then run it through the named validator — validateTrustBundle from @kontourai/surface. The CLI wraps it and exits non-zero if the artifact is not a well-formed trust.bundle.

validate this receipt

$ npx @kontourai/[email protected] report \

--input governance-readiness-ready.trust.bundle --format summary

# exit 0 prints the trust summary; a broken file exits 1

Prefer the library directly? The CLI just calls it:

node — the named validator

import { validateTrustBundle } from "@kontourai/surface";

import { readFileSync } from "node:fs";

validateTrustBundle(JSON.parse(readFileSync("governance-readiness-ready.trust.bundle", "utf8")));

# throws if the bundle is invalid; returns the parsed bundle otherwise