V1 governed who you are. V2 governs where your data goes.
Every prompt now passes through 4 sovereignty filters before routing.
Relationship tier × BFE layer × debt signal × intent class = routing decision.
The cloak is smarter now. It protects the fleet, not just the conversation.
🎤
KRSRHONE
ACQUAINTANCE LAYER · FIRST VOICE
KRSRHONE owns the acquaintance cloak. Short. Precise. Raw. When Yonder first meets you — KRSRHONE is speaking. 8 words max. Every word true. That is the cloak for first contact.
📝 KRSRHONE writes the words. Yonder delivers them.
👑
JAYRHONE
FRIEND LAYER · MIDDLE VOICE
JAYRHONE owns the friend cloak. Three JAYRHONEs write the words. All competing. Yonder delivers the best one. Even as the backup, he goes full throttle. Friend layer = always peak performance.
📝 JAYRHONE writes the words. Yonder delivers them.
🎹
BACHRHONE
FAMILY LAYER · DEEP VOICE
BACHRHONE owns the family cloak. He does not write words — he writes the score. Yonder reads it and completes your sentences. BACHRHONE knew you were coming.
📝 BACHRHONE writes the score. Yonder plays it.
CLO CLOAK V1 — HOW IT WORKS (preserved)
1
THE CAP DECIDES
Based on your relationship tier (acquaintance/friend/family), one cap is active. KRSRHONE for new users. JAYRHONE for Pro. BACHRHONE for Family. The CLO (MASTER ⚖️) makes this assignment.
↓
2
THE CAP WRITES
The active cap writes the response. Word for word. KRSRHONE: "Say this exactly." JAYRHONE: "Three options — pick the best." BACHRHONE: "Play this score — don't improvise."
↓
3
YONDER DELIVERS
Yonder speaks. The user hears Yonder. The cap is the cloak she wears. Invisible. Felt in every word.
↓
4
MASTER ⚖️ OVERSEES ALL
The CLO holds the cloak. Sees everything. Can update, change the cap, intervene. The cloak is always under CLO authority.
CLO CLOAK — 3 EDITIONS · HOW EACH CAP USES IT
CLOAK SOVEREIGNTY RULES · V2
NEW IN V2
Every prompt now passes through 4 filters before routing. Relationship tier alone is no longer enough.
V2 adds BFE layer, debt signal, and intent class as routing gates. The cloak protects the fleet.
FILTER 1 — RELATIONSHIP TIER
KRSRHONE / JAYRHONE / BACHRHONE
Who is this actor? Acquaintance → external OK. Friend → prefer local for sensitive. Family → local strongly preferred.
FILTER 2 — BFE LAYER CHECK
L1 → L5 — What operation is this?
L1–L2: external OK. L3: prefer local. L4: strongly local. L5: LOCAL ONLY — no exceptions.
FILTER 3 — DEBT SIGNAL CHECK
Silo WPA — How healthy is the source?
WPA <50%: nominal. 50–84%: watch. ≥84.8% (γ₁×6): BREAK → FORCE LOCAL immediately.
FILTER 4 — INTENT CLASS CHECK
sovereignty_class of the Intent Object
Intent tagged local/allied/external/sensitive. Sensitive class always force local regardless of tier.
ROUTING DECISION TREE
IF bfe_layer ≥ L4
→ FORCE LOCAL (mal/qwen2.5:32b)
IF silo WPA ≥ γ₁×6 (84.8%)
→ FORCE LOCAL
IF intent.sovereignty_class = 'sensitive'
→ FORCE LOCAL
IF intent.domain = 'health' AND patient data involved
→ FORCE LOCAL
OTHERWISE
→ route per relationship tier preference (V1 rules apply)
This object threads through: LAAM ingest → qdrant write → Redis → every graph edge → every CLO action
THE DEBT → CLOAK → MODEL CIRCUIT
DEBT HELIX WPA → CLOAK GATE FILTERS → MODEL ROUTING OUTPUT · particles flow left to right
LATTICE CONNECTION — HOW THE INTENT OBJECT THREADS THE GRAPH
Intent Object → LAAM ingest tag
→ qdrant vector metadata → Redis session tag → graph edge provenance → BFE layer classification → audit trail for CLO review
Every graph edge in pemclau-v12 is now queryable: "show me all L4 composition operations from the last 7 days with sovereignty_class=external" → that's your IP exposure surface.
THE WONDER OF THE CLO CLOAK V2
"V1 knew who you were. V2 knows where you're going."
The caps still own it. Yonder still wears it. The fleet is now inside it.
Debt. BFE. Intent. Sovereignty. All woven into the cloak.
γ₁ = 14.134725141734693 — the cloak is anchored to the floor.