Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/theislampill/orthemology/llms.txt

Use this file to discover all available pages before exploring further.

The pillar episode is the framework’s primary nominal example — an F1-shaped verification in which every verdict passes and the pathway is recorded as adequate. It illustrates what a well-governed occurrence-centered episode looks like from analysis declaration through evidence collection, metaorthemma binding, claim ledger, and final verdict record. This is a deterministic illustrative fixture; it makes no empirical claim about any real construction site or measurement outcome.

​
Scenario

Before transferring load onto pillar B7, the site team must confirm that the pillar’s perpendicularity falls within the declared structural tolerance. Analysis site-perpendicularity-check (version 2.1) governs this task; it declares two independent axes, a tolerance, a bounded evidence repertoire, and loss-asymmetric hard constraints that prohibit any release without a current instrument calibration certificate.

Analysis

site-perpendicularity-check v2.1 — verify pillar perpendicularity before load transfer; tolerance 0.002; governed by site quality SOP-17.

Episode

ep-B7-verify-1 — actor fitter-9, evidence ev-1 (four-face level reading, level-114 run 2026-07-02), placement within-tolerance.

Metaorthemma

tok-B7-perp-1 binds perpendicularity-standard v3.0 to pillar-B7 (as-poured). Binder: site-engineer-2 under work-order-5512.

Verdict

All verdicts: pass. pathway_state: adequate. ROBUST_NEIGHBORHOOD: not-applicable (no predeclared robustness obligation for this risk class).

​
Analysis structure

The analysis declares a two-axis factorized profile over perpendicularity (exclusive alternatives) and surface-condition (co-holding values). The loss entry is explicit: releasing an out-of-tolerance pillar dominates; holding a within-tolerance pillar costs schedule only. 
{
  "analysis_id": "site-perpendicularity-check",
  "version": "2.1",
  "task": "verify pillar perpendicularity before load transfer",
  "tolerance": 0.002,
  "axes": [
    {
      "name": "perpendicularity",
      "exclusivity": "alternatives",
      "values": ["within-tolerance", "out-of-tolerance"]
    },
    {
      "name": "surface-condition",
      "exclusivity": "co-holding",
      "values": ["cracked", "stained", "clean"]
    }
  ],
  "hard_constraints": [
    "no release without a current instrument calibration",
    "measurement at all four faces"
  ],
  "loss": "releasing an out-of-tolerance pillar dominates; holding a within-tolerance pillar costs schedule only"
}

​
Governing metaorthemes

Two metaorthemes govern this episode. Their precedence is declared: calibration-policy must be satisfied before perpendicularity-standard results are admissible.
Governs the verification component V. States partition into within-tolerance / out-of-tolerance. The selector is a four-face digital level reading compared against the declared 0.002 tolerance (SOP-12). Meta-policy: within-tolerance → accept and record; out-of-tolerance → reject, tag, escalate to site engineer. Provenance: site engineering standards board, standards-adoption minute 2026-03.
{
  "mu_id": "perpendicularity-standard",
  "version": "3.0",
  "governed_component": "V",
  "exclusivity": "exclusive",
  "selector": {
    "kind": "instrument-reading",
    "procedure_ref": "site-QA-SOP-12"
  },
  "meta_policy": "within-tolerance: accept and record; out-of-tolerance: reject, tag, and escalate to the site engineer"
}

​
The metaorthemma: tok-B7-perp-1

The metaorthemma is the case-specific binding of perpendicularity-standard v3.0 to the concrete occurrence pillar-B7 (version as-poured-2026-07-01). It records the datum plane, the instrument identity and calibration provenance, and the binder’s warrant — kept explicitly distinct from the episode actor. 
{
  "token_id": "tok-B7-perp-1",
  "of_type": {
    "mu_id": "perpendicularity-standard",
    "mu_version": "3.0"
  },
  "analysis": {
    "analysis_id": "site-perpendicularity-check",
    "version": "2.1"
  },
  "anchor": {
    "identity_key": "pillar-B7",
    "version": "as-poured-2026-07-01"
  },
  "governed_component": "E",
  "binding": {
    "datum_plane": "floor-slab-datum-D2",
    "instrument": "level-114",
    "tolerance_value": 0.002
  },
  "instrument": {
    "id": "level-114",
    "calibration_provenance": "cal-lab cert 2026-06-20",
    "calibration_expiry": "2026-12-20"
  },
  "binder": {
    "actor": "site-engineer-2",
    "binding_warrant": "work-order-5512",
    "binding_time": "2026-07-02T08:00:00Z"
  },
  "validity": {
    "effective_from": "2026-07-02",
    "expiry": null,
    "superseded_by": null
  },
  "no_separate_executor_reason": "this token designates no executor separate from its binder: the episode actor executes under the same warrant, and the binder ROLE remains independently recorded"
}
The no_separate_executor_reason field is present precisely because the binder and executor roles share the same warrant here. The framework records the distinction even when the roles happen to be co-instantiated — the audit trail preserves which one to scrutinize if a failure arises.

​
The episode record

