Runs & Artifacts
RFC-003 run contracts, RFC-004 scientific axes, and the RFC-009 publication boundary.
Current Contract
A run is an execution record with an explicit kind, artifact contract, and failure semantics. Core stores the run identity and artifacts; executor services such as ECAM-X or Copilot return bounded outputs. The app reads the result and projects it into UI state. It does not invent artifacts when a run is incomplete.
No synthetic artifacts
Run Kinds
| Kind | Purpose | Expected Artifacts | Conformance Gate |
|---|---|---|---|
| ecamx | Evidence attribution for claim/evidence links | manifest.v1 + explain.v1 | ECAM-X minima: evidence links, NLI labels, similarity, judge config, negative controls, and CI disclosure. |
| aei_delta | Explanation stability under perturbation | manifest.v1 + stability.v1 | Stability-only contract: seeds, perturbations, delta distributions, confidence intervals, and sanity checks. |
| tca / tca_hitl | Human reliance and editorial trust calibration | manifest.v1 + trust.v1 | Trust-only contract: HITL decisions, override patterns, decision coverage, and calibration summary. |
| ecamx_bundle | Full analytic composition and Story Health fallback | manifest.v1 + explain.v1 + stability.v1 + trust.v1 | Hybrid contract: must satisfy ECAM-X, AEI-Delta, and TCA minima together. Not required by RFC-009 publication. |
| combined | Configured full composition | manifest.v1 + explain.v1 + stability.v1 + trust.v1 | Same full analytic contract as ecamx_bundle when all three axes are requested. |
| story_render | Narrative projection from story revision to reader/export body | manifest.v1 + story_spec.v1 + story_render.v1 + story_render_map.v1 + story_render_policy_report.v1 | Projection-only. It creates render artifacts; it must not fabricate analytic evidence, stability, or trust artifacts. |
Status Semantics
ok
Run completed and every artifact required by the run kind is present and schema-valid.
warn
Run completed with non-fatal disclosures. The UI may show the result, but must name the warning.
block
A policy or input precondition failed before execution. No synthetic artifacts may be emitted.
error
Execution failed. RFC-003 permits a manifest-only error record, but non-error statuses must satisfy the artifact contract.
Publication Boundary
RFC-009 publication is not just another run. It is an explicit Core-owned publication act that binds a story revision, render run, evidence links, and audit bundle into an immutable record. A publication can consume support metadata produced byecamx,ecamx_bundle, orcombined runs, but it does not require the bundle run kind itself.
| Publication identity | RFC-009 v1.1.0 adds Core-issued publication_id as the immutable publication act identity. |
| Required support | Publication requires publication-grade claim/evidence support metadata from explain.v1-compatible runs. |
| Optional support | stability.v1 and trust.v1 strengthen the publication record, but absence is disclosed as not measured. |
| Forbidden shortcut | The app, LINA, and browser must not mint audit bundles, publication IDs, or placeholder metrics. |
ecamx_bundle classification