Control room · Dashboard
The operating room for company knowledge health.
Source health, proof logs, approval risk, worker activity, and persistence status in the same calm control-room language as the Fable homepage.
What changed since the last source health check, and can this workspace answer with proof?
The workspace can answer from demo/local company knowledge, but the system still flags source gaps before relying on it. 1 of 4 sources are healthy, 170 indexed items are visible, and the dashboard keeps customer data unloaded while persistence status is checked server-side.
Healthy
1
Indexed
170
Persistence
unavailable
Company Brain
What should Innexios prove in the first demo?
Worker run
Summarize what the first Innexios demo must prove before any live integration.
Workers
3
Customer data
none loaded
Persistence foundation
Self-hosted DB boundary
DB mode: mock_fallback. Schema: innexios. DATABASE_URL is not set; using local/mock fallback with no persistence.
no browser database secrets, no hosted Supabase target, no live Onyx, no email sends, and no external actions.