The headline drift: the belief model was flattened
When you say "beliefs" you mean doc 544, a signal-based belief map built for diagnosing a live investor. The database replaced it with a generic 5-stage marketing-awareness journey. These are different ontologies, and the richer one, the one that lets a transcript be scored and a call be routed, is the one that did not make it into the brain as structured data.
544 — your model (what got left behind)
~18 belief signals + states + routing + gates
- Qualification: QT (tax rate), QL (liquidity)
- Core C1–C4: problem real / unsolved / EIS understood / risk accepted
- Persona clusters: G1–G3 Growth Seeker · L1–L2 Legacy Builder · P2–P3 Preserver
- Situational S1–S6: credible / considering / valuation / team / terms / timing
- States: Green / Amber / Grey / Red / N/A
- Gates: C4 compliance gate · Pack 1 gate (S2+C4+score≥70)
- Routing table: belief → exact content asset
→
Brain — what's there now
5-stage awareness funnel
- BS1 Unaware → BS2 Problem Aware → BS3 Solution Aware → BS4 Committed → BS5 Advocate
- One linear axis, marketing-stage shaped
- No signal states, no gates, no per-belief routing
- Cannot answer "what does this investor believe right now"
- Cannot enforce the C4 compliance gate
Continuity worth noting: the G / L / P persona clusters did survive, as the persona E-axis (E1 Preserver, E2 Growth Seeker, E3 Legacy Builder, E4 Undetermined) across the 10×4 persona matrix. So the persona half of 544 is intact; the belief-signal half is what's missing. And every rendering was re-tagged to BS1–BS3 only, so the original per-asset belief code (330 = C2, 380 = G1, 490 = S6, 430 = S1) was dropped: 0 of 19 renderings carry a 544 belief code.
~190
Brain entities migrated
~55
Correctly excluded (ops)
Migrated well
What came across cleanly (credit where due)
The substrate layers are solid. This is not a failed migration, it is a partial one.
Atoms, renderings, personas, pillars, channels, recipes, compliance
The content substrate is largely intact
Present in the brain
01_acus 24 (facts + expression variants + 2 prohibited)
02_renderings 19 content pieces (330–550 series, original IDs kept)
03_personas 51 (P1–P10 × E1–E4 + bases) — G/L/P preserved as E-axis
04_pillars 8 (CP1–CP8) · 05_channels 9 · 08_recipes 28
07_compliance 8 constants · 11_campaigns 1 (CAMP-001 EIS Oct 2026)
Verdict
The atomic content layer migrated faithfully and the renderings kept their original 330–550 IDs (good continuity). The gap is not in the substrate, it is in the operating system that sits on top of it.
Genuinely / practically missing
Whole layers the brain was built without
These are not naming-drift artefacts. They are referenced by docs that did migrate, but the things themselves are absent.
Critical
The belief-signal operating system (544–551, 235, 530)
The instrument that makes signals work, entirely absent as brain entities
Missing from the brain
545 Belief Map Framework V4 — governing definitions + routing philosophy + gap register
546 Signal System Spec — Werner's data model + gate logic (the bridge doc)
547 Question Sequence (25 Qs) — each question mapped to a belief signal
548 Demo Run Order V3 · 549 Three-Call System · 551 Post-Call Protocol
235 Belief-Map Email Templates · 530 Agent Quick Reference
search result: 544 codes appear only in 2 methodology docs + 1 HTML render, 0 structured rows
Why it matters
This is exactly what you were circling at the start of the session, "what beliefs must an investor hold, scored from a transcript." The brain literally cannot do it because the signal definitions, the question→signal map, the states and the routing table are not in it. 546 is also the natural Tom→Werner bridge: it is the build spec for the data model.
Critical
The C4 compliance gate (doc 140 Access Explainer)
A non-negotiable gate with no home in the brain
What 544 says
"C4 compliance gate: If C4 is not green, send 140 — Access Explainer ONLY.
Nothing else. No Pack 1. No valuation content. No founding round terms."
In the brain
Doc 140 (Access Service Explainer) is not a rendering. The gate is a hard compliance rule, and it is not represented as a constant in 07_compliance either. The brain has FCA-perimeter and capital-at-risk constants, but not the behavioural gate that governs what may be sent before risk is understood.
High
The investor-pack / conversion layer (100–199)
The brain holds only top-of-funnel content; the closing assets are absent
Missing renderings
100 One-pager · 110 Three-pager · 120 Pack 1 · 130 Pack 2 IIM
150 EIS Secret Weapon · 155 EIS Investor Guide · 160 Five Case Studies
170 IHT Planning · 180 Fee Comparison · 181 Portfolio Stress Test
182 BPR Explainer · 197 FAQ · 198 Exit Strategy · 199 Market Opportunity
confirmed: NONE of the 100-series present in 02_renderings
The practical break
rendering belief_stage spread: BS1 ×6 · BS2 ×6 · BS3 ×7 · BS4 ×0 · BS5 ×0
Why it matters
544's routing table sends 140, 150, 120, 160, 170, 180, 181, 182 at specific belief states, and the brain cannot serve any of them. Every piece in the brain sits in the top three stages; there is nothing for Committed (BS4) or Advocate (BS5). The brain is currently an awareness engine with no closing kit.
Medium
Behavioural + sequence pieces (450, 540, 470)
Signal-bearing assets dropped from the renderings set
In matrix, not in brain
450 Social Proof E03 — S1 credibility belief (testimonial sequence)
540 Clicked-Not-Booked — the behavioural re-engagement branch
470 Voicemail Drop VM1 — cold-outreach voicemail
440 Rate Response template
note: brain kept 460 (Final E05) + 550 (Urgency E04) but dropped 450/540 from the same sequence
Why it matters
450 carries the S1 credibility signal and 540 is the behavioural branch your email-sequence logic depends on. Partial sequence migration means the nurture arc has holes mid-flow.
Would add value
Not strictly missing, but worth bringing across / building
These restore capability rather than just files.
Reinstate the belief-signal layer as a brain entity type
Make C1–C4 / G/L/P / S1–S6 first-class alongside (or instead of) BS1–BS5
The move
Add a belief-signal table (codes, definitions, states, persona-cluster mapping) so the brain holds your actual model. Decide whether BS1–BS5 stays as a coarse marketing overlay or is retired. This is the single highest-leverage change: it re-enables transcript scoring and call routing.
Re-tag every rendering with the belief signal it resolves
Rebuild the routing table the migration dropped
The move
The original tags still exist in the matrix descriptions (330 = C2, 380 = G1, 400 = P2, 430 = S1, 490 = S6, 500 = L2…). Re-applying them as a resolves_signal field restores 544's "one belief → one asset" routing with almost no new authoring, just re-tagging from a known source.
Signal states + gates as queryable rules
Green / Amber / Grey / Red + the C4 and Pack 1 gates
The move
Encode the five states and the two non-negotiable gates as rules the brain can enforce, so "what may I send this person now" is answerable from data, not memory. This is where 546 (the signal spec) becomes the Werner build target.
Bring across the content-gap register (960) + ACU register
The matrix already tracked its own gaps
The move
Doc 960 (Content Gap Build Plan) and the ACU Register already enumerate known gaps with priority + owner. The ACU register sits in 09_strategy but 960 does not. Pulling it in gives the brain a self-aware backlog instead of re-deriving gaps each time, like this audit had to.
Correctly excluded
Not gaps — these belong elsewhere
Roughly 55 of the 138 files are project ops, not content. They should not be in the content brain, do not flag them as missing.
Governance, CRM, roadmap, migration + build-spec docs
OS-vault material, not content-brain material
Examples (rightly absent)
000–012 index/governance/design-bible · 200/210 Pipedrive+Aircall setup
600/601 agent + UAT team specs · 950–996 roadmap / CRM maps / driver tree
964/965 migration protocols · ERD + database specs · session summaries
Note
A few sit on the boundary and are judgement calls for the session: 701 Compliance Language V4 (the single source of truth for approved/prohibited terms, the brain has only 8 constants vs the full register), 520 19-Persona Guide (vs the brain's 10×4 matrix, reconcile or retire), and 655 EIS Glossary (maps to the GLO Tier-B class). Worth a yes/no each, not assumed.
Naming drift to reconcile
Renderings kept their original 330–550 IDs, which is good. But the ID space collided across eras: 530 means three different things, original 530 = Cold Call Open CS1 (agent script), original 530 = Agent Quick Reference (in the 500-series), and brain 530 = Email ColdE1A Universal. Similarly 400 is both a content piece (Correlation Audit) and a tech spec (Decumulation Engine). Any re-import needs an ID-collision pass first, or the routing table will point at the wrong asset.
Next steps
A sequenced plan — in dependency order
Each step names an owner and what unblocks it. Steps 1–2 gate everything else; do them first.
1
Decide the belief-model authority Tom + Werner
Pick the canonical model: reinstate 544's signal map (C1–C4 / G·L·P / S1–S6 + states + gates) as the brain's belief layer, with BS1–BS5 either retired or kept as a coarse marketing overlay. This blocks steps 2–6. Output: a one-line decision logged to Intelligence/decisions/.
2
Import 546 Signal System Spec as the build target Werner
546 is the bridge doc — investor-profile object, data model, gate logic. Werner builds a belief_signals table (code, definition, state enum Green/Amber/Grey/Red/NA, persona-cluster mapping) plus a gates rule for C4 and Pack 1. Depends on step 1.
3
Re-tag the 19 renderings with resolves_signal Tom low effort
The original tags survive in the matrix descriptions (330=C2, 380=G1, 400=P2, 430=S1, 490=S6, 500=L2…). Re-apply them as a field — re-tagging, not re-authoring. Restores 544's one-belief→one-asset routing table.
4
Encode the C4 compliance gate + Pack 1 gate as enforced rules Tom + Werner compliance-critical
Add to 07_compliance: "until C4 green, only 140 Access Explainer may be sent." Add Pack 1 gate (S2 green + C4 green + score ≥70). Makes "what may I send now" answerable from data.
5
Bring the conversion layer into renderings Tom authoring
Priority order, matching the funnel hole (BS4/BS5 empty): 140 Access Explainer first (gate-critical), then 120 Pack 1, 130 Pack 2 IIM, 150 Secret Weapon, 160 Case Studies, 170 IHT Planning, 180/181/182. Each gets ACU dependencies + a resolves_signal tag on creation.
6
Backfill the behavioural / sequence pieces Tom
450 Social Proof (S1), 540 Clicked-Not-Booked (behavioural branch), 470 VM1. Closes the holes mid-nurture-arc that partial sequence migration left.
7
Run an ID-collision pass before any re-import Werner do before 5–6
530 means three different things across eras and 400 is both a content piece and a tech spec. Resolve the ID space first, or the routing table points at the wrong asset.
8
Reconcile boundary docs + pull the gap register Tom + Werner
Yes/no each: 701 Compliance Language (full register vs the brain's 8 constants), 520 19-Persona Guide (vs the 10×4 matrix), 655 Glossary (→ GLO Tier-B). Import 960 Content Gap Build Plan so the brain carries its own backlog.