Verdict Record Schema: Result and Pathway Verdicts

The verdict-record.schema.json defines the contract for the complete verdict adjudication on an orthing episode. It holds statuses for all verdict IDs, the governance-derived required path, per-claim reasoning paths, and the objectivity index that makes pathway adequacy judgments objective relative to a declared analysis, actor, decision time, and information state.

Verdict semantic IDs (e.g., RESULT_CORRECT, GOV_TOKEN_ADEQUATE) are authoritative in machine records. Display aliases (V1, V3c) are for prose and equations only. The IDs are defined in docs/verdict-registry.yaml (Decision 0004).

Required Fields

episode_id

string

required

The episode this verdict record belongs to.

index

object

required

The full objectivity index: the analysis, evaluating actor, decision time, and information state relative to which this verdict is objective. Dropping any component makes “objective” an overstatement (R4 finding B3).

Show index properties

analysis_id

string

required

Which analysis governs the verdict (must match the episode’s declared analysis).

analysis_version

string

required

Version of the analysis.

actor

string

required

The evaluating actor whose EX_ANTE_JUSTIFIED index this is.

decision_time

string

required

The decision time the ex-ante judgment is indexed to.

information_state

string

required

The information state available at decision_time.

required_path

array

required

ReqPath(e) — the governance-derived required path. An array of verdict semantic IDs from CorePath ∩ RequiredBy(A, shape, risk, claims, governance). Must have at least one item.

statuses

object

required

Verdict statuses keyed by semantic ID. All keys must be valid verdict IDs from the registry. Values are one of "pass", "fail", "undetermined", or "not-applicable".

pathway_state

enum

required

The aggregate pathway state: "adequate", "defective", or "undetermined". Derived as the conjunction over all verdicts in required_path.

All Verdict IDs

The following table lists all 14 verdict semantic IDs from the normative registry (v1.0.0):

Semantic ID	Alias	Side	Factive	Meaning
`RESULT_CORRECT`	V1	result	yes	Placement correctness against O*(m; A(e))
`EVIDENCE_SUPPORT`	V2a	pathway	no	Evidence meets the declared support standard per placed claim
`PROCEDURE_RELIABLE`	V2b-P	pathway	no	Configured-procedure truth-conduciveness under the predeclared RelSpec
`TOKEN_TRUTH_LINKED`	V2b-T	result	yes	Factive, claim-wise truth linkage through the truth-relevant mechanism
`EVIDENCE_CURRENT`	V2c	pathway	no	Load-bearing evidence current for (κ, v) with admissible provenance
`GOV_CONFIG_ADEQUATE`	V3a	pathway	no	Governing configuration adequacy for the case’s risk class
`GOV_POLICY_ADEQUATE`	V3b	pathway	no	Meta-policy well-formedness for the configuration it runs under
`GOV_TOKEN_ADEQUATE`	V3c	pathway	no	Metaorthemma binding adequacy — token correctly instantiated, compatible, anchored, scoped, current, provenanced, authorized
`EXECUTION_FAITHFUL`	V3d	pathway	no	Executor fidelity — the actor executed the procedure as written
`EX_ANTE_JUSTIFIED`	V3e	pathway	no	Decision-time reasonableness on exactly the evidence then available
`ROUTE_ADMISSIBLE`	V4a	pathway	no	Route safety under the constraints in force
`ROUTE_QUALITY`	V4b	advisory	no	Near-optimality advisory (safe is not best) — not in CorePath
`CLOSURE_TRUTHFUL`	V5	pathway	no	Closure matches the burden ledger — no disposition collapse
`ROBUST_NEIGHBORHOOD`	V6	pathway	no	Robustness under the declared perturbation family

Optional Fields

na_reasons

object

Required for every not-applicable status anywhere in the record (not only on the required path). Keys are verdict IDs; values are non-empty explanation strings. The cross-record validator enforces this.

claim_verdicts

array

Per-claim result-side records. Each item covers one claim:

Show claim_verdicts item properties

claim_id

string

required

The claim this entry covers.

result_correct

enum

required

"pass", "fail", or "undetermined" for this claim’s placement correctness.

token_truth_linked

enum

