Working glossary
The terms that carry consequence.
These definitions are deliberately narrow. They separate evidence, authority, software state, and release claims.
- Claim-matched evidence
- Evidence interpreted only for the claim it supports: observation proves occurrence, a test proves exact-build behavior, policy defines allowed behavior, and an assertion proves it was stated.
- Scoped disposition
- A named human decision with a defined subject, boundary, authority basis, source passage, and currency. It does not imply release approval.
- Representative case
- One real or explicitly simulated workflow instance chosen with stated scope and limitations. It can reveal behavior; it cannot establish frequency alone.
- Candidate binding
- The exact software, model route, prompts, configuration, data, tools, and policy revision to which evaluation or release evidence applies.
- Readback
- A source-of-truth check that verifies the requested effect occurred with the intended scope and result.
- Typed dependency graph
- An inspectable map of which evidence, decisions, and revisions affect downstream artifacts. It routes review; it never grants authority.
- Behavior bundle
- A versioned set of model route, prompt, context policy, guardrails, harness, and compatibility assumptions evaluated together.
- Currentness
- Whether a projection still matches governed upstream evidence and decisions. Current does not mean accepted or approved.