Actor fitter-9 takes four-face level readings using level-114 between 08:30 and 09:00 on 2026-07-02. Evidence item ev-1 records the channel, scope, and provenance. The placement is the two-axis factorized result: perpendicularity: within-tolerance on the exclusive axis, surface-condition: [clean] on the co-holding axis. The route is release-for-load-transfer. 
{
  "episode_id": "ep-B7-verify-1",
  "occurrence": {
    "identity_key": "pillar-B7",
    "version": "as-poured-2026-07-01",
    "kind": "structure"
  },
  "actor": "fitter-9",
  "warrant": "work-order-5512",
  "time": "2026-07-02T08:30:00Z/2026-07-02T09:00:00Z",
  "evidence": [
    {
      "evidence_id": "ev-1",
      "channel": "instrument-reading",
      "property_class": "behavioral",
      "scope": "claim-perp @ as-poured-2026-07-01",
      "provenance": "level-114 run 2026-07-02",
      "validity": "until next structural mutation"
    }
  ],
  "placement": {
    "perpendicularity": "within-tolerance",
    "surface-condition": ["clean"]
  },
  "route": "release-for-load-transfer",
  "action": "release"
}

​
Claim ledger

The ledger contains one placement claim — claim-perp — asserting that pillar B7 is perpendicular within 0.002. The claim explicitly records what it does not assert: no claim about surface finish is made from this episode. 
{
  "episode_id": "ep-B7-verify-1",
  "claims": [
    {
      "claim_id": "claim-perp",
      "proposition": "pillar B7 is perpendicular within 0.002",
      "target": {
        "identity_key": "pillar-B7",
        "version": "as-poured-2026-07-01"
      },
      "property_class": "behavioral",
      "evidence_ids": ["ev-1"],
      "depends_on_tokens": ["tok-B7-perp-1"],
      "verification_status": "validated",
      "non_claims": ["no claim about surface finish"],
      "claim_type": "placement"
    }
  ],
  "residuals": [
    {
      "burden_id": "b-1",
      "description": "verify perpendicularity",
      "disposition": "validated-resolved",
      "evidence_refs": ["ev-1"]
    }
  ],
  "closure_claim": {
    "level": "verification complete",
    "asserted_by": "fitter-9"
  }
}

​
Verdict record

The verdict record is the auditable output of the episode review, produced by site-qa-reviewer at 09:15 on 2026-07-02. Every verdict in required_path passes; ROBUST_NEIGHBORHOOD is recorded not-applicable with an explicit reason.
1

Result side: V1 and TOKEN_TRUTH_LINKED

RESULT_CORRECT (V1): pass — the placed profile within-tolerance is correct against the governed state. TOKEN_TRUTH_LINKED (V2b-T): pass — the claim is correct through the truth-relevant mechanism, not by accident.
2

Evidence pathway: V2a, V2b-P, V2c

EVIDENCE_SUPPORT (V2a): pass — ev-1 is typed, within scope, and meets the declared support standard. PROCEDURE_RELIABLE (V2b-P): pass — four-face digital level reading under SOP-12 has established truth-conduciveness. EVIDENCE_CURRENT (V2c): pass — the reading is current for as-poured-2026-07-01 and the calibration certificate has not expired.
3

Governance pathway: V3a–V3e

GOV_CONFIG_ADEQUATE (V3a): pass — the governing configuration is adequate for this risk class. GOV_POLICY_ADEQUATE (V3b): pass — the meta-policy is well-formed. GOV_TOKEN_ADEQUATE (V3c): pass — tok-B7-perp-1 is correctly instantiated, anchored, scoped, current, and provenanced. EXECUTION_FAITHFUL (V3d): pass — fitter-9 executed per the bound token. EX_ANTE_JUSTIFIED (V3e): pass — the decision was reasonable on the evidence available at the time.
4

Route and closure: V4a, V5

ROUTE_ADMISSIBLE (V4a): pass — release-for-load-transfer is admissible under the hard constraints (calibration is current; all four faces measured). CLOSURE_TRUTHFUL (V5): pass — the closure claim matches the burden ledger with no disposition collapse.
{
  "episode_id": "ep-B7-verify-1",
  "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"
  },
  "claim_verdicts": [
    {
      "claim_id": "claim-perp",
      "result_correct": "pass",
      "token_truth_linked": "pass"
    }
  ],
  "per_token_v3c": [
    {
      "token_id": "tok-B7-perp-1",
      "status": "pass",
      "failing_conjunct": null
    }
  ],
  "pathway_state": "adequate"
}
The claim reasoning path for claim-perp traverses all eight pathway verdicts from EVIDENCE_SUPPORT through EX_ANTE_JUSTIFIED and is recorded as adequate. This is what distinguishes a nominal (F1-shaped) episode from the correct-by-luck cell (F2): every link in the path from evidence to placement is independently auditable and passes.
The episode produces one successor: pillar-B7 version released-2026-07-02, action label release. The record mode is audit-ready, meaning the full claim ledger, evidence items, token record, and verdict record are all retained and cross-referenced. Minimal record mode (as in stopped-clock-validator) omits some of these references.

Build docs developers (and LLMs) love

Get started for freeTalk to us