ClassifiedThe Intelligence Loop · v1.0 Doctrine
00The Intelligence Loop

Four acts, repeating quietly, forever.

The loop begins the day you provision the house and does not end until the last asset departs. Everything below runs in production, today, in your color scheme, on your schedule, in your timezone.

I

Provision the House

Admin onboarding · 6 minutes

The principal — usually the CHRO, COO, or founder — creates the organization inside the console. Domain, timezone, cadence, and the initial roster are established in a single provisioning flow.

Roles are assigned from a strict hierarchy: sovereign, consul, analyst, observer. The scanner grants no privilege by default; the doctrine grants none by omission.

provisioning.log
▸ organization created  
▸ region · tz · Europe/Beirut  
▸ retainer · Sovereign tier  
▸ roster · 214 assets imported  
▸ role · sovereign granted to admin@…
II

Seed the Court

Employee enrollment · Telegram-native

A single invite link is generated per organization. HR distributes it however they distribute anything else — Slack broadcast, email, printed onboarding packet. Employees tap the link, land in a Telegram bot conversation, and confirm.

No app to install. No password. No pretext. Adoption in every rollout so far has exceeded 90% within seven days because Telegram is where employees already are, and the act of joining feels like nothing.

Chessboard Bot
Welcome. You have been enlisted into Acme Holdings. Reply anything to acknowledge.
telegram_link · confirmed · asset_id #4471
III

The Games Begin

Behavioral scenarios · timezone- and cadence-aware

Each asset receives short behavioral scenarios directly in Telegram — decision dilemmas, allocation puzzles, reaction prompts. Scenarios are personalized by typology and department, respect send windows and org timezones, and never repeat within a 30-day window.

The engine ships with a 35-scenario starter library covering Sales, Engineering, Operations, Legal, C-Suite, and cross-department dynamics. Sovereigns may extend the library or hand-author scenarios per role.

Scenario #017 · The Reassigned Account

Your largest account has been reassigned to a peer, without notice. You have thirty seconds before the client dials in. What do you do?

Confront
Absorb
Delay
response captured · latency 4.2s · vector recorded
IV

The Ledger

Real-time telemetry → typology, friction, playbooks

Every response is scored across dominance, autonomy, diplomatic register, sycophancy, and authenticity. Assets resolve into named typologies. Departments resolve into a friction matrix. Anomalies surface as insider-threat alerts in the systemic signal feed.

By the time the principal opens the console on Monday morning, the court map is already redrawn — and, if requested, a communication playbook is waiting for the week's most consequential meetings.

Signal
217
Flagged
12
Aligned
84%
24h telemetry · streaming
V30-Day Cadence

A month of scenarios, tuned to your organization's tempo.

Frequency
1–3 scenarios / week / asset
Send Window
Configurable, per timezone
Response Latency
Captured to the millisecond
Scenario Pool
35 seeded · unlimited custom
"Measure often enough to be current, seldom enough to be invisible. The signal you extract from the tenth question is worth more than the first nine combined."
Rule of Cadence

The loop is running. The only question is whether you are watching it.

Request Access