Content Production System is a file-driven operating system for launch narrative, demo planning, content workflows, expert routing, and governed evidence. It starts from a route-context fixture so the project has route-context, memory, protocol, expert, evidence, and Aming Claw governance boundaries before product-specific code is added.
system-fixture/contains the instantiated route-context baseline.system-fixture/map/system-map.jsondefines domains, files, dependencies, and graph reconcile hooks.system-fixture/route-context/owns visible route context and action policy.system-fixture/protocols/defines starter file-backed protocols.system-fixture/experts/defines routed expert lanes for content work.system-fixture/memory/defines private feedback and lesson boundaries.system-fixture/evidence/defines dispatch, merge, and close evidence gates.system-fixture/governance/binds this system to Aming Claw backlog, graph, timeline, and close gates.content-system/defines the first content production video demo contract: brief, storyboard, shot list, and reproducible capture/render pipeline.
The first governed content artifact is a technical product demo for the content production system itself. The demo shows how a fuzzy video goal becomes an expert-routed content plan, then a backlog-backed production contract with evidence checkpoints.
Core artifacts:
content-system/demo-brief.md: audience, claim, duration, route evidence, and done definition.content-system/storyboard.md: scene-by-scene story with evidence checkpoints.content-system/shot-list.md: recording plan for each visible capture.content-system/render-pipeline.md: reproducible capture, narration, caption, assembly, and verification flow.content-system/test-scenarios/: executable scenario contract and current satisfaction/toolchain reports for media E2E readiness.content-system/capture-plan.md,content-system/narration-script.md, andcontent-system/captions/: source-controlled inputs for future CLI capture, voice, caption, and render automation.
Run:
python -m unittest discover -s testsThe tests confirm every JSON config parses, all manifest paths exist, route context exposes visible alerts and role policy, and the governance, expert, memory, and evidence layers are present.
Recommended project id: content_sys
Reviewed bootstrap excludes:
.git.pytest_cache__pycache__node_modulesdistbuild.expo.nextcoverage