On this page
The Black Vault
Ideas before they become canon. Creator decisions before they get lost in a thread.
Start with the session register and 15 October: the hidden city. The repository is the source of record; the creator-authorized website mirror is at The Black Vault. It is not a new fictional organization or an in-world database.
Capture a session
Say “Vault this” and supply the idea. Create sessions/YYYY-MM-DD-short-name.md from TEMPLATE.md, assign the next BV-YYYY-NNN ID, and append it to sessions.json. Multiple ideas may share a session but each decision must have its own status. Preserve the creator's words where useful; label assistant elaboration.
Statuses: captured, exploring, creator-directed, production-adopted, canon-confirmed, parked, superseded. An interesting idea is never promoted automatically. Record date, source, affected story/production files, dependencies, contradictions and the next decision.
Promote deliberately
- Creator direction goes into
docs/current-decisions.mdwith its scope and date. - A selected production method goes into the current protocol or production register.
- A story change reaches the bible/edition/atlas only through a named revision. A future-part idea does not rewrite the current ending by implication.
- Link the implementing commit back to the session. Keep the original idea when it changes; add a superseding decision.
Creator authorization, 15 October 2026: publish this Black Vault and its current sessions as an unlisted, noindex website area, accessible to anyone with its URL. Keep idea statuses and explicit promotion records. This exception does not publish production codes, credential vaults or unrelated Studio-only classified material. Protocol ZIPs remain workflow/template kits; sessions are published separately. This is a capture convention and repository system; it is not an automatic background recorder of every chat.
