Back to corpus
architecturetechnical paper candidatescore 40

Stage 2: Compound Synthesis -- Beyond Architecture

1. Accepts any sequence of typed events on the bus 2. Groups them into "processes" (identified by a processId) 3. Embeds each event into a vector 4. Computes anticipation scalars over the trajectory 5. Publishes scalar snapshots and intervention signals 6. Enables paradigm adapters (OmniFlow, Draft-and-Prune, Prompt Optimization) to plug in as process types that define how to embed events, interpret scalars, and execute interventions

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

1. Accepts any sequence of typed events on the bus 2. Groups them into "processes" (identified by a processId) 3. Embeds each event into a vector 4. Computes anticipation scalars over the trajectory 5. Publishes scalar snapshots and intervention signals 6. Enables paradigm adapters (OmniFlow, Draft-and-Prune, Prompt Optimization) to plug in as process types that define how to embed events, interpret scalars, and execute interventions Beyond is NOT a separate process, NOT a Python sidecar, NOT a Gemini API wrapper. It is a TypeScript package inside the NUMU daemon that operates on bus events in real time. The core insight from the research: all three paradigms follow the same geometric trajectory (explore -> converge -> lock). Anticipation scalars make this trajectory visible and actionable without domain-specific convergence criteria. Building on Step 1. The scalar engine is a TypeScript port of `AnticipationGeometry.compute()` from `python/anticipation_geometry/generalized_anticipation.py`. The port covers 4 scalars (not 7 -- phase_stiffness, novelty, and stability require motion-domain features that don't apply to event trajectories):

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.