ANNABELLE'S COGNITION PAGE

An AI orchestration dashboard for the business — built, not yet live.

This is Annabelle's cognition page: ten parts of the business mapped around her, built to show how work would route for owner review — and why, not just what. The screen runs in the product today; the orchestration layer that would feed it live activity is not connected yet.

Built and running — orchestration layer not yet connected

What it is

Ten parts of the business around her. She routes the work — she is not just another box on the screen.

Most dashboards show you what happened. This one is built to show you why — the actual reasoning behind a decision Annabelle already made, two clicks past the headline number. Construction PM, Pool Service Ops, Visual Records, Route & Dispatch, CRM, Billing, Compliance, Vendor & Procurement, Comms, Team Room — every part of the business she runs, mapped around her.

The screen

It exists. It is also, right now, sitting still.

This is the page in the running product, not a rendering of it. All ten systems are on the graph with Annabelle at the core. Every one of them reads STANDBY, the counters read zero, and the header says ORCHESTRATION RECONNECTING — the screen is built, and the layer that would feed it live work is not connected yet.

Annabelle's cognition page in the Stinger Command Center — graph view with Annabelle at the center and the ten platform systems around her (Construction PM, CRM, Pool Service Ops, Route and Dispatch, Visual Records, Billing, Team Room, Vendor and Procurement, Comms, Compliance), each labelled STANDBY. The header reads ORCHESTRATION RECONNECTING, the inspector shows Annabelle with the orchestration layer offline and zero actions, active, and pending, and the flow ledger reads No hops recorded yet.

Command Center · 2026-08-31 — 10 systems, 1 agent, 0 active. Nothing here is staged: the zeros are the real state.

The concept

The shape of the page.

Annabelle at the center, with ten parts of the business — Construction PM, Pool Service Ops, Visual Records, Route and Dispatch, CRM, Billing, Compliance, Vendor and Procurement, Comms, and Team Room — around her, connected by thin lines. Construction PM Signed jobs, punch lists, inspections Pool Service Ops Recurring routes, chemistry, equipment Visual Records Site photos matched to the property Route & Dispatch Tech assignment, licensing, radius CRM Accounts, dosing plans, hazard checks Billing Invoices, payments, the GL Compliance Licenses, certifications, expirations Vendor & Procurement Subcontractors, purchase orders Comms Calls, texts, notifications Team Room The model fleet, live sessions ANNABELLE routes the work

A schematic, drawn for this page — the product's own version of it is in the screenshot above. The ten system names are the ten the product actually carries. No numbers appear here because, with orchestration offline, the real screen has none to show.

Drill-down

Overview → system → reasoning. Two clicks, not twenty.

1. Overview

Ten parts of the business, one glance. Jobs open, routes running, invoices out. Nothing more until you ask.

2. System

One level in. The live queue for that system — what's moving, what's waiting, what needs a human to look at it.

3. Reasoning

Not a log dump — the actual reasoning. What she checked, what she found, what she did next, in her own words.

The flow it's built to trace

Signed job → serviced customer.

Chosen because it's genuinely live in the product today — not staged for a demo. Making this chain watchable end to end is what the page is for; the ledger stays empty until the orchestration layer starts reporting the hops.

1 A signed job hits its final build stage — inspection passed, punch list clear. Construction PM
2 Job auto-converts to a service customer. Site access, GPS, and equipment carry over — nothing re-typed. Pool Service Ops
3 Route optimizer slots the first weekly visit for the nearest licensed tech. Route & Dispatch
4 Arrival photo logged and matched to the property record automatically. Visual Records
5 First chemistry reading logged. Dosing plan calculated, hazard-checked, sent to the tech. CRM

What's built vs. what's connected

Honest about the line, on purpose.

The flow is real

The construction-to-service conversion above already runs in the product — site access, GPS, and equipment carry over automatically when a signed job becomes a service customer. The screen that would show it happening is built too. It has not watched a single one yet: the ledger reads "No hops recorded yet" because nothing is reporting into it.

The panels are there; the data isn't

Inspector, reasoning pane, activity stream, flow ledger — all present, all empty. Actions 0, active 0, pending 0, last event a dash. We would rather show you the zeros than a seeded number that makes the page look busy.

What's left is the connection

The remaining work is the orchestration layer — the thing that reports each hop as Annabelle makes it. Until that lands, the header keeps saying RECONNECTING, and we keep saying it out here too.

Get started

Want to see where this is headed?

Talk to Vincent about where the Cognition Page fits your rollout — or see what's already shipped across the rest of the lineup.

Talk to Vincent See the full lineup

Related

Part of the same AI-tooling lineup.

The Cognition Page draws on the same orchestration Annabelle uses across the platform, and it shares its AI-tooling neighborhood with Teams and Forge.

Stinger Teams, the multi-model AI room Stinger Forge, the AI coding workspace See the full Stinger platform