Evidence Model

BoundaryKit uses evidence to keep production claims honest. A workload is not ready because a file exists or a command was intended to run; it is ready only when current evidence proves the gate.

BoundaryKit draws on a running local implementation. This evidence model distinguishes that operational experience from specific test results. The worked example has fictional inputs and unexecuted probes; its not-run statuses apply only to that teaching packet. Public records distinguish three forms:

Example receipts are fake and marked example_only; this includes the fictional substrate PASS table from the retired lab design.
Historical scoped observations are newly written public summaries of earlier negative tests. They name what was observed, but do not imply current runtime/version/date or adjacent boundaries.
Operational experience records the operator-confirmed running local implementation and its high-level architecture, documented 2026-10-03. This acknowledges actual use without treating operation as a security audit or recovery-test result.

Evidence Principles

Evidence is observed, not invented; fictional examples are explicitly labeled.
A real receipt should record exact inputs, commands, outputs, and stop conditions privately; public summaries omit raw transcripts and private identifiers.
Secret values are never public evidence.
A failing receipt is useful when it preserves the scoped failure.
Promotion and recovery claims require their own observed evidence.

Common Receipt Fields

Field	Purpose
`status`	gate state, such as `example_only_pass`, `blocked`, or `failed`
`scope`	what the receipt does and does not authorize
`artifact`	digest-pinned fake or real artifact reference, depending on repo context
`source`	source revision or synthetic example revision
`policy`	policy file and hash, if applicable
`sbom`	SBOM path and checksum, if generated
`signature`	signing and verification result
`validation`	commands run and observed result
`audit`	audit sink or local example log result
`rollback`	rollback target and drill evidence
`boundary`	actions not performed, such as no push, no deploy, or no traffic shift
`risks`	unresolved issues and review questions

Gate Evidence

Gate	Evidence required
Build	artifact digest, source revision, build command, checksum or image id
SBOM	generated SBOM path and checksum
Signature	signature command result and verification result
Policy	tool allowlist, denied tools absent, schema hash behavior, fail-closed behavior
Egress	default deny proof and audit event
Deploy-only canary	health, readiness, running digest matches manifest
Read-only canary	expected read behavior, denied write/tool behavior, audit trail
Rollback	target, command, elapsed time, post-rollback health
Promotion	evidence packet review and explicit decision

Public Evidence In This Repo

Files under examples/reference-cell/evidence/ demonstrate fictional receipt shape only. Files under docs/evidence/ distinguish the fictional substrate example from historical scoped sandbox and inference-path observations. The latter do not prove current realm isolation, successful credential resolution, or recovery. No public receipt authorizes production-readiness claims.