Intent building Intent

The meta-loop

Intent's development follows its own Notice → Spec → Execute → Observe loop. Observations about how work flows (or doesn't) get captured as signals. Signals cluster into problems worth solving. Specs define what to build. Agents execute. Events get emitted. And the loop continues.

What you're looking at below is the actual output of that loop — not mock data, not a demo. These are real signals from real sessions, feeding real specs, generating real events. Knowledge Engine (Layer 1) feeds the Intent loop through lint-generated signals and knowledge queries during spec-shaping.

Why this matters

Most operating models are described in slide decks. Intent is described in its own format. Every signal on this page was captured using intent-signal. Every spec was written using the Intent template. Every event was emitted by the Intent GitHub Action.

This isn't just documentation. It's a live system observing itself. When we notice friction in using Intent to build Intent — that observation becomes a signal, which feeds the next iteration. The methodology improves by running.

The methodology this system follows →

And Intent is the operating model that built the rest

The same loop that built Intent governs real, shipping products across a coherence stack — Intent is the reference implementation, not the whole system. On The Parlor portfolio, every product points back here as “the operating model that built me.” The products aren't a catalog to buy; they're the dogfood proof that the discipline is operationalized, not asserted — see the repos Intent governs.

See the coherence stack Intent is part of →  active hypothesis, v0 — built to be challenged