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

These are the statuses the validator works out from the evidence, not the ones written in the file. Run the command further down and you get this row back.

Download raw .bundleschemaVersion 5 · 1 claims ·1 evidence

In plain language

What this receipt says

The answer was no.

What was checked

One claim, about one thing — a single assertion this run makes about itself, with its own policy attached. The kind of thing being claimed:

software-readiness-verdict

How they came out

1 disputed.

disputedevidence contradicts it

What backs them

1 evidence record captured while the commands ran — 0 reporting a pass, 1 reporting a failure. Every claim here is backed by an evidence record, a verification event, or both.

What's still open

1 transparency gap, blocking, listed in full below. The receipt records it rather than dropping it.

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.

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

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.

second opinion — the reference CLI

$ npx -y -p [email protected] -p [email protected] hachure validate \

governance-readiness-not-ready.trust.bundle

valid TrustBundle (schemaVersion 5)

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

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.

policy_violationseverity highblocking
Evidence explicitly reported a non-passing result. — the written policy for this claim was not satisfied.
On the claim: “mergeReadiness”
working-tree-798d536c54a9d1c0d4c238509527732827088f61d7e74a65c9f830ccb8d77eca.veritas-readiness.mergereadiness
under policy policy:software-readiness-verdict

Provenance

Where this file came from

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

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 — 0 passing, 1 failing

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

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.

Show all 1 claims

Derived status	Subject / field	Type · facet	Value
disputed	working-tree:798d536c54a9d1c0d4c238509527732827088f61d7e74a65c9f830ccb8d77ecamergeReadiness	software-readiness-verdictveritas.readiness	{"verdict":"not-ready","sourceRef":"working-tree:798d536c54a9d1c0d4c238509527732827088f61d7e74a65c9f830ccb8d77eca","blocking":{"failedRequirements":["required-veritas-cli-artifacts"],"failedEvidenceChecks":[]}}