The program map

c1302026-11-10

Eight cycles and a naming cycle, the four gates between them, and what each waits on.

Source: c130 plan.md (the program map, the gates G1–G4, the Ruling column and the Answers of 2026-11-09); CYCLES.md as of 2026-11-10; the c131 and c137 records for what is done.

Runs now · no gate, or the gate already open

▤c130 · Native App (program)

The primer, the shape, the gates, the pitch; the record of the roadmap.

kicked off 2026-11-09 · primer (Phase 1) done · next: shape.md and the pitch

⬚c131 Phase 0 · the spike

A hello app in GPUI Kit, the tray beside the event loop, the three-source nozzle with a fixture plane.

under way in ../qnative since 2026-11-09 · steps 1–3 committed · strobe and CI next

▤c134 Phase 0 · the inventory

Both apps mapped, a 30-item API gap list, the asks consolidated, what the layer lacks.

done 2026-11-09 · Phases 1–5 wait for Kamal and Tyler's repo decision

▭c137 Phases 0–2 · App Messaging

The inventory, the bones with ten examples, the ports and controls mocked as three lab pages.

done 2026-11-09 · review stop: ten questions for Mark · Phase 3 with c131, Phase 4 with c134

⬚c135 · Component Cleanup

The layer catalog audited against the five checks, duplicates resolved, every component documented.

no gate · not kicked off · starts on Mark's word

G1 · Shape ruled

D1–D10 ruled 2026-11-09; shape.md still to be accepted. Opens c131's build and c133.

G2 · Requirements session

Tyler's working session, mid-November: the primer, the shape and the spike on the table; Q1–Q12 answered; outcome A or B; c0's shortlist on the agenda.

G3 · V1 handoff

c131 Phase 5: the app, its patterns doc, the fixture world and the headless tests handed to the engineers. The program's main deliverable.

G4 · Control plane port

c134's Phase 4 plan accepted by Tyler and Kamal. Opens the port.

Gated · each waits on another's output

▣c131 · Native App V1, the build

Shell, DataNozzle, the message channel's ports and bones, Status, Inventory, Events, Config, Connect, the tray; packaged for three OSes; handed over at G3.

waits on shape.md (G1) and c0's name · Mark's word

▤c132 · Native Design Prototyping

The medium, the token bridge, captures, skills, one worked example: how design mocks GPUI screens.

waited on the primer, done 2026-11-09 · open now, not kicked off

▭c133 · Remediation Training

Trigger, lesson, check, record: a finding becomes a lesson and completion becomes proof in the audit log.

waits on c137's bones (done) and a brief in market-analyst · shape ruled (G1)

▭c136 · Mechanic Access

Time-boxed, categorised, audited access a partner grants Qpoint on their plane: the grant screen and one Status line.

Phase 0 (prior art) may run now · the rest waits on c134's identity decision and Tyler's say on where grants live

The app's own repo · ../qnative, provisional name

▤c0 · Call My Name

The names: the native app, the control plane, the third data source, the two roles, the repo; grounded in the customer's words.

started 2026-11-09 · brief written · Mark's first pass, then the open session with Tyler (on G2's agenda)

⬚c1 · the spike

c131 Phase 0 as the repo's own cycle: hello app, tray, nozzle, fixture plane.

steps 1–3 committed · strobe measurements and CI next

What waits on what

shape.md

c130 Phase 2, to be accepted

c131 · the build

c133

c0 · the name

the session with Tyler

names

c131 · the repo and display name

c137 D7 · the role words

the primer

c130 Phase 1, done

done

c132

open now

c137 bones

done

a brief

market-analyst

both

c133

c134 D2

the identity decision

waits

c136 · Phases 1–4

Kamal's data model

Tyler's repo decision

c134 · Phases 1–5

c131 Phase 1

c134

carry

c137 Phase 3

the V1 slice

c137 Phase 4

the plane side

c131 Phase 5

c134 Phase 4 plan

G3 · G4

the engineers

V1 handed over

the control plane port

ours; kicked off or under waynot yet kicked offa gatesomeone else's input (Tyler, Kamal, a brief), or a document of ours still to be acceptedan output already on record

The problem

Eight cycles came out of one roadmap session and one decisions walk, each with its own gate, and most wait on another's output. Without the map every executor re-reads the plan to learn what it may start; with it the question is one glance: which rug am I on, and what opens the next one.

The core idea

Gates, not dates. A cycle starts when its input exists: the shape opens the build, Tyler's session answers the questions, the handoff ends the program. Whatever needs no gate runs now in its own session, and the spike runs beside the primer because a running app answers faster than reading.

What is open

shape.md (G1's second half) and the pitch; the date of Tyler's session (G2), with Q1–Q12 and the names; whether c131 becomes “attach at the UI layer” (outcome A) after it; Kamal's data model for c134 and G4; c132's medium, unblocked and waiting for a kick-off; Mark's answers to c137's ten questions.