layer 3
source pages
linked public source pages remain the deeper bibliography behind the strategy surface.
traceability
external depth
linked below ↓
hub map
three layers, one dashboard
this site is now split by cognitive job. overview is for orientation, proofboard is for causal belief, operating cadence is for keeping the team honest over time.
layer 1
proofboard
evidence-backed strategic claims, confidence, caveats, falsifiers, and roadmap implications.
new
belief -> implication
open module →
layer 2
operating cadence
how truth moves: update rhythms, source hierarchy, kill conditions, and delta-only review loops.
new
process guardrails
open module →
overview
what the team should keep in view
the point of the overview is not to repeat all the doctrine. it is to keep the active field visible: what seems settled, what is still soft, and what needs disciplined pressure next.
settled
chief of staff beats assistant
the system is valuable when it coordinates reality: priorities, people, approvals, timing, and follow-through.
doctrine
settled
scaffolding beats raw model delta
memory, orchestration, and decision surfaces appear more leverage-bearing than model chasing for real workflows.
strong belief
needs internal replication
in motion
wedge is role pressure, not just wealth
the strongest axis still looks like complexity x stakes x agency, with HNW as one likely first segment.
active bet
next
freeze the first briefing workflow
the product still needs a single approval-ready briefing surface that users would immediately want to keep.
current focus
active field
the five things a strong dashboard must expose
this is the information architecture shift suggested by the team discussion: less polished certainty, more readable tension.
01
active bets with kill conditions
every active bet should show confidence, test, owner, review date, and the condition under which the team would kill it.
02
traction signals, not just stories
surface the strongest confirming signal, strongest disconfirming signal, and the weird new signal that changed the map.
03
proof points below doctrine
doctrine should be brief. the evidence, caveats, and falsifiers should live in a linked proof layer.
04
market clock
track what changed outside in the last 30 days so the team does not keep solving a dead problem with beautiful language.
05
open loops with owners
every expensive hanging loop needs an owner, next step, and review date. loops without owners decay into mood.
design rule
capable of contradiction
a pre-pm-fit dashboard should be clear, alive, and slightly uncomfortable. otherwise it becomes a status object.
next clicks
where to go from here
one click for strategic belief. one click for team operating discipline. then deeper source pages for provenance.
recommended next click
proofboard
the strongest upgrade from the team chat was structural: stop showing naked doctrine. show evidence-backed claims with caveats and falsifiers.
open proofboard →
process layer
operating cadence
the second big upgrade was process discipline: cadence of truth, source hierarchy, permission to kill, and daily delta prompts.
open cadence →