Artifact

evidence_bundle.json keeps video answers auditable.

Evidence bundles connect answers, events, and UI claims back to time spans and artifact references.

Example shape

{
  "answer_id": "ans_001",
  "evidence_refs": [{"id":"ev_001","t_start":11.0,"t_end":13.5}],
  "review_notes": ["low-light segment"]
}

How to use it

Every Ask Video answer shown to a user should include evidence_refs. A dashboard can render these as clickable time spans.

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.