The System — Flow

The Intent Loop

A continuous cycle with no sprint boundaries. Work flows from noticing a signal through specifying, executing, and observing — then back again. Every transition emits an event.

Loop Diagram
Intent CONTINUOUS LOOP Notice Capture signals Spec Shape into contracts Execute Agents implement Observe Measure outcomes
Phase Details

Notice

Capture signals from anywhere practitioners work.

Inputs Error logs, conversations, PR reviews, user feedback
Output Signal (scored with confidence + trust)
Tool intent-signal

Spec

Shape signals into agent-ready specifications.

Inputs Signals, codebase context, domain knowledge
Output Spec with verifiable contracts
Tool intent-spec

Execute

Agents implement against approved specs.

Inputs Approved spec with contracts
Output Artifacts, code, configuration
Tool Claude Code, GitHub Actions

Observe

Measure outcomes and capture learnings.

Inputs Execution results, runtime telemetry
Output Events, dashboards, new signals
Tool events.jsonl, dashboards
Loop Properties
∞

Continuous

No sprint boundaries. Work flows when it's ready, not on a two-week cadence.

⏱

Multi-speed

Minutes for a hotfix signal. Weeks for a strategic capability. Same loop.

◎

Observable

Every phase transition emits an OTel-compatible event to events.jsonl.

⚙

Agent-native

Specs are executable contracts, not prose stories. Agents can act on them directly.

Work Ontology

The loop operates on a seven-level work ontology. Each level has a clear owner, clear transitions, and emits events when work crosses a boundary. Signals flow up from raw observations into shipped products.

Signals → Intents → Specs + Contracts → Capabilities → Features → Products

Notice captures Signals. Spec shapes them into Intents, Specs, and Contracts. Execute builds Capabilities and Features. Observe measures the Product and feeds new signals back in.