shellCopy SWITCHER_NEW_INITIATIVE_LABEL · RUNNER-SPEC §7

Initiatives you run

3 open · updated moments ago convening_instance.runner_id = you · RUNNER-SPEC §2
count convening_instance families
3
Initiatives
2 sent · 1 not sent
unbuilt · W1
6
Branches
1 private
unbuilt · W0/P4
8
Teams involved
across 2 sent initiatives
ask − resolved, per family
17
Questions open
Waiting on 17 answers
commitment over ask
26
Questions resolved
held so far — signed in ink
response.type = reroute
4
Questions rerouted
“Suggest someone else”

By initiative

RUNNER-SPEC §4 sort axes
Initiative name: W0/P2 unapplied
Planning window
Nodes
Branches
Teams
Open · resolved · rerouted
Last change
2027 budget planning
run by you · Delgado owns runner_id · principal_id
Aug 1Sep 12
Day 12 of 42 · 31 days left send_at → frame_end_date · dates only
28
4
5
11 open·17 resolved·3 rerouted
2h ago
an answer landed

Teams by open questions GROUP BY team, state — the work, never the person · DEC-0812-measure-the-work-never-the-person

Sales6 openoldest open 9 days
Finance3 openoldest open 4 days
Engineering2 openoldest open 2 days
Legal0 openall 4 resolved
Compensation review — run by D. Okafor Private open · 9 days · 3 questions in it structure survives privacy: nodes, states, counts, dates — never who or why · DEC-0811-runner-sees-by-default
opens the nudge composer — you write it, you send it; never one-click fire · class-4: always a person · DEC-0811-runner-visibility-open-items
Open
“Nodes” as a chrome word (RUNNER-SPEC §2 row 1): Nick dictated the metric and the word; whether “node” is a surface term or map-register leaking into chrome is unruled. Rendered as dictated, flagged rather than silently renamed. register law §8.7 — no ruling covers it either way
Open
“Exec readout” per initiative (RUNNER-SPEC §10.1): T15's specified audience is the economic buyer, org-level. The initiative-scoped summary the runner asked for in §4 is either a different surface sharing the name, or a corrected audience. Not drawn here — routed to Nick, not assumed.
Open
Window mapping (RUNNER-SPEC §10.2, W0 finding iii): the planning window's END is frame_end_date; its START and the execution window have no schema home. This mockup renders start = send date as an assumption. The “Day n of m” read is arithmetic over dates — deliberately not a fill bar, no percent-complete, no “on track” (boundary law; §10.3 honoured).

Questions for me

4 waiting · from 3 initiatives ask.addressee_id = you · DEC-0812-answering-is-a-first-class-axis
Term open
“Questions for me” is a candidate name, not a decided one — the DEC opened a TERM-LEDGER row and did not settle it. Every string in this band uses “question” per DEC-0812-ask-becomes-question.
“Can Sales absorb the 2027 quota model by March 31?” ask.confirmed_sentence · PL-8 verbatim serif
R. Delgado is asking — in support of 2027 budget planning provenance · STAKEHOLDER-SPEC §1 shape
in-shell route — closes blueprint F4.1; signed-in members land in product
decideneed by Aug 223 days on your desk
“Data-residency review holds for the Frankfurt launch.”
Your commitment — does it still hold? check_in_addressee_id = you · SCHEMA §1.7
check-inby Aug 15due in 3 days
“Who signs off contractor budget above £250k?”
P. Sandoval suggested you — in support of FY27 vendor strategy response.type='reroute' → new ask · §8.7 “Suggest someone else”
authorizeneed by Aug 201 day on your desk
“Can your team bottom out platform costs for the 2027 plan?”
M. Osei is asking about your team's part — in support of 2027 budget planning relay: ask with subject_branch_instance_id · SCHEMA §1.2
deliverneed by Sep 1today
F2
Slack is not built. The stakeholder spec names Slack a primary answering mode; it is specified (SlackAdapter) and unimplemented. Until it exists, email is the demo path into every row above. DEC-0812-level-1-is-one-surface REJECTED note

States (F3) — drawn, not implied

Each block below is the same surface under a different condition. These are part of the mockup, not an appendix: most of the real experience lives here.

Day one — no initiatives. Same surface, zeroed (option b, Nick leaned, not ruled — carried as recommendation) RUNNER-SPEC §2

0
Initiatives
0
Branches
0
Teams involved
0
Questions open
0
Questions resolved
0
Questions rerouted

No initiatives yet.

Frame one, route it to the people who own its pieces, and drive it to a committed answer.

Questions for me — empty. Quiet, factual; nothing decays, nothing nags boundary law

Nothing is waiting on you.

When someone routes a question to you, it lands here — and in your email.

Loading — first load ONLY. Skeleton keeps the layout; figures settle once when real. A refetch never re-skeletons — hold the previous render at reduced opacity, no layout jump (reduced-motion: appear instantly, end state kept)

Degraded — a metric's source is unavailable; the figure refuses, the row does not

Small team — the k-anonymity posture, stated where it applies DEC-0811 wrap: k-risk accepted for the runner's own structure read; floor untouched where it binds

Teams by open questions

Legal2 open2 people on this team — shown: this is your own initiative's structure, a read you could assemble from your own screen. Org-level rollups and leadership aggregates keep the k=3 floor and refuse instead. DEC-0731-small-tenant-onboarding-choice governs the below-floor org case

Motion — the authored layer (F7 · DEC-0811-product-feels-alive · DESIGN.md motion rules)

Spec
Focal arrival — “the ledger takes stock”: figures count up in ink (600ms, staggered 40ms) while rows rise beneath (420ms, staggered 60ms) and each window tick slides to today. Once per landing.
Feedback: every pressable scales to .97 on press (120ms); question cards lift on hover, pointer-fine only.
Change, marked: a navy dot settles beside what moved since arrival (“an answer landed”). Silence never animates — no pulse on the unanswered, ever (boundary law at the motion layer).
Grow: the day-one route draws itself once — DESIGN.md's own signature, at the only moment it can orient.
Reduced motion: every end state renders instantly and completely; nothing is hidden behind the choreography.
Build note (F7): these are authored expressions; the mechanics beneath them (focus, ARIA, interruption, queueing) come from the baseline library set Nick owes — not hand-rolled.

Why this shape

One instrument, two bands, no mode switch: the same person runs initiative A and answers into initiative B (runner_id is per-initiative, not a user type). The totals band is byte-identical on day one and day one hundred — only the figures change — which is the property Nick named when he leaned to the zeroed rollup. Sections render empty when they do not apply; nothing is greyed, nothing nags, and what moved is a sort axis, not a notification. Alive means the surface answers “what changed since I last stood here” on sight (DEC-0811-product-feels-alive) — the settle-in-ink arrival, the “last change” column, and recency-first sort carry that without a single pressure surface.

F5
Gate: this mockup is not signed. Its row in REBUILD-PLAN-2026-08.md §7 is open, and nothing here is build-authorised until Nick signs it.