Operating review

Sides

Owners, accountable Roles, Role agents, Watchers

Unit of work

The Goal tree and the review that ends in a Decision

Examples

• Dashboard and analytics, for the Business itself

The five tests

1. who signs in
2. which record dominates
3. who acts next
4. how money moves
5. who may settle what

Carried only by it, from What every App needs

The review that ends in a Decision; target authority; the agent context block as a first rendering; owner-private scenarios

Screens its Interfaces name, by reader

Founder, every reader

The Situation · money in and what the Business keeps · the drill path from a number to its formula, Events, Actions and Verbs

Founder, Plan teammates

The Goal tree with derived progress, pace, machine status beside a human override with reason and owner, confidence as a named judgement

Analyst, accountable Role

Metric page · watch rules

Weekly review

Weekly Test and Office Hours · Role reviews per filled seat · the review run with its frozen reading and one disposition per signal · the closing Decision

Product and Growth Roles

Experiments with the Hypothesis, assignment, exposures, stopping rule and readout · the workbench

Founder, Finance Role

Forecast and runway, the spend state it sets, projections with method and interval, scenarios labelled as scenarios

Watcher, Studio

Pending feed of Actions in a delay window · Portfolio review with sample sizes, Cohort against control, brakes, Traction

Role agents, native clients

none

Build today: the Site pages around it

• stats
• facts
• article Template

9actors6workflows9records

An Operating review is the App where a Business steers itself by its numbers. Its readers answer for outcomes: the owner, operator cofounders, the accountable Role behind each Metric, the Role agents that read their measures on every wake, and the parent's Watchers.

It holds the Goal tree with pace, exceptions, watches that act, Experiments, product analytics and forecasts. It shows agent and work performance only at the grain the measurement policy allows. Its review cadence ends in a Decision, and its scope is one Business, a Portfolio or a Studio.

Earlier studies folded executive and KPI dashboards into Admin as Views. This type undoes that. The study describes the work; how an App is defined is open, see What every App needs.

• Owner or founderWorkReads the Situation, sets and moves targets, names objectives, closes reviews with Decisions, arms watches
• Teammates with Plan accessWorkEdit Goal names, targets, periods and the Hypothesis link; never values
• Accountable RoleWorkAnswers for one Metric; its seat is reviewed weekly
• Role agentsWorkRead their Role's View as a context block on every wake; are measured by their Role's results
• Office Hours agentWorkHolds the weekly review with the founder and writes the Decision
• AnalystWorkDefines and watches Metrics; answers questions with the query shown
• WatcherWorkPauses, redirects or cancels pending Actions, each a Decision
• Studio operatorWorkReviews the Portfolio by exception; trips and lifts brakes
• Owner-private readerWorkValues the Business, runs scenarios, solves for "what must be true"

1. 01
   Workflow 1: The first reading

   1. 1.1The Founding Hypothesis becomes the root, and its Minimum Success Criteria its one Goal, with one Metric that reads honestly: unmeasured, source not live, or a valid zero.
2. 02
   Workflow 2: The weekly loop

   1. 2.1The Weekly Test ranks the Hypothesis's open questions and compiles the week's one Experiment.
   2. 2.2Role reviews run per seat, and Office Hours on Friday writes the Decision.
   3. 2.3The quarter ends with a review that freezes a reading.
3. 03
   Workflow 3: The monthly review

   1. 3.1It waits for the books to close, or runs on a flagged estimate.
   2. 3.2A late refund shows as a restatement, never a silent change.
4. 04
   Workflow 4: A watch fires

   1. 4.1On the edge, once, per environment: it opens a Worklist item, switches an agent to assist or pauses a campaign.
   2. 4.2A watch demotes freely and promotes only through the eval gate.
5. 05
   Workflow 5: Runway sets the spend state

   1. 5.1A Forecast after a large money Decision moves spend to tight or hold, and other Systems read it.
6. 06
   Workflow 6: The Studio reviews its Portfolio

   1. 6.1Per-Startup readings with sample sizes, Cohort against control, and brakes that skip the delay window.

Metric definition5 states

1. declared
2. measured or unmeasured
3. versioned on change
4. retired
5. a rename maps every reader

Reading11 states

1. present
2. absent with a reason
3. withheld by class
4. unconfirmed
5. provisional
6. partial
7. early
8. unset
9. failed
10. not run
11. none renders as zero

Key Result2 states

1. value read from its Metric
2. machine status beside a human override with a reason

Review run6 states

1. scheduled
2. gathering
3. dispositioned
4. objective named
5. closed with a Decision
6. an off-cycle run starts when a strategic watch trips

Watch rule5 states

1. off or on
2. armed
3. fired (writes an Action)
4. re-armed when false
5. per environment

Hypothesis, Experiment8 states

1. stated
2. testing
3. supported or refuted
4. designed
5. running
6. stopped
7. concluded ship
8. kill or iterate

Role Review3 states

1. one per filled Role per week
2. immutable
3. with the seat's rung after it

Forecast4 states

1. computed weekly
2. sets the spend state free
3. tight or hold
4. scored on its read date

Brake3 states

1. tripped with a reason and effects
2. lifted or expired
3. resolved by a Decision

Why it is a typeCopy Anchor Link

A Metric is always derived and never typed in. An Admin form over Metrics lets an operator type a value, and Event, Metric, Funnel and Goal as CRUD tables is what flattening analytics into Admin produces.

The type is expressible two ways: as the analytics part of the operator's App, beside Admin and the Worklist, or as an App of its own. A Portfolio review spans Startups no single shell holds. A law practice reading its morning view needs the type without any operator shell.

ActorsCopy Anchor Link

Every reader is also a subject: the founder's Key Results are read by the Office Hours agent, and a Role agent reads the Metric it is judged by. That is why the measurement policy is part of the type, not a filter added later.

InterfacesCopy Anchor Link

A Dashboard is the View this App renders at a scope's address, not the App. Editing a Metric's definition or a Goal's target is a Change in Admin, and this App links to it and shows its effect on readings.

Records and actionsCopy Anchor Link

Verbs: define, query and watch a Metric; ask a question and get the query beside the answer; set or move a target; override a status; test a Hypothesis; conclude an Experiment; review a Role. A review closes with a Decision, and a Decision is superseded, never edited. A Watcher pauses, redirects or cancels, and the Studio brakes and lifts.

TermsCopy Anchor Link

Terms9 quoted from startupbuilder.dev · 1 it lacks · 1 colliding

Term	In startupbuilder.dev	Definition, quoted from startupbuilder.dev or the gap
Metric	Metric	"A Metric is a named measure computed from Events or Entries, always derived and never typed in."
Goal	Goal	"A Goal is what a Thing is trying to achieve: an objective with one or more Key Results."
Key Result	Key Result	"A Key Result is one measurable target inside a Goal: a Metric, a baseline, a target, and a deadline." No Verb sets or moves its target.
Dashboard	Dashboard	"A Dashboard is one unified view of a scope, rendered as Markdown for Agents, screens for Humans, and JSON for native clients." What this App renders, not its name.
Decision	Decision	"A Decision is the immutable record of a choice: its options, the choice, the reason, who decided, and the stakes."
Role Review	Role Review	"A Role Review is a dated check of one Role against its contract: its results, its standards and its autonomy rung." Over a seat one human fills, it is per-person attainment.
Hypothesis	Hypothesis	"A Hypothesis is a belief about a Startup stated so it can be proved wrong, with the Metric and threshold that settle it." Read for any Business.
Forecast	Forecast	"A Forecast is a dated week-by-week projection of a Startup's cash, revenue and Cost, computed from its records, that sets its spend state."
Policy	Policy	"A Policy is a ruling a Startup declares on how its numbers are computed or its choices made, such as revenue recognition."
KPI	lacks a Noun	A relation: a Metric a Thing has chosen to watch. business-as-code makes it a record with typed-in values.
Watch rule	collides	startupbuilder.dev's Watch is an outbound Event subscription.
Reading, pace, polarity, grain, review run, disposition, scenario	lack
Review, Scorecard	collide, retired	Review has five senses; Scorecard is retired in favour of Role Review.

WorkflowsCopy Anchor Link

1. The first reading. The Founding Hypothesis becomes the root, and its Minimum Success Criteria its one Goal, with one Metric that reads honestly: unmeasured, source not live, or a valid zero.
2. The weekly loop. The Weekly Test ranks the Hypothesis's open questions and compiles the week's one Experiment. Role reviews run per seat, and Office Hours on Friday writes the Decision. The quarter ends with a review that freezes a reading.
3. The monthly review. It waits for the books to close, or runs on a flagged estimate. A late refund shows as a restatement, never a silent change.
4. A watch fires. On the edge, once, per environment: it opens a Worklist item, switches an agent to assist or pauses a campaign. A watch demotes freely and promotes only through the eval gate.
5. Runway sets the spend state. A Forecast after a large money Decision moves spend to tight or hold, and other Systems read it.
6. The Studio reviews its Portfolio. Per-Startup readings with sample sizes, Cohort against control, and brakes that skip the delay window.

BoundariesCopy Anchor Link

• Plan and Strategy are private to the owner and Plan teammates, never on the Site, a portal or the API.
• Customers appear in aggregate. A named account appears only in an owner-private rendering.
• Agents are measurable in full, except a rate on a key a named human deputized.
• Employees under the employer regime are read by object, step, Site and window, never per person. "Average hours per person" fails that rule.
• A Role Review of a human-filled seat published to every Team is per-person attainment by another route; the conflict is recorded, not resolved.
• A roll-up recomputes ratios, never averages them, and an aggregate over rows the reader may not see is withheld.
• Benchmarks across Startups need a floor the owner has not ruled.
• Every reading names its reporting entity and its Policy.

AgentsCopy Anchor Link

Agents assemble every reading, rank exceptions, draft the review packet, run Experiments, Forecasts and Role reviews, and answer questions. A model never writes a figure: it routes the question to a declared Metric and cites it. An agent never varies the Metrics or Evaluators it is judged by.

A person names objectives and moves targets where a human founder exists, and approves spend beyond the envelope. A change to a figure an outside holder has seen goes to the disclosure room as a correction.

Hard partsCopy Anchor Link

1. Honest readings. Absent, withheld, unset, failed and zero are different; a source error never renders as 0, and a stale value never shows healthy.
2. Target authority. The founder sets targets, but no record says who else may, how an agent founder does, or that an agent never moves its own target.
3. Two registers. A goal register allows targets and pace; an evidence register refuses them. The refusal belongs to the View's audience, not to a field.
4. One Task store, four measured subjects. Agent track records, performers' Registers, Role reviews and the review read the same Events under different rules.
5. Counting rules. Outside revenue against run-rate revenue over everything; two NRR methods. Every reading names its Policy, and two north stars coexist without either replacing the other.
6. A review that ends in no Decision is ceremony. The close refuses an undispositioned red signal.
7. Budgets for agents. A 150-token block carries Needs you, pace and exceptions without truncating dishonestly.
8. Physical work arrives as Events. Gaps from unattested devices render as gaps, and grain stops at Site and window for employer-directed human work.

Day oneCopy Anchor Link

For an idea-stage founder, day one holds:

• the Founding Hypothesis and its one Goal, read from one Metric, with no typed-in values;
• the Situation: Needs you, the Goal with pace, exceptions, money in;
• the context block for every Role agent, before any screen;
• the weekly loop: the Weekly Test, one change a week, Friday's Decision;
• drill to records for every number, and questions in chat;
• Test and Live apart, and a daily briefing that notifies only on blocked, missed or stale.

An owner-operated practice uses the same type with no Studio: matters and deadlines by object, Goals that hold or break, and no review ritual beyond the owner's.

Related studiesCopy Anchor Link

Prototypes this study needsCopy Anchor Link

1. 01

   Can one record-and-Verb definition yield several side projections?

   One services-as-software Business written twice, as types only, with four projections including its own Operating review. Count duplicated declarations.

   names: Operating reviewnames: review
2. 02

   Does one measurement guard hold every per-person view?

   Run a performer's Register, a firm roster, a team queue, capacity per credential, a Role Review of a human seat and a deputized agent key through one guard; output pass, own, withheld or fail per audience.

   names: review
3. 03

   Can a watch change autonomy safely?

   A watch that drops an agent from full to assist; check the Decision, the re-arm and the next context block.

   names: Decision
4. 04

   Is a type a definition-level concept or a preset?

   Build the operator console, the Operating review's shell and an owned-edge desk from shared parts only.

   names: Operating reviewnames: review