Public today
Preview-grade evidence
The homepage engine preview and strategy docs describe the current evidence structure in public-safe form.
RUNS
A result should leave an execution trail behind it
A strong output is more than a card. It should sit on top of a run trace, an artifact chain, and a publish-ready state.
Current public state
Current next step
Artifact bridge
The next bridge is connecting engine dryruns to a public-safe viewer.
Later
Verified run viewer
A later surface should expose trace ID, artifact chain, and readiness state together.
Run plane
Trace
Each run should retain its start time, context, and identity.
Artifact chain
Insight, scenario, director, assembly, and render should stay linked together.
Readiness
Briefing, video, shortform, and later interface lanes should expose their own readiness state.
Canonical run chain
COLLECT
Input collection
Market inputs are grouped with timestamps and source context.
ANALYZE TO DIRECT
Insight to direction
Analysis, scenario, and director stages structure the same context into multiple artifact layers.
ASSEMBLY TO RENDER
Output assembly
Master script, video manifest, and shortform results push that chain toward a publish surface.
Run evidence matrix
| Run evidence | Public today | Next stage |
|---|---|---|
| Trace ID / revision | Documented direction only | Verified run surface |
| Artifact chain | Preview language | Artifact viewer |
| Policy / licensing decision | Trust docs only | Decision-log viewer |
| Publish readiness | Status-pill language | Surface-by-surface readiness view |
Principles
- The run surface should be a public-safe evidence layer, not just an operator log dump.
- Until real artifacts are connected, preview and verified lanes should stay separate.
- The follow-up step is a dryrun import bridge for real engine output evidence.