VP Completion — Mission Control

The single pane. Generated 2026-07-12T12:00:00.000Z · deep detail: JTBD Scoreboard · What Great Looks Like · Canon v1.6 · Ingestion · Hub

34%

overall complete
generated truth

screen x stakeholder
tasks

6/57

curated jobs scored
7%

5/43/5

BE live/mock/missing
contract read

Definition of done — what "VP works" means

VP is complete for this campaign when every burning + core JTBD scores 10/10 on the anchored rubric, for all three stakeholders, on the shared demo world. Concretely:

Distributor (built): every screen renders World v2 for the viewer; every burning job at 10/10.
Processor + Producer (building): their tailored screens exist, fed by the world, jobs at 10/10.
One world, three lenses — same objects, RBAC-projected, no leaks. Zero console errors, data reconciles, nothing fake.
Demo DB + schema statement handed to Allan — the "just needs ingestion" state made literal.

Then going live = Allan connects the sources. Everything after is iteration (more stakeholder lenses, the 159-step trust curriculum climbing).

Your role — architect & domain, nothing mechanical

Only you do these four things:

Design judgment — on new surfaces (processor/producer screens): "yes, that's the experience" or "redo like this." Claude Design is canonical; you hold it.
Domain truth — the burning jobs, the RACI calls, what a role actually needs to do their work. The processor/producer JTBD sets. You are the source.
Score the jobs — the HITL passes: open a screen, can the role do their job at 10/10? Your number is authoritative; it sets the gap list.
Direct — "go", "redo: …", set priorities. You never hand-edit output or chase bugs.

You never: write code · debug · wire screens · do git · catch mechanical bugs (the sweep + gates do that before anything reaches you).

How VP delivers a job — the loop

JOB (registry) → SCREEN + VP ACTIONS (what VP surfaces/drafts/executes) → SCORE 0–10 (your HITL) → GAP → codex fix → RE-SCORE → 10/10

Every job in the registry names the screen(s) that serve it and the concrete actions VP takes (e.g. "VP drafts the chase to Ana Costa naming the slipped date"). The delegation dial (RACI's dynamic R) says whether VP does it with you, drafts for you, or does and reports — climbing as it earns trust. Score measures the job; the dial measures the partnership. Both move to their target.

Generalizes to 36,000 — the primitives under the jobs

The clarified JTBDs aren't bespoke per client. They decompose into a handful of reusable primitives — so the demo (3 stakeholders, one world) is the engine and each of the 36,000 clients is config, not a rebuild:

Primitive	What it is	Per client =
Ingestion	Connect each source in its own dialect (CAMT/MT940 · PAIN · HBCI · file · REST), normalize + validate into the world.	a connector config — Remexian: Collmex / D365-BC files, Coface, SFirm, Corpay
Connection	One company-to-company RBAC'd graph; the same objects projected per role & tenant.	a lens — 36k clients = 36k lenses, no rebuild
HITL	The human scores the job, corrects the data, approves the action; the delegation dial climbs as VP earns trust.	the same loop
Write-back	VP writes the correction/decision back to the client's book of record (D365 · Collmex · CRM) with tracked sync-state.	the same canonical writer
Provenance	Every number traces to its source system — highlight → sources.	ambient, everywhere

This is why "just needs ingestion" is the whole scale story: the job surfaces + HITL + write-back are the reusable engine; onboarding a client = ingest its sources + project its lens. Ground-truthed on Remexian finance (2026-07-10).

Generated truth — completion, velocity, ETA

Formula	overallPct = 65% * screenStakeholderTaskPct + 35% * curatedJobScorePct; task status weights: done=1, verifying=0.75, building=0.45, todo=0; unscored curated jobs count as 0/10 until HITL scoring.
Completion	34% overall = 48% task-weighted screens x stakeholders + 7% curated-job scores.
Velocity	48.14 commits/day over last 7 days (337 commits). Throughput assumption: using commit velocity fallback: 1 commit = 2 implementation hours because task close dates are not yet present.
ETA	2026-07-14 at 96.3 estimated hours/day, 135 hours remaining.
Atlas	71 routes/screens indexed.
Registry	1,649 jobs; 0 scored in registry source; 57 curated scorecard jobs parsed.

45%

Distributor
15 tasks

29%

Processor
15 tasks

29%

Producer
13 tasks

Idea inbox — drop it, don't lose it

Getting an idea mid-build? Say "idea: …" to Claude. It becomes a GitHub issue (tied to the right epic), lands in this inbox, and threads to the job it affects — nothing floats. Captured ideas:

Idea	Issue	Ties to	Status
— none yet · fire away, the loop is live —

The full app — every screen × stakeholder

Screen	Distributor	Processor	Producer	Jobs
Dashboard BE 1/8/1 · 351 registry jobs	building FE · MC-DIST-DASHBOARD	todo FE · MC-PROC-DASHBOARD	todo FE · MC-PROD-DASHBOARD	C1 C2 C3 C4 P2 PR1
Financials BE 1/2/1 · 995 registry jobs	building FE · MC-DIST-FINANCIALS	todo FE · MC-PROC-FINANCIALS	todo FE · MC-PROD-FINANCIALS	C2 C5 S4 P2 PR1
Actions BE none · 508 registry jobs	building FE · MC-DIST-ACTIONS	todo FE · MC-PROC-ACTIONS	todo FE · MC-PROD-ACTIONS	J5 P3 F3 PR2
Connections BE none · 710 registry jobs	building FE · MC-DIST-CONNECTIONS	building FE · MC-PROC-CONNECTIONS	building FE · MC-PROD-CONNECTIONS	S7
Inventory BE 0/5/0 · 194 registry jobs	building FE · MC-DIST-INVENTORY	todo FE · MC-PROC-INVENTORY	todo FE · MC-PROD-INVENTORY	S3 P1 PR1
PO Tracker BE 3/7/0 · 34 registry jobs	built FE · MC-DIST-PO-TRACKER	built FE · MC-PROC-PO-TRACKER	built FE · MC-PROD-PO-TRACKER	J1 J2 J3 J4 U1 U2 U3 U4 U5 U6
Messages BE none · 155 registry jobs	built FE · MC-DIST-MESSAGES	built FE · MC-PROC-MESSAGES	built FE · MC-PROD-MESSAGES	S6
Data BE 0/1/0 · 962 registry jobs	built FE · MC-DIST-DATA	todo FE · MC-PROC-DATA	todo FE · MC-PROD-DATA	S5
Supply BE 0/11/0 · 464 registry jobs	building FE · MC-DIST-SUPPLY	—	—	S1
Demand BE 0/8/1 · 304 registry jobs	building FE · MC-DIST-DEMAND	—	—	S2
Catalog · Pricing BE 1/0/0 · 546 registry jobs	building FE · MC-DIST-CATALOG-PRICING	—	—	S8
Routes BE 0/3/2 · 253 registry jobs	building FE · MC-DIST-ROUTES	building FE · MC-PROC-ROUTES	—	S10 P2
Pharmacies BE 0/3/0 · 29 registry jobs	building FE · MC-DIST-PHARMACIES	—	—	S9
Team · Settings BE 0/0/1 · 264 registry jobs	building FE · MC-DIST-TEAM-SETTINGS	todo FE · MC-PROC-TEAM-SETTINGS	todo FE · MC-PROD-TEAM-SETTINGS	S11
CoA / Labs BE 1/0/0 · 0 registry jobs	—	built FE · MC-PROC-COA-LABS	built FE · MC-PROD-COA-LABS	P1 F1
QP / QA Release BE none · 0 registry jobs	—	built FE · MC-PROC-QA-RELEASE	building FE · MC-PROD-QA-RELEASE	P3
Remediation BE none · 0 registry jobs	—	building FE · MC-PROC-REMEDIATION	building FE · MC-PROD-REMEDIATION	F3
Downpacking · Schedules BE none · 0 registry jobs	—	building FE · MC-PROC-DOWNPACKING	—	proc-ops
Cultivation · Yield BE none · 0 registry jobs	—	—	built FE · MC-PROD-CULTIVATION-YIELD	PR1 PR2
Agreements BE none · 0 registry jobs	built FE · MC-DIST-AGREEMENTS	building FE · MC-PROC-AGREEMENTS	—	terms

built = priority done + FE route + no missing BE for that screen · wired = route or proof exists but BE/status is not fully clean · building = active priority lane · todo = queued. Grid is generated from priorities + atlas + registry + backend contract.

The path today

Priority	Step	Stakeholder	Screen	Who	State	Estimate
1	Distributor dashboard cockpit wiring MC-DIST-DASHBOARD	Distributor	Dashboard	codex	building	6h
2	Processor dashboard lens MC-PROC-DASHBOARD	Processor	Dashboard	codex	todo	5h
3	Producer dashboard lens MC-PROD-DASHBOARD	Producer	Dashboard	codex	todo	5h
4	Distributor financials wiring MC-DIST-FINANCIALS	Distributor	Financials	codex	building	7h
5	Processor own-leg financials MC-PROC-FINANCIALS	Processor	Financials	codex	todo	6h

Assignable task list — manual priorities, generated status

Priority	ID	Task	Stakeholder	Screen	Owner	Status	Hours	Jobs
1	`MC-DIST-DASHBOARD`	Distributor dashboard cockpit wiring	Distributor	Dashboard	codex	building	6	C1 C2 C3 C4
2	`MC-PROC-DASHBOARD`	Processor dashboard lens	Processor	Dashboard	codex	todo	5	C1 C3 P2
3	`MC-PROD-DASHBOARD`	Producer dashboard lens	Producer	Dashboard	codex	todo	5	C1 C3 PR1
4	`MC-DIST-FINANCIALS`	Distributor financials wiring	Distributor	Financials	codex	building	7	C2 C5 S4
5	`MC-PROC-FINANCIALS`	Processor own-leg financials	Processor	Financials	codex	todo	6	C2 P2
6	`MC-PROD-FINANCIALS`	Producer own-leg financials	Producer	Financials	codex	todo	6	C2 PR1
7	`MC-DIST-ACTIONS`	Distributor actions loop	Distributor	Actions	codex	building	5	J5
8	`MC-PROC-ACTIONS`	Processor actions lens	Processor	Actions	codex	todo	4	P3 F3
9	`MC-PROD-ACTIONS`	Producer actions lens	Producer	Actions	codex	todo	4	PR2 F3
10	`MC-DIST-CONNECTIONS`	Distributor connections fixes	Distributor	Connections	codex	building	4	S7
11	`MC-PROC-CONNECTIONS`	Processor connections lens	Processor	Connections	codex	building	3	S7
12	`MC-PROD-CONNECTIONS`	Producer connections lens	Producer	Connections	codex	building	3	S7
13	`MC-DIST-INVENTORY`	Distributor inventory lots wiring	Distributor	Inventory	codex	building	4	S3
14	`MC-PROC-INVENTORY`	Processor inventory lots lens	Processor	Inventory	codex	todo	4	S3 P1
15	`MC-PROD-INVENTORY`	Producer inventory lots lens	Producer	Inventory	codex	todo	4	S3 PR1
16	`MC-DIST-PO-TRACKER`	Distributor PO Tracker	Distributor	PO Tracker	claude	done	0	J1 J2 J3 J4 U1 U2 U3 U4 U5 U6
17	`MC-PROC-PO-TRACKER`	Processor PO Tracker lens	Processor	PO Tracker	claude	done	0	J1 J2 J3 J4 U1 U2 U3 U4 U5 U6
18	`MC-PROD-PO-TRACKER`	Producer PO Tracker lens	Producer	PO Tracker	claude	done	0	J1 J2 J3 J4 U1 U2 U3 U4 U5 U6
19	`MC-DIST-MESSAGES`	Distributor messages	Distributor	Messages	claude	done	0	S6
20	`MC-PROC-MESSAGES`	Processor messages lens	Processor	Messages	claude	done	0	S6
21	`MC-PROD-MESSAGES`	Producer messages lens	Producer	Messages	claude	done	0	S6
22	`MC-DIST-DATA`	Distributor data surface	Distributor	Data	claude	done	0	S5
23	`MC-PROC-DATA`	Processor data lens	Processor	Data	codex	todo	3	S5
24	`MC-PROD-DATA`	Producer data lens	Producer	Data	codex	todo	3	S5
25	`MC-DIST-SUPPLY`	Distributor supply	Distributor	Supply	codex	building	4	S1
26	`MC-DIST-DEMAND`	Distributor demand	Distributor	Demand	codex	building	4	S2
27	`MC-DIST-CATALOG-PRICING`	Distributor catalog and pricing	Distributor	Catalog · Pricing	codex	building	5	S8
28	`MC-DIST-ROUTES`	Distributor routes	Distributor	Routes	codex	building	4	S10
29	`MC-PROC-ROUTES`	Processor freight routes	Processor	Routes	codex	building	4	P2
30	`MC-DIST-PHARMACIES`	Distributor pharmacies	Distributor	Pharmacies	codex	building	4	S9
31	`MC-DIST-TEAM-SETTINGS`	Distributor team and settings	Distributor	Team · Settings	codex	building	4	S11
32	`MC-PROC-TEAM-SETTINGS`	Processor team and settings lens	Processor	Team · Settings	codex	todo	3	S11
33	`MC-PROD-TEAM-SETTINGS`	Producer team and settings lens	Producer	Team · Settings	codex	todo	3	S11
34	`MC-PROC-COA-LABS`	Processor CoA and labs	Processor	CoA / Labs	claude	done	0	P1 F1
35	`MC-PROD-COA-LABS`	Producer CoA and labs testing	Producer	CoA / Labs	claude	done	0	P1 F1
36	`MC-PROC-QA-RELEASE`	Processor QP/QA release	Processor	QP / QA Release	claude	done	0	P3
37	`MC-PROD-QA-RELEASE`	Producer QP/QA release lens	Producer	QP / QA Release	codex	building	4	P3
38	`MC-PROC-REMEDIATION`	Processor remediation	Processor	Remediation	codex	building	5	F3
39	`MC-PROD-REMEDIATION`	Producer remediation	Producer	Remediation	codex	building	5	F3
40	`MC-PROC-DOWNPACKING`	Processor downpacking and schedules	Processor	Downpacking · Schedules	codex	building	6	proc-ops
41	`MC-PROD-CULTIVATION-YIELD`	Producer cultivation and yield	Producer	Cultivation · Yield	claude	done	0	PR1 PR2
42	`MC-DIST-AGREEMENTS`	Distributor agreements	Distributor	Agreements	claude	done	0	terms
43	`MC-PROC-AGREEMENTS`	Processor agreements lens	Processor	Agreements	codex	building	4	terms

Progress over time — git history

▃▁▅▅█▃▂▆▆▅▇▃▆▃

Date	Commits	Branches
2026-06-29	24	feat/vp-completion-board:24 · feat/demo-connections:24 · feat/demo-integrated:24 · feat/demo-lens-redo:24 · feat/demo-messages:24 · feat/demo-processor:24 · feat/demo-producer:24 · feat/demo-spine:24 · feat/demo-world-v2:24
2026-06-30	0	—
2026-07-01	45	feat/vp-completion-board:45 · feat/demo-connections:45 · feat/demo-integrated:45 · feat/demo-lens-redo:45 · feat/demo-messages:45 · feat/demo-processor:45 · feat/demo-producer:45 · feat/demo-spine:45 · feat/demo-world-v2:45
2026-07-02	47	feat/vp-completion-board:47 · feat/demo-connections:47 · feat/demo-integrated:47 · feat/demo-lens-redo:47 · feat/demo-messages:47 · feat/demo-processor:47 · feat/demo-producer:47 · feat/demo-spine:47 · feat/demo-world-v2:47
2026-07-03	79	feat/vp-completion-board:79 · feat/demo-connections:79 · feat/demo-integrated:79 · feat/demo-lens-redo:79 · feat/demo-messages:79 · feat/demo-processor:79 · feat/demo-producer:79 · feat/demo-spine:79 · feat/demo-world-v2:79
2026-07-04	23	feat/vp-completion-board:23 · feat/demo-connections:23 · feat/demo-integrated:23 · feat/demo-lens-redo:23 · feat/demo-messages:23 · feat/demo-processor:23 · feat/demo-producer:23 · feat/demo-spine:23 · feat/demo-world-v2:23
2026-07-05	9	feat/vp-completion-board:9 · feat/demo-connections:9 · feat/demo-integrated:9 · feat/demo-lens-redo:9 · feat/demo-messages:9 · feat/demo-processor:9 · feat/demo-producer:9 · feat/demo-spine:9 · feat/demo-world-v2:9
2026-07-06	57	feat/vp-completion-board:57 · feat/demo-connections:57 · feat/demo-integrated:57 · feat/demo-lens-redo:57 · feat/demo-messages:57 · feat/demo-processor:57 · feat/demo-producer:57 · feat/demo-spine:57 · feat/demo-world-v2:57
2026-07-07	58	feat/vp-completion-board:58 · feat/demo-connections:58 · feat/demo-integrated:58 · feat/demo-lens-redo:58 · feat/demo-messages:58 · feat/demo-processor:58 · feat/demo-producer:58 · feat/demo-spine:58 · feat/demo-world-v2:58
2026-07-08	48	feat/vp-completion-board:48 · feat/demo-connections:48 · feat/demo-integrated:48 · feat/demo-lens-redo:48 · feat/demo-messages:48 · feat/demo-processor:48 · feat/demo-producer:48 · feat/demo-spine:48 · feat/demo-world-v2:48
2026-07-09	69	feat/vp-completion-board:69 · feat/demo-connections:69 · feat/demo-integrated:69 · feat/demo-lens-redo:69 · feat/demo-messages:69 · feat/demo-processor:69 · feat/demo-producer:69 · feat/demo-spine:69 · feat/demo-world-v2:69
2026-07-10	25	feat/vp-completion-board:25 · feat/demo-connections:25 · feat/demo-integrated:25 · feat/demo-lens-redo:25 · feat/demo-messages:25 · feat/demo-processor:25 · feat/demo-producer:25 · feat/demo-spine:25 · feat/demo-world-v2:25
2026-07-11	60	feat/vp-completion-board:47 · feat/demo-connections:34 · feat/demo-integrated:44 · feat/demo-lens-redo:44 · feat/demo-messages:33 · feat/demo-processor:44 · feat/demo-producer:44 · feat/demo-spine:32 · feat/demo-world-v2:43
2026-07-12	20	feat/vp-completion-board:3 · feat/demo-integrated:17 · feat/demo-lens-redo:2 · feat/demo-processor:3 · feat/demo-producer:3

Counts are unique commits across feat/vp-completion-board, feat/demo-connections, feat/demo-integrated, feat/demo-lens-redo, feat/demo-messages, feat/demo-processor, feat/demo-producer, feat/demo-spine, feat/demo-world-v2, window 2026-06-29T00:00:00Z to 2026-07-12T12:00:00.000Z.

Distributor = built, looping to 10/10 · Processor + Producer = building now · The gate: cite a job or don't build it. · Clay ⇄ Claude · Mission Control