Secure meeting room

Consultation agenda and room scaffold with recording and transcript disabled by default.

UI scaffoldOpen cockpit

Synthetic principal scenario. All identifiers are reserved or fictional. No real people are scraped or enriched.

Authorized scopeHuman approval requiredNo live scrapingNo external sendingNo real personal data

One authorized client, one real exposure-defense loop, zero fake actions.

Human consultation resolves ambiguous approvals and partner handoffs.

Principal

Jordan Hale

synthetic-principal-001

Findings

case-state fallback

StealthScore

54 -> 78

rubric estimate

External actions

human approval required

Loop proof

Evidence that this screen supports the Jordan Hale defense loop.

agenda

pre-call checklist

post-call notes

no call history

State declaration

No surface claims a live action that is not wired.

UI scaffoldProtected actionHuman reviewWaiting client

Any outside-world touch remains protected, gated, or dry-run. Scaffolded controls can acknowledge intent locally but do not send, provision, upload, scan, call, publish, or mutate external systems.

Capability proof

Route-level proof that this screen stays inside the Jordan Hale loop.

operate

Jitsi consultation room

Protected action

A consultation room card that shows the agenda and privacy settings before a real meeting link is created.

Real today

The route shows a room placeholder and agenda; recording and transcript are disabled by default.

Scaffolded

Jitsi IFrame API embedding, room creation, invite delivery, and calendar scheduling are protected future integrations.

Agenda

Recording disabled

No call history is faked

No meeting room is created

externalActionTaken: false. No external action is triggered from this route.

human_review

Human review center

Human review

The approval desk where sensitive decisions wait for a person before they can leave the system.

Real today

The review cards are deterministic and show local approval requirements without executing external workflow steps.

Scaffolded

Approvals, rejections, escalations, and partner notifications require protected mutation endpoints and audit persistence.

Review queues

Decision reasons

No auto-submit

No external message is sent

externalActionTaken: false. No external action is triggered from this route.

Support mode

Capabilities

Docker

Vercel

Postgres can persist support and audit facts locally or on Vercel. Deployments without DATABASE_URL stay public-safe and degraded.

integration

External service actions

UI scaffold

Local Postgres: degradedVercel: degraded

Jitsi, Twilio, SendGrid, Cloudflare, AWS, SCC, scan, and submit tools all return implemented:false.

Every external action remains scaffolded/protected until intentionally wired.

externalActionTaken: false

safety

Responsible-use gates

Connected

Local Postgres: supportedVercel: supported

Sensitive UI controls and MCP tools state human approval and externalActionTaken:false.

Safety gates remain active in fixture mode.

externalActionTaken: false

Defense loop ledger

Principal, evidence, risk, work, approval, report, and recurrence stay tied together.

Stages

Findings

Evidence

Approvals

External actions

Principal

3 aliases, 2 cover entities, and 2 reserved contacts are fixture-backed.

Discovery

12 curated findings across 6 source classes.

Evidence

12 evidence records, 12 redacted, 12 protected by default.

Risk

StealthScore moves 54 to 78; average finding risk is 59; top risk is EXP-001.

Work

12 tasks across 5 lanes; 2 need partner help.

Cadence

6 milestones from Day 0 to Day 30.

Action

2 packet drafts, all generated by template fallback and all unsent.

Approval

7 high/critical findings and 2 packet drafts require human review.

Report

11 active findings, 2 pending packets, 5 recurrence-watch items.

Recurrence

5 findings have recurrence likelihood at or above 0.70.

Principal context

The only subject in this demo is synthetic.

Name: Jordan Hale
Role: Synthetic executive principal
Risk posture: Elevated public-profile risk with family, property, business-entity, and credential-exposure concerns
Authorization: Synthetic or client-authorized only

Work objects

Only objects that advance the defense loop are shown.

EXP-001

Aggregated people-search profile with home + relatives

EXP-002

Property record links residence to principal name

EXP-003

Reserved mobile number indexed against principal

EXP-004

WHOIS-style metadata exposes personal email

EXP-005

Officer filing names principal at residential address

Packet posture

Drafted does not mean sent.

PKT-003Human review

Privacy request

No message sent. No takedown submitted.

PKT-004Human review

Takedown notice

No message sent. No takedown submitted.

Related findings

Synthetic exposure objects connected to this surface.

EXP-002CriticalValidated

Property record links residence to principal name

Highest physical-risk exposure in the case.

EXP-005CriticalWaiting partner

Officer filing names principal at residential address

Requires legal/trust partner remediation.

Guarded interactions

All sensitive controls are honest scaffolds.

Create consultation room

No external action taken from this UI phase.

Protected action

Evidence, risk, work, approval, report

The single loop remains visible from every route.

Discover

12 findings

Evidence

12 records

Score

54 -> 78

Operate

12 tasks

Prove

report + trace