For the extra curious

Visual codemap

The three public repos as one picture. Nodes are files, protocols, or demo paths. Edges are runtime flow (events, jobs, signatures), not folder nesting.

The series as one system

green = the check / the signature / a human surface raised = process, worker, spec

Two questions define any loop.

Continuation on the x-axis, locus on the y-axis. The interesting differences sit on the right: how “done” is decided.

cloud-persistentin-session

trigger · cloud
Claude RoutinesAntigravity /scheduleCursor Automations

verification · cloud
Codex Goal modeAntigravity /goal

trigger · session
Claude /loop

verification · session
Claude Code /goal

gated by a triggergated by verification

Event vocabulary

Everything the UI does is a typed event on one SSE stream.

TEXT_MESSAGE_*

Streaming concierge copy. Start / content delta / end.

TOOL_CALL_*

An agent step with args and results. OperatorView lives on these.

GENERATIVE_UI

A real component: component + props.

USER_TASK_PENDING

A Camunda user task, surfaced as a card.

STEP_STARTED / FINISHED

Process progress on customer stepper and operator log.

PARTY_HOP

EP 03. Lights the four-party AP2 strip.

How to read a PR in these repos

Start at the wire, not the model.

1. The event

If a card appeared, an event was emitted. Find emit( in the worker.

2. The job

The worker is a Zeebe job. Operate shows the same sequence.

3. The fork

If a human appeared, a DMN table or a user task put them there.

4. The proof

EP 01: frame stills. EP 02: operator log. EP 03: merchant signature check.

Back to the hub Essays EP 01 EP 02 EP 03