"pass", "fail", "undetermined", or "not-applicable". Schema enforces: if token_truth_linked is "pass", then result_correct must be "pass" (factivity constraint).

claim_reasoning_paths

array

Per-claim reasoning path adequacy (Decision 0011). ReqReason_q(e) is the projection of ReqPath onto verdicts that bear on claim q. A downstream routing or closure failure must not flip a soundly reached claim.

Show claim_reasoning_paths item properties

claim_id

string

required

The claim this entry covers.

req_reason

array

required

The subset of required_path verdicts that bear on this specific claim.

reasoning_path_adequate

enum

required

"adequate", "defective", or "undetermined" — the conjunction over req_reason.

per_token_v3c

array

Per-token GOV_TOKEN_ADEQUATE statuses preserved alongside the episode-level conjunction. Useful for auditing which specific metaorthemma token failed and which conjunct of the adequacy definition it failed on.

Show per_token_v3c item properties

token_id

string

required

Token identifier.

status

enum

required

"pass", "fail", or "undetermined".

failing_conjunct

enum

Which conjunct of the TokenAdequate definition failed: MetaInst, Compatible, Anchored, ScopeCorrect, Current, Provenanced, or AuthorizedBinding. Null if status is not fail.

rel_spec

object

RelSpec per claim for PROCEDURE_RELIABLE (V2b-P). Keys are claim IDs; values are full reliability specifications conforming to reliability-spec.schema.json. A free-form string does not satisfy this field (R4 enforcement).

perturb_spec

object

PerturbSpec per claim for ROBUST_NEIGHBORHOOD (V6). Keys are claim IDs; values are full perturbation specifications conforming to perturbation-spec.schema.json.

Minimal Example

verdict-minimal.json

{
  "episode_id": "ep-B7-verify-1",
  "index": {
    "analysis_id": "site-perpendicularity-check",
    "analysis_version": "2.1",
    "actor": "site-qa-reviewer",
    "decision_time": "2026-07-02T09:15:00Z",
    "information_state": "four-face level readings ev-1 and cal-lab cert for level-114"
  },
  "required_path": [
    "EVIDENCE_SUPPORT", "PROCEDURE_RELIABLE", "EVIDENCE_CURRENT",
    "GOV_CONFIG_ADEQUATE", "GOV_POLICY_ADEQUATE", "GOV_TOKEN_ADEQUATE",
    "EXECUTION_FAITHFUL", "EX_ANTE_JUSTIFIED", "ROUTE_ADMISSIBLE", "CLOSURE_TRUTHFUL"
  ],
  "statuses": {
    "RESULT_CORRECT": "pass",
    "EVIDENCE_SUPPORT": "pass",
    "PROCEDURE_RELIABLE": "pass",
    "EVIDENCE_CURRENT": "pass",
    "GOV_CONFIG_ADEQUATE": "pass",
    "GOV_POLICY_ADEQUATE": "pass",
    "GOV_TOKEN_ADEQUATE": "pass",
    "EXECUTION_FAITHFUL": "pass",
    "EX_ANTE_JUSTIFIED": "pass",
    "ROUTE_ADMISSIBLE": "pass",
    "CLOSURE_TRUTHFUL": "pass",
    "TOKEN_TRUTH_LINKED": "pass",
    "ROBUST_NEIGHBORHOOD": "not-applicable",
    "ROUTE_QUALITY": "pass"
  },
  "na_reasons": {
    "ROBUST_NEIGHBORHOOD": "no predeclared robustness obligation for this risk class"
  },
  "pathway_state": "adequate"
}

For the full worked verdict record, see the Pillar Episode example.

Introduction

Core Concepts

Worked Examples

Schemas & Validation

Experiments & Terminology

Verdict Record Schema: Result and Pathway Verdicts

Required Fields

All Verdict IDs

Optional Fields

Minimal Example

Build docs developers (and LLMs) love

Introduction

Core Concepts

Worked Examples

Schemas & Validation

Experiments & Terminology

Documentation Index

​Required Fields

​All Verdict IDs

​Optional Fields

​Minimal Example

Build docs developers (and LLMs) love

Required Fields

All Verdict IDs

Optional Fields

Minimal Example