◊ OPERATOR · structured strategy
v1.0 · sovereign single-file · MIT

Structured strategy · without the £1M deck.

McKinsey's frameworks are public. Porter. 7S. BCG. Minto. The IP is in every business-school textbook. What you pay for is the polish · and the brand on the cover. OPERATOR runs the playbook, sovereignly, with audit-chained provenance on every claim, and outputs a board-ready deck outline you can polish in 30 minutes.

the 5-phase engine
1

Diagnose

MECE issue tree · hypothesis pyramid · the question before the answer
2

Research

Multi-source evidence · 3-vote adversarial verification · killed-claims list
3

Frame

Porter 5 · McKinsey 7S · BCG matrix · Value-Driver Tree · auto-filled from research
4

Synthesize

7-strand strategy weave · contradiction detection · risk-scored options
5

Deck

Minto pyramid · slide outline · markdown · reveal.js · Konomi-signed envelope
how it differs from a McKinsey engagement

Same frameworks · half the cost ceiling · cryptographic provenance.

  • Every claim is hash-chained. SHA-256 prevHash on every research entry. If a finding gets edited later, the chain breaks. Provenance built in.
  • Every deliverable is Ed25519-signed. Against your Konomi keypair. Client verifies "this exact analysis came from you at this exact time, untampered."
  • Adversarial verification on every claim. 3-vote pattern. Refuted claims get listed openly · same honesty pattern that won audiences for nhs-reinjection.
  • MIT open source. Fork it. Self-host. Brand it your firm's name. Same engine.
  • Sovereign. Single HTML file. Works offline. No backend. No leaking client data to a SaaS.
for builders

Engine extraction follows the GroundLevel ripple pattern.

v1.0 is the PWA. SDK · Worker REST API · CDN <script> shim · MCP server · Obsidian plugin all on the roadmap. Same audit chain · same Konomi signature · same fall-signal mesh. See src/pro-slot.md for the swap contract.

engagement

Untitled

MECE issue tree

Decompose the question · mutually exclusive · collectively exhaustive

Root = the question · branches = sub-questions you must answer · leaves = specific data you need.

hypotheses

Initial hypotheses (top-down)

Start with what you'd recommend if you knew nothing. Research either confirms or kills each hypothesis.

research base · evidence per sub-question

Build the evidence base.

For each sub-question (from your MECE tree), paste research · cite the source · vote each claim as confirmed, refuted, or pending. Refuted claims get listed in the killed-claims section · same honesty pattern that built credibility for nhs-reinjection.

killed claims (the credibility builder)

What we refuse to publish.

Refuted claims are listed openly · pre-empts the analyst who would otherwise discredit your whole report.

no killed claims yet
frameworks · structured analysis

Apply the canonical frameworks.

Industry attractiveness · score each force L/M/H, paste evidence.

Organisational fit · the 7 elements that must align for execution to land.

2x2 matrix · market growth (vertical) × relative market share (horizontal). List business units, services, or product lines in each quadrant.

⭐ Stars · high growth · high share
❓ Question marks · high growth · low share
🐄 Cash cows · low growth · high share
🐕 Dogs · low growth · low share

Where the cash actually comes from. Revenue × Margin - Capital intensity. Find the highest-leverage driver.

7-strand synthesis · the operator's lens

Cross-cutting analysis.

Same weave pattern that powers GroundLevel · re-skinned for strategy. Each strand asks a different question about the recommendation. Contradictions between strands flag where you've missed something.

Overall risk score

Click "Compute risk" to score the synthesis.

Algorithm: average of strand-evidence-density minus contradiction penalty (same scoreRisk pattern from groundlevel-sdk). Output: STRONG / MODERATE / WEAK / INADVISABLE.

minto pyramid · deck output

Top-down storyline.

Governing thought → 3 key arguments → 3 supporting data points each. The McKinsey deck structure. Output as markdown, JSON, or signed reveal.js HTML.

◊ governing thought (the one-line recommendation)
output
past engagements

History.

Every engagement is audit-chained · final hash sealed at "Finish" · Konomi-signed envelope exportable as JSON for client provenance.

configuration

Settings.

◊ Konomi identity

Ed25519 keypair generated on first boot via libsodium-wasm · stored in IndexedDB · signs every engagement envelope.

statusinitialising…
public key—
created—

κ ledger

current balance0
lifetime earned0
engagements completed0

BYOK · LLM cascade (optional)

For auto-fill of MECE trees, framework synthesis, and storyline generation. Key stays in localStorage · only sent to the provider you pick.

Sister tools in this browser

Tools that emit on fall-signal.

listening…