secondme strategy hub
current overview · scan first, dive second

current overview for secondme.

this page is the live scan-layer for the project: what looks settled, what is still in motion, and what deserves attention now. it is not the canonical doctrine page and not the source bibliography. those live in separate surfaces.

hub map

four page roles, four different jobs

the pages should not compete with each other. each one should solve a different reading job.

page contract

what belongs where

the main fix for duplication is to keep each page narrow.

constitution

what we are building

mission, wedge, v1, principles, trust ladder, business posture, non-goals.

overview

where we stand now

current posture, strongest beliefs, open tensions, and immediate focus.

proofboard

why we believe it

claim, evidence, caveat, falsifier, implication, confidence.

cadence

how truth gets updated

source hierarchy, review rhythm, open-loop discipline, and promotion rules.

canon ops

how the constitution is maintained

agent roles, card schemas, section thresholds, current status, and next implementation steps.

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 onboarding-to-leverage flow

the product still needs one sharp flow where a user grants read-only access to live context, gets immediate insight, and sees tailored leverage already in motion.

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.