AnchorWorks The Briefing Room On the record
AnchorWorks
Executive Brief 009 · July 3, 2026

The War Board, Reconciled

Prepared by Chris Campbell AnchorWorks
The Briefing Room · 2026
  • Source of Truth Divergence doctrine§ Executive Decisions · Decision Log

    when the tracker and the record disagree, believe the record; a tracker only earns trust if it is reconciled.

  • Three-surface source-of-truth model§ Executive Summary

    the Miro War Board is the design intent (the revenue engine as designed); the Notion War Board is the execution tracker (what is being built); and the Executive Brief Cloud is the accurate record (what shipped, and why).

See every standing order in the SOP Library →

The executive summary.

The company's single source of truth had quietly split. The Notion War Board — our execution tracker — had drifted behind reality, while the Executive Brief Cloud had become the accurate record of what actually shipped. This brief closes that gap: the tracker is realigned, the design blueprint carries a plain "you-are-here" view, and the discipline that keeps them honest is written into doctrine.

Three surfaces, each with one job, are now named and separated: the Miro War Board is the design intent (the revenue engine as designed); the Notion War Board is the execution tracker (what is being built); and the Executive Brief Cloud is the accurate record (what shipped, and why). The governing rule: when the tracker and the record disagree, believe the record.

We didn't just update statuses. We restored one honest picture of where the company actually is — and made the gaps impossible to hide.

Current stage: Launch. Eight of sixteen revenue-engine components are live or substantially complete; the remaining gap is the Sales / monetization layer, now explicit and owned rather than buried in a stale board.

What was decided.

  • Named and separated the three surfaces: Miro = design intent, Notion War Board = execution tracker, Executive Brief Cloud = accurate record.

    locked
  • Adopted the Source of Truth Divergence doctrine — when the tracker and the record disagree, believe the record; a tracker only earns trust if it is reconciled.

    locked
  • Reconciled the Website Launch system from a stale 32% to ~90%, marking 21 git-verified tasks complete.

    locked
  • Resolved the KPI Intelligence System contradiction ("Done" at 0%) — set to 100% with a note that it was delivered via the Supabase KPI Command Center build (Briefs 004–007), off its own board.

    locked
  • Deliberately left 10 tasks open rather than over-claim — 8 unverified copy items and 2 genuinely-unfinished assets.

    locked
  • Added a simplified, color-coded "Current State — You Are Here" table to the Miro board; left the hand-built blueprint untouched and fully reversible.

    locked
  • Confirmed all five email / nurture sequences are live (Indoctrination · Reminder · Countdown · Warm 4-Pillars · No-Show Recovery).

    locked
  • Captured the reconciliation and doctrine in Black Ledger OS / Obsidian (the War Board concept note + a session record).

    locked

What was done.

01The three-surface source-of-truth model

The problemProgress lived in three places — a Miro funnel diagram, a Notion "War Board," and the Executive Brief Cloud — with no rule for which one to believe. They had silently diverged.
What was doneAssign each surface a single job and a precedence order, so anyone can tell design intent from execution tracking from the accurate record. Defined Miro = design intent, Notion War Board = execution tracker, Executive Brief Cloud = accurate record; documented the model and its precedence rule in the Black Ledger OS. The Executive Brief Cloud remaining the disciplined, accurate record.
The impactOne legible operating picture; disagreements between tools now resolve by rule instead of by argument.

02The Notion War Board, reconciled to reality

The problemThe War Board undercounted reality: Website Launch read 32% though it was near launch-ready, and KPI Intelligence read "Done" at 0% while all its sub-tasks sat in backlog.
What was doneBring Notion back in line with the shipped record — but only mark complete what the git history and briefs actually prove, and leave the rest honestly open. Marked 21 git-verified tasks complete on the Website Launch board (14→36 done), moved its rollup 32%→~90%, and resolved KPI Intelligence to 100% + a "superseded" note pointing to the Supabase KPI Command Center build. Left 10 tasks In Progress on purpose. Owner confirmation on the 8 unverified copy items; Creative Assets for the 2 unfinished deliverables.
The impactThe board is trustworthy again; the real remaining work — not a phantom 68% — is what shows.

03The Miro "Current State" map

The problemThe Miro board is a rich 176-item blueprint of the revenue engine as designed — with no at-a-glance signal of what is actually built.
What was doneOverlay a simplified "you-are-here" view without touching the blueprint, so design intent and execution state live on one canvas. Added one clean, color-coded table — "Current State — You Are Here (July 2026)" — mapping 16 components across engines, funnels, lead sources, nurture, pipelines, and supporting systems: 8 live · 6 partial · 2 not built. A single reversible widget. Owner's ground-truth per funnel (e.g. the email sequences confirmed live).
The impactAnyone opening the board sees the true state in seconds; the honest gaps (the Sales layer) are visible, not implied.

04The Source of Truth Divergence doctrine

The problemReconciling once fixes today; it does not stop the tracker from drifting again next week.
What was doneWrite the lesson into canon so the discipline outlives this session. Captured the War Board concept note in Black Ledger OS / Obsidian — the three-surface model, the "believe the record" rule, and the standing risk that an unreconciled tracker becomes actively misleading — plus a dated session record. Extended the Executive Brief Cloud chronicle through 008. A weekly reconciliation cadence and an owner for it.
The impactThe same failure is now cheap to catch: when a board's % and a brief's story disagree, the rule already says which one wins.

By the numbers.

6
Systems on the War Board
21
Tasks reconciled to complete
32→90%
Website Launch, corrected
16
Components mapped (current state)
8 / 16
Components live
8
Briefs shipped this week
~90%
Website (Revenue Engine relaunch)
50% · 8 of 16
Revenue-engine components live
0% · not built
Sales / monetization layer

Where we are.

01
Foundation
02
Launch
03
Scale
04
Expansion
05
Acquisition

Decisions still required.

  • Keep or demote the Notion War Board. Reconcile it weekly against the briefs, or demote it to a working scratchpad and let the Executive Brief Cloud + the Miro current-state view stand as canon.
  • Sequencing of the Sales layer. When to build the Sales Engine and the AE revenue pipeline — the last major unbuilt part of the machine.

    “Stop-doing: Brain harvesting, wiki filing, dashboard polish, funnel #5, website commits, hiring conversations.”

  • Owner of weekly reconciliation. Who is accountable for snapping the tracker back to the record each week so it never drifts this far again.

What comes next.

  1. 01
    Build the Sales / monetization layer
    The Sales Engine + the AE revenue pipeline and no-show recovery — the largest remaining gap on the current-state map.
  2. 02
    Finish Creative Assets
    VSL I / II edits, the four educational videos, and the Market Report · Strategy Prep · LAS Results PDFs (the board's honest 67%).
  3. 03
    Complete the War Room webinar
    Registration is live; the webinar content is not — finish it or cleanly defer it.
  4. 04
    Institute weekly reconciliation
    Assign an owner and a cadence to keep the War Board matched to the briefs; verify the 8 unconfirmed copy items.
  5. 05
    Close the credibility gaps
    Real testimonials and the finished Market Report PDF — the two genuinely-unfinished items left open on Website Launch.
Executive Brief · Nº 009 · July 3, 2026 · Canonical