Product guide / Strategy
your bets and assumptions, on the record
Agents propose. People decide. The record keeps both.
The company’s strategy spine — bets, charters, hypotheses, signals, decisions, experiments — where an agent can read everything, propose anything, and write nothing without a human signing for it.
Where this helps
Strategy documents go stale because keeping them current is nobody’s job. Handing that job to an agent is worse — unless the agent can only propose, and a person has to sign.
The question it puts in front of you
Do we accept this proposed change to what the company believes?
Where judgment belongs
Every strategy record is approved, edited, or rejected by a person, and what you changed while reviewing is recorded next to what was originally proposed.
What gets prepared for you
Agents read the whole spine freely and route every write through a proposal, so a suggestion arrives as a reviewable diff instead of a silent edit.
Strategy & decisions
How a proposal becomes a record.
Capture six typed records — bet, charter, hypothesis, signal, decision, experiment — on governed company lists.
Review each proposal against the original values, and against anything you edited mid-review.
Approve, reject with a reason, or let it expire — every resolution keeps its receipt.
Open the impact lens before retiring a bet, to see what depends on it.
Strategy in the real world
If this bet dies, what else just became suspect?
An agent can read every bet and assumption you hold, and change none of them. It proposes; the Workbench shows you the proposal next to what was there before, notes anything you edited while reviewing, and keeps a receipt either way.
The impact view reads the other direction. Pick a bet and it shows what depends on it, and what depends on that. Retiring a bet stops being a line-item edit and becomes a question the team has to answer out loud.
What holds up
What it does well, and what it was never meant to do.
Constraints are a design position, not an apology. Everything on the left ships today; everything on the right we decided against.
What you can rely on in Strategy
- Six record types: bet, charter, hypothesis, signal, decision, experiment.
- Agents can read all of it and change none of it without your approval.
- Each proposal is pending, approved, rejected, or expired, and keeps a receipt either way.
- The impact view only ever shows you what you already have access to.
What we chose not to build
- An agent cannot write a strategy record directly. That is the design, and there is no bypass.
- The impact view is a list today, not a visual graph.
- The six types are fixed. This is a strategy record, not a general-purpose database.
- Approving a proposal records a decision. It does not execute one.
Works with
Where Strategy hands the work on.
Decisions rarely stop where a product does. These are the guides that pick the work up next.
For your company
See how Operalta fits your company.
Bring one current decision or process. We will map it together.