---
# /blocks/performance/ - the operator's cockpit: the always-on view, NOT a
# block. Kept deliberately short; the recurring management pack (an artefact
# on a clock) is its own loop - see reporting.md. Canon excludes the cockpit
# from the block map: it is the substrate's interface to the operator.
title: 'The operator’s cockpit'
slug: 'performance'
object: 'The live state of the business - the view every block reports into.'
pain: "I can't tell how the quarter is actually going without asking three people."
description: 'The live state of the business, read rather than built - assembled continuously from the same sourced record the blocks run on.'
metaTitle: 'The operator’s cockpit: the live state of the firm'
related:
  - 'reporting'
  - 'product'
order: 99
cockpit: true # the operator's cockpit - shown apart from the object-loops
noindex: false # launched 2026-07-24
---

# The operator’s cockpit

**The live state of the business, read rather than built** - not a loop among
the others, but the view every block reports into.

---

## What it is

This is not a block. It is what the foundations themselves do once they are
in place.

Every block runs on a shared spine of signals and one continuously-learning
brain that holds every object in the business: the accounts, the invoices,
the matters, the obligations. The cockpit is that record, read. There is no
cycle, no assembly and no sign-off - you look, and it is current. *"How is
the quarter going?"* is answered from the live record rather than from
somebody's recollection or a document built three weeks ago, with each figure
carrying its source, so drilling from a number to the records underneath it
takes one step.

Where the pack you distribute is an artefact produced on a clock - assembled,
challenged, signed off - that is a loop of its own, and it is
[the reporting block](/blocks/reporting/). The cockpit is the surface beneath
it: always on, always current, answering the question the moment it is asked.

## Where it comes from

You do not buy the cockpit. It arrives with the first block you build,
whichever that is - because the same spine and the same brain that run the
loop are what the view is read from. One block gives you the live picture of
that object. Each block after it widens the view, at no additional cost,
because the foundation is already there.

That is also why it cannot sensibly be bought on its own. A cockpit with
nothing underneath it is a dashboard: a picture assembled from wherever the
numbers happened to be, as stale and as unsourced as the systems it scraped.
The value is not the screen. It is that everything behind the screen is one
governed, continuously-maintained record.

## What it surfaces

A leading indicator, ahead of the lagging one. Usage dipping across three
accounts, invoices ageing on the same names, a renewal window opening ⇄ the
account and cash loops. The revenue number still looks fine; the cockpit
surfaces why it will not in ninety days, with the evidence attached, while
there is still time to act.

Every figure states where it came from and how fresh it is - an order the
operator can read, and an auditor or a board can examine.

## Where to start

You start with a block, not with the cockpit. Pick the loop where the pain
concentrates, and the view comes with it.

Take [the ten-minute diagnostic](https://benchmark.somai.studio), or write to
[hello@somai.studio](mailto:hello@somai.studio?subject=The%20operator%27s%20cockpit),
or see [what we build](/blocks/).

---

<small>Runs on [our framework](/ai-native-company/) · related reading:
[Most AI spend never reaches the P&L](/thinking/most-ai-spend-never-reaches-the-pnl/)</small>