Distance-Time Kernel telemetry
Geometry-first distance, clockless chronology, gravity-wave baseline, photon-lane residuals, uncertainty, and sampling metadata.
Export Builder Contract
A public contract page for the ArcSecs integration reviewer that maps Distance-Time Kernel telemetry, Multi-Messenger Event Theater telemetry, Framework Claim Map state, validation ledger rows, and quality-gate state into the seven verified export outputs.

Direct answer
This page keeps export-builder scope explicit before the integration reviewer wires runtime export logic.
The export builder contract defines how live simulator telemetry becomes durable evidence artifacts.
The runtime integration should consume the contract JSON and TypeScript contracts, then produce all seven export outputs without dropping Operator Runbook, source references, caveats, falsification paths, UTC timestamps, speculative-boundary text, or finite telemetry guards.
Input mapping
The plugin should collect these live inputs before assembling export outputs.
Geometry-first distance, clockless chronology, gravity-wave baseline, photon-lane residuals, uncertainty, and sampling metadata.
Active event, actor graph, delay budget, counterpart confidence, missing-channel state, and scene timeline.
Claim nodes, support links, evidence weights, caveats, and claim-boundary labels.
Immutable validation rows with actor, action, hash, timestamp, result, and failure notes.
Gate results, thresholds, margins, warning/fail states, and regression summary.
Bibliographic entries, report links, retrieval hashes, caveats, and falsification paths.
Seven outputs
The Operator Runbook is a required export target, not an optional appendix.
Machine-readable metrics, time series, uncertainty, metadata, and scenario state.
Parameter set, calibration constants, methods, residuals, validity, and source constraints.
Validation results, margins, pass/fail state, warnings, and evidence summary.
Step-by-step usage, thresholds, operational guidance, caveats, and recovery notes.
Linked evidence artifacts, hashes, provenance, figures, tables, and validation rows.
Full analysis bundle, report references, figures, tables, datasets, and derivations.
Event-theater scene snapshot with active event, actors, state, geometry, timeline, and telemetry.
Implementation links
These are the theme-side files the ArcSecs Plugin Architect should consume.
docs/arcsecs-plugin-export-builder-handoff.md documents the expected plugin implementation behavior.
assets/ts/arcsecs-physics-engine/ExportBuilderHandoff.ts provides strict TypeScript contract mapping.