Five modes, one sky
Not pages. Ways of looking.
One map of your business, and five ways of looking at it. Observe, Ask, Investigate, Decide and Memory are not pages; they are what you do on the map.
- 01Observe
The whole business, at rest.
Points of light for every system you run. When Arden notices something, the points involved light up and connect, and the verdict reads beside them.
ARDEN — MISSION CONTROL · OBSERVELive
- 02Ask
Three subscribers, and one wholesale account.
Ask in plain language and the sky reorganises around the question. The answer is a verdict with the evidence beneath, every claim linked to the system it came from.
ARDEN — MISSION CONTROL · ASKLive
- 03Investigate
Five investigations open.
Arden digs on its own clock. Each investigation is a trail of checks with its source; open one and follow the light from the question to the decision.
ARDEN — MISSION CONTROL · INVESTIGATELive
- 04Decide
Three decisions need you.
The judgments that need a human, as a queue — and beneath it, what ran under policy without you. A cleared queue is a designed state.
ARDEN — MISSION CONTROL · DECIDELive
- 05Memory
What the organization has learned.
The Sunday brief, and the learnings with their sources: what was tried, what happened after, and what Arden now does differently.
ARDEN — MISSION CONTROL · MEMORYLive
One catch, end to end
9:14 AM. Arden noticed something.
9:14 AM. Shopify: order #4471 has sat unfulfilled for 41 hours, and its promise date is tomorrow.
One point brightens.
Illustrative. The systems are real; the order is not.
The decision detail
The trust surface, and the heart of the product.
Every decision carries the same five layers in the same order, so you can approve in ten seconds or read for ten minutes. Every resolution writes a learning to Memory.
- 01
Policy gate
Why this needs a human. “Shipping changes over $10.” Confidence stated next to it.
- 02
Headline and narrative
The verdict in Arden’s voice, and the one-paragraph case for it.
- 03
Evidence chain
Each claim paired with its source system. Hover a claim and the point that supports it lights up.
- 04
Blast radius
Before any approval: which system is written to, what changes, what it costs, how long it stays reversible, what the customer sees.
- 05
Governed actions
Approve, adjust among options with the recommendation marked, or decline with a reason. Declines teach Arden where the bar sits.
Business Memory
Your business already has the information. It doesn’t have the understanding.
What the systems say
- ShopifyJane Smith · 6 orders · last 11 days ago
- HubSpotJ. Smith · contact at Meridian · spring reorder due 14 Mar
- QuickBooksSmith, Jane · invoice #2291 · 21 days overdue
- Gmailjsmith@ · complained about a late delivery in March
- GorgiasJane S. · CSAT 4.6 → 3.9 across 12 tickets
What Arden knows
One customer, who has complained once and churned once, whose company reorders in March with an invoice three weeks overdue.
Where systems disagree, Arden asks instead of guessing: “Is J. Smith in QuickBooks the same person as Jane Smith in HubSpot?” Every answer becomes provenance-backed memory.