Engineering

8-TypeScript: The Vercel AI SDK Surface

The grammar crossing the language boundary is itself the demonstration the series has been building toward. A TypeScript-driven cycle is no more able to certify itself than a Python-driven one. The discipline travels because the validator carries it.

7-MCP: 5QLN as a Connector

The cycle becomes a network service. The codex becomes a fetchable artifact. Any MCP-aware client gets the full surface in one config line. The validator sits behind the same protocol every other capability uses — discipline is one more tool call away.

6-Python: Phases as Tools (Anthropic Tool-Use API)

Receptive tools and generative tools. The receptive ones return values that come from the human, regardless of what the agent says. Trying to bypass them fills the center: with produced sparks (L2) or with false access to ∞0 (L3). The validator catches both.

5-Python: The Cycle as a LangGraph

The cycle expressed in LangGraph: each phase a node, the edges S→G→Q→P→V, the validator the terminal check. Execution interrupts at attestation points so a human fills the slots no model can fill for them. The graph carries the discipline by construction.

4-Python: The C1 Validator

The validator emits findings the validator itself cannot resolve. ATTESTATION_REQUIRED for L2 at the spark, for L3 at the resonance — only the human inquirer can attest. The validator refuses to silently certify a cycle whose human side was empty.