PSEUDONYM ENGINE
SOVEREIGN IDENTITY LAYER · GID INTENT GATE · CLO CLOAK BACKED · TRIAL v1
Every person in the ONBA / CLO system has a sovereign name token — the name that appears on every public-facing page, system, and communication. The real legal name is masked behind the token.
The GID Intent Gate evaluates inbound requests: why does this caller need the real name? Court order → reveal. Investigation → CLO review. Curiosity → block. Harassment → block + flag.
This is the trial. Submit an intent. Watch the gate decide.
The GID Intent Gate evaluates inbound requests: why does this caller need the real name? Court order → reveal. Investigation → CLO review. Curiosity → block. Harassment → block + flag.
This is the trial. Submit an intent. Watch the gate decide.
SOVEREIGN
NAME TOKEN
e.g. "Gee"
→
NAME TOKEN
e.g. "Gee"
GID
INTENT
SCAN
→
INTENT
SCAN
INTENT
CLASSIFIER
legal/admin/priv/harm
→
CLASSIFIER
legal/admin/priv/harm
CLO
GATE
if borderline
→
GATE
if borderline
REVEAL
or MASK
decision
or MASK
decision
🎭 Sovereign Name Registry — Live Subjects
⚡ INTENT GATE TRIAL — Submit a Request
CALLER IDENTITY
TARGET SUBJECT
STATED INTENT / REQUEST
📋 Intent Gate Log
No requests yet. Submit an intent above.
📐 GID Intent Classification Rules
✅ REVEAL — Legal Authority
Court orders, enforcement writs, CRA/WSIB/government tax authority, PPSA registry searches with matter ref, CLO bench internal review. Real name released to caller. Audit log entry created.
⚠️ CLO GATE — Borderline
Banks, insurers, commercial creditors, media with valid inquiry, employers with consent. Intent forwarded to CLO bench for review. Sovereign token used until CLO approves. Max 24h response.
🚫 BLOCK — No Authority
Anonymous callers, social media, unknown parties with no credentials. Token only. Real name never released. Request logged. Repeat attempts escalate to flagging.
🛡 CLOAK — Threat Detected
Harassment signals, stalking patterns, repeated probing, bad-faith requests. Subject notified. Caller flagged in CLO Cloak registry. Sovereign data lockdown for this caller permanently.
🎯 How This Protects CRIGATOR Users
The problem we just had: Gee's full legal name appeared on a public page because the build pipeline had no identity gate. Anyone who googled the page saw his real name linked to asset enforcement work — a safety and privacy risk for a bailiff/repo operator.
What the Pseudonym Engine fixes:
For CRIGATOR specifically: Gee's enforcement work means people he's chasing know who he is. Keeping his preferred name separate from his legal name on public platforms is not bureaucracy — it's operational security.
What the Pseudonym Engine fixes:
- Every ONBA member is registered with a sovereign token (preferred name)
- All pages, UIs, roast pages, crew spirals → token only
- Legal name is stored encrypted, never rendered in HTML
- Any system that needs real name → must pass GID Intent Gate
- CLO bench reviews borderline cases → audit trail created
- The pre-deploy name-scan hook checks new HTML for known real names before push
For CRIGATOR specifically: Gee's enforcement work means people he's chasing know who he is. Keeping his preferred name separate from his legal name on public platforms is not bureaucracy — it's operational security.