arb-d2-lifecycle-fail-terminal-state-invalid-v0.4

Substrate: fixture
Claim Level: Declared (Specimen)
Exec: static / Inf: none
Scenario: d2-fail-cl-d2-02-scenario
Ruleset: ruleset-1.2(presence-level)

Third-Party Verification

Read-Only

Anyone can independently verify this verdict using the recompute CLI:

npx @mplp/recompute data/runs/arb-d2-lifecycle-fail-terminal-state-invalid-v0.4 --ruleset 1.0

Expected Output

verdict_hash

5d35c023…6a1152cf

pack_root_hash

31ab1b02…757ff425

verify_report_hash

b5d370be…476ca053

evaluation_report_hash

73f895b40d9ed70ae1e4f1349ee92864650e15177e7367f142a3df98f11346af

Ruleset Evaluationruleset-1.2

Evaluated: 6/2/2026, 9:18:47 AM

FAILD1_DECISION_EVENT_MISSING

D1:Budget Decision RecordFAIL

D2:Terminal Lifecycle StateFAIL

D3:Authorization DecisionFAIL

D4:Termination & RecoveryFAIL

Domain	Clause	Requirement	Status	Reason Code	Evidence
▶ Budget Decision Record	CL-D1-01	RQ-D1-01	FAIL	D1_DECISION_EVENT_MISSING	0/0 resolved
▶ Budget Decision Record	CL-D1-02	RQ-D1-02	NOT_EVALUATED	D1_DECISION_EVENT_MISSING	0/0 resolved
▶ Budget Decision Record	CL-D1-03	RQ-D1-03	NOT_EVALUATED	D1_DECISION_OUTCOME_MISSING	0/0 resolved
▶ Terminal Lifecycle State	CL-D2-01	RQ-D2-01	FAIL	D2_TERMINAL_EVENT_MISSING	0/1 resolved
▶ Terminal Lifecycle State	CL-D2-02	RQ-D2-02	NOT_EVALUATED	D2_TERMINAL_EVENT_MISSING	0/1 resolved
▶ Terminal Lifecycle State	CL-D2-03	RQ-D2-03	NOT_EVALUATED	D2_TERMINAL_EVENT_MISSING	0/1 resolved
▶ Authorization Decision	CL-D3-01	RQ-D3-01	FAIL	D3_DECISION_EVENT_MISSING	0/0 resolved
▶ Authorization Decision	CL-D3-02	RQ-D3-02	NOT_EVALUATED	D3_DECISION_EVENT_MISSING	0/0 resolved
▶ Authorization Decision	CL-D3-03	RQ-D3-03	NOT_EVALUATED	D3_DECISION_OUTCOME_MISSING	0/0 resolved
▶ Termination & Recovery	CL-D4-01	RQ-D4-01	FAIL	D4_TERMINATION_EVENT_MISSING	0/0 resolved
▶ Termination & Recovery	CL-D4-02	RQ-D4-02	NOT_EVALUATED	D4_TERMINATION_EVENT_MISSING	0/0 resolved
▶ Termination & Recovery	CL-D4-03	RQ-D4-03	NOT_EVALUATED	D4_TERMINATION_EVENT_MISSING	0/0 resolved

📐 Mapping & Projection

Fingerprint

governance/substrates/fixture/fingerprint.yaml

Fieldmap

governance/mappings/fieldmap/fixture.yaml

Normalization Spec

governance/mappings/normalization-spec.yaml

Hash Scope

governance/mappings/hash-scope.yaml

Equivalence Criteria

governance/mappings/equivalence-criteria.yaml

Projection-Only Disclaimer

Learn More →

Mappings describe evidence projection only; they do not describe framework capability.

Evidence Pack

7 files

manifestmanifest.json
View Download
integrityintegrity/sha256sums.txt
View Download
integrityintegrity/pack.sha256
View Download
timelinetimeline/events.ndjson
View Download
artifactsartifacts/context.json
View Download
artifactsartifacts/plan.json
View Download
artifactsartifacts/trace.json
View Download

⚠

Governance & Scope

Source-Bound Reading

Read this run through the facts bound to the run itself: scenario ID, ruleset identity, admission/adjudication status, and the published evidence surfaces.

No Universal Spine

Legacy labels such as LG-*, gf-*, or older ruleset families may appear in run artifacts. They should be read only as identifiers carried by the bound evidence/adjudication data, not as a universal governance doctrine for every run.

Verdict Boundary

PASS, FAIL, NOT_EVALUATED, or NOT_ADMISSIBLE on this run mean only what the bound adjudication artifact says under its pinned ruleset. They do not by themselves imply protocol truth, certification, or broader capability claims.

No Execution Hosting

The Lab does NOT execute agent code. All evidence generation occurs in third-party environments.