Kontour Veritas Governance Kit — readiness adapter

Governance Kit readiness — blocked verdict

A readiness evaluation that a required standard blocks: the projected software-readiness-verdict claim derives to disputed, showing what a gate looks like when it refuses to pass.

1 disputed

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 not-ready readiness record above; the projection is deterministic and re-runnable.

Repository: kontourai/flow-agents
Source path: kits/veritas-governance/fixtures/readiness/not-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
disputed	working-tree:798d536c54a9d1c0d4c238509527732827088f61d7e74a65c9f830ccb8d77eca mergeReadiness	software-readiness-verdict veritas.readiness	{"verdict":"not-ready","sourceRef":"working-tree:798d536c54a9d1c0d4c238509527732827088f61d7e74a65c9f830ccb8d77eca","bloc…

Evidence

What supports the claims

auditability policy_rule

Veritas readiness verdict is not ready (run veritas-1783001840335). Blocking: required-veritas-cli-artifacts.

veritas:readiness:veritas-1783001840335

Open questions

Gaps this receipt does not hide

disputed mergeReadiness — evidence disputes this claim.

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-not-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-not-ready.trust.bundle", "utf8")));

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