The Boneyard
The Boneyard is the library and authoring cockpit for reusable prompt ingredients: installed element packs, generator BONE contracts with live readiness badges, prompt recipes, and marketplace packs. Provider quirks belong in portable contracts — not scattered through chat history.
ZERO-KEY FLOOR: PIPER TTS · ARCHIVE.ORG · WIKIMEDIA · PEXELS · PIXABAY
ITS OWN COCKPIT
The Boneyard manages BONEs, prompt ingredients, recipes, and packs independently from the production. Each contract declares its requires[] capabilities and shows honestly whether it can generate today. When a better model ships, you author or install a new contract, point the shot at it, and the story structure never moves. Marketplace packs — elements, prompts, bones, production kits — install and log; they never execute.
Boneyard surfaces
Installed JSON element packs — cameras, lenses, lighting, palettes — grouped by category and tag, with custom authoring.
Installed generator contracts with armed / needs-setup / unavailable readiness badges and JSON inspection.
Prompt recipe stubs and modifiers from installed prompt packs.
The dedicated contract editor with live schema validation, governance fields, and starter templates.
Install element packs, prompt packs, bone packs, and production kits.
Start from installed packs, marketplace categories, or a custom .bone.json contract in the BONE Builder.
Set fields, UI hints, target, provider, prompt assembly, output, LLM instructions, and requires[] capabilities — validated live.
Every contract shows armed / needs-setup / unavailable by joining its requires[] against the capability matrix.
Swap model contracts without rewriting the story structure. Director fills them in Shot Builder.