Artifact

timeline.json gives dashboard and agents temporal order.

Timeline artifacts help applications navigate long footage by event order rather than raw frames.

Example shape

{
  "events": [{"t": 11.0, "type": "entered_zone", "evidence_refs": ["ev_001"]}],
  "semantic_refresh": [{"t":10.8,"reason":"new object enters zone"}]
}

How to use it

Use timeline.json for event navigation, jump-to-time links, semantic refresh views, and replay controls.

Review posture

Do not treat an artifact field as a final decision. Pair important artifact claims with evidence references, confidence, detector warnings, and human review boundaries when the workflow is high-risk.

A good product surface links the artifact to the user interface. When a reviewer clicks an event, the UI should show the timestamp, supporting evidence, confidence, and any detector warning. When an answer is generated, the same evidence should be visible. This makes debugging possible and prevents the documentation from becoming a theoretical schema list that developers cannot operationalize.