Chassis lifecycle

What this package supports

The Chassis is a reusable, profile-driven execution engine that owns durable run state, ordered stages, retry/budget, run claims + concurrency, crash/handoff recovery, registered decision forks, deterministic resolution, fail-toward-asking elevation, append-only decision + dispatch logs, run-path containment, legitimate terminal states, and a codification sink. A consumer declares a profile (declarative data + seam wiring + procedure) and inherits all of it. The engine has exactly three active consumers — Auto Plan, Cure v2, and Cure v3 fix-pass. Auto Plan is an eight-stage profile. And in the Cure v2 operation, a reported finding with no persisted artifact blocks advancement — the artifact outranks the summary. (Technical companion §6, §8.)

Proves

the engine owns twelve named capabilities behind a purity boundary, each cited to the engine's own contract doc (engine-capabilities.md); a profile is a three-kind contract validated fail-closed, and three real consumer profiles exist and import the engine (consumer-profile-contract.md); Auto Plan's stage surface is an ordered eight-stage sequence (auto-plan-8-stages.md); and the Cure v2 §2.5 gate mechanically blocks advancement when an investigator's return summary claims findings its persisted manifest does not carry (artifact-outranks-summary.md).

Does not prove

any performance or reliability figure. This package evidences structure — what the engine owns, how a profile is validated, how many consumers exist, how the stages are ordered, and what one gate enforces — all of which is checkable by reading the cited source. It makes no claim about success rates, time-to-completion, or before/after measurement. The already-public reference package is explicit that no such numbers are published, and neither are they here.

↓ Download package (.zip)

8 files · 14.5 KB Every artifact, the manifest, checksums, and the full README — one archive.

Inside the archive — 8 files, 28.2 KB

File Size
artifacts/artifact-outranks-summary.md 3.8 KB
artifacts/auto-plan-8-stages.md 3.3 KB
artifacts/consumer-profile-contract.md 4.1 KB
artifacts/engine-capabilities.md 4.4 KB
checksums.txt 647 B
manifest.json 3.5 KB
README.md 5.1 KB
source-summary.md 3.4 KB

Full package README — claim, source provenance, redaction statement, reproduction

Claim supported: The Chassis is a reusable, profile-driven execution engine that owns durable run state, ordered stages, retry/budget, run claims + concurrency, crash/handoff recovery, registered decision forks, deterministic resolution, fail-toward-asking elevation, append-only decision + dispatch logs, run-path containment, legitimate terminal states, and a codification sink. A consumer declares a profile (declarative data + seam wiring + procedure) and inherits all of it. The engine has exactly three active consumers — Auto Plan, Cure v2, and Cure v3 fix-pass. Auto Plan is an eight-stage profile. And in the Cure v2 operation, a reported finding with no persisted artifact blocks advancement — the artifact outranks the summary. (Technical companion §6, §8.)

Claim IDs: E7-C001, E7-C002, E8-C001 Evidence level: exercised Access classification: Sanitized public excerpt (much of this is also publicly inspectable — see below)

What this package proves, and what it does not

Proves: the engine owns twelve named capabilities behind a purity boundary, each cited to the engine's own contract doc (engine-capabilities.md); a profile is a three-kind contract validated fail-closed, and three real consumer profiles exist and import the engine (consumer-profile-contract.md); Auto Plan's stage surface is an ordered eight-stage sequence (auto-plan-8-stages.md); and the Cure v2 §2.5 gate mechanically blocks advancement when an investigator's return summary claims findings its persisted manifest does not carry (artifact-outranks-summary.md).

Does not prove: any performance or reliability figure. This package evidences structure — what the engine owns, how a profile is validated, how many consumers exist, how the stages are ordered, and what one gate enforces — all of which is checkable by reading the cited source. It makes no claim about success rates, time-to-completion, or before/after measurement. The already-public reference package is explicit that no such numbers are published, and neither are they here.

Publicly inspectable companion

A public reference implementation of this exact architecture already ships at publications/chassis-reference/ (README.md, METRIC_PROVENANCE.md, examples/, excerpts/). It is a runnable, dependency-free engine + one example operation, plus nine production modules copied byte-for-byte under excerpts/. For the parts of this claim covered there, access is "Publicly inspectable." Per publications/chassis-reference/METRIC_PROVENANCE.md, the production engine is 25 source modules / 3,743 lines (excluding __tests__) with 3 consumers — a figure this package independently re-derived from the live tree at the source commit (25 modules, 3,743 lines).

Source

Reproduction