Story Beat
beat.schema.json
The rules
JSON Schemas
12 document schemas define every typed object in the pipeline — projects, transcript units, claims, clips, beats, shots, timelines, decisions, provenance records and QA issues. All are draft 2020-12, cross-referenced through a shared definitions file, and enforceable through the public validator.
This material is a specification and reference set with a reference rule engine. It is not an editing application, a rendering pipeline or a completed production, and the worked example is entirely fictional — it exists to demonstrate the method.
Claim
claim.schema.json
Clip Candidate
clip.schema.json
LAKA Media Common Definitions
common.schema.json
LAKA Production Decision
decision.schema.json
Production Rules File
production_rules.schema.json
LAKA Media Project
project.schema.json
Media Provenance Record
provenance.schema.json
QA Issue
qa_issue.schema.json
Shot Plan or Captured Shot
shot.schema.json
Semantic and Editorial Timeline
timeline.schema.json
Transcript Unit
transcript_unit.schema.json
Validate a document
POST {"schema": "clip", "document": {...}} to /v1/validate and the document is checked against the named schema — required fields, enumerations, patterns, ranges and cross-file references — with readable error paths.
curl -s https://video.bowtiekreative.com/v1/validate \
-H 'content-type: application/json' \
-d '{"schema":"claim","document":{"claim_id":"clm_001"}}'