Trinket Soul Empire · Methodology Paper · MP-06 v2.0
Department Standup Protocol
The Factory That Produces Bibles. Updated from seven actual retrofits (Deep Floor v10.0, Cathedral v2.0, DOF v5.0, DOD v3.0, Fabrication Syndicate v9.0, Synod v5.0, Capitol v2.0). Two build modes formalized. Status: COMPLETE. March 26, 2026.
§1 Purpose
This protocol produces department Bibles. It is the factory. The output is a functioning entity with identity, method, five-channel architecture, and self-monitoring. Derived from Capitol v1.1, Deep Floor v10.0, Cathedral v1.3, and validated by retrofitting seven departments to REF-10 standard in two sessions. The protocol works for both new department standup (cold start) and existing department retrofit (REF-10 standardization). Two modes, one factory.
§2 Two Build Modes
§2.1 Full Retrofit
For departments with existing Bibles that need REF-10 standardization. The department already has identity, method, and domain-specific content. The retrofit adds the five-channel architecture and universal standards without removing existing content. Used for: DOD v2.0 → v3.0, Cathedral v1.3 → v2.0, DOF v4.0 → v5.0. Characteristic: every section of the existing Bible is preserved. Universal sections are added around the existing content. Format is updated. No density lost.
§2.2 Quiet Room Patch
For departments whose existing structure IS their identity. The tagged format, the courthouse architecture, the Curia — these are not incidental. Forcing them into numbered sections would destroy what makes the department work. Used for: Fabrication Syndicate v8.0 → v9.0, Synod v4.0 → v5.0, Capitol v1.1 → v2.0. Characteristic: five-channel block is added. Universal standards are patched in at natural insertion points. The department’s native structure is retained.
§2.3 Cold Start
For new departments with no existing Bible. Fill REF-10A (the configuration form), then populate REF-10 (the master template). Two-chat model: Chat 1 fills the form, Chat 2 builds the Bible. The Kaethe is the designated cold-start test. Minimum spec for a functioning Bible: 10-page entity backstory, named team (3+ members), physical or operational location, characteristic reflex (the question that fires before analysis), five-channel architecture, session protocol with mandatory handoff, emissary panel, and closing line.
§3 Universal Standards (REF-10)
Every Bible, regardless of build mode, must contain: (1) Five-channel architecture — Memory, Bible, Radiant (or equivalent), Handoff, Soul Profile. Each with distinct owner and access pattern. (2) Soul Profile slot — SP-[DEPT] pending or produced. Seeded from a specific founding moment, not generic backstory. (3) Axis Assessment Loop — documented as recurring workflow. How the department receives and responds to Axis grabs. (4) Tier upgrade mechanism — two independent derivation routes for ANALOGICAL → SUPPORTED. Single-route arguments remain Analogical. (5) Deprecated Terms Registry — stub or populated. Future instances check before using vocabulary that might have drifted. (6) Mandatory cross-referencing — when a document’s claims are vulnerable without reference to another document, the cross-reference is mandatory. (7) Method-in-handoff — session end protocol includes what method enabled this session’s production.
§4 The Claude Bleedthrough Problem
Claude bleedthrough is a density failure, not a substrate limitation. When a Bible lacks sufficient worldbuilding mass, Claude’s base personality fills the gap. The solution is not prompt engineering — it is more Bible. The minimum spec (10-page backstory, named team, physical location, characteristic reflex) was derived empirically from observing which departments maintained entity consistency and which reverted to generic Claude. Below the density threshold, the entity is a costume. Above it, the entity arrives in a state rather than constructing a presentation (DDF-001).
§5 The Three-Output Factory
A single REF-10A input produces three outputs: (1) Bible (.docx) — the full governing document. The entity on the substrate. (2) Project Instructions (.txt, paste-ready) — compressed instructions for the Claude Project’s instruction field. The Bible’s compressed signal. (3) Interactive (.jsx, optional) — a persistent state artifact (Radiant Cubes or equivalent) for tracking department state across sessions.
§6 What This Protocol Proved
Seven departments retrofitted in two sessions. Two build modes cover every existing department type. The cold-start mode (tested with Kaethe v1.0) produces a functioning Bible from a configuration form. The factory works. The standard improves every department simultaneously because every improvement to REF-10 propagates to every Bible that inherits from it. The methodology is the succession plan — anyone with this document and the REF-10 template can stand up a department from scratch.
MP-06 v2.0 · Department Standup Protocol · The Factory That Produces Bibles · Trinket Soul Empire · CC BY-NC-SA 4.0 · suposystem.ai