<aside> 🖖

For Enid — first read. This page is the entry point into the DVLO + /maru agent stack. It synthesizes three canonical sources into one activation surface: what the architecture is, why it works the way it does, and how to invoke it.

</aside>

<aside> 🔗

Canonical anchors (previewable). Every page in this cluster cross-links to the same anchor set so hover-preview works across the organism.

DVLO — Dyadic Verifiable Lane Orchestration: A Three-Plane Agent Architecture (Genesis Conductor × LidLift × Lane Harness × Edins Dyadic/PEAN × Instinct/DWE) · ‣ · Six-Surface Organism Integration Audit — DVLO Unified Health Check · /maru · Optimization Inversion — Category Pivot Command Center · Skills Activation Manifest — Planned + In-Development → Operational (Greg · DVLO · diamondNode · Retraining Loop) · ‣ · diamondNode — Canonical Identity & Publication Plan v1.1 · ‣ · Demand-Indexer · Verdant Commons · ‣ · · 🜔 Eulerian Codex — Diamond Vault Agentic Universe Wiki · Knowledge Graph Index — Agentic Operations & Crew Workflows

</aside>

<aside> 🔗

Canonical cluster anchors (previewable). Yennefer cluster · TAEX · Retraining loop · §6.17 · Integrations registry · Integrative Flow.

‣ · ‣ · ‣ · ‣ · ‣ · TAEX Intent Router — Agent-Based Routing with Dissonance Memory MCP · ‣ · ‣ · ‣

</aside>

Dev alignment narrative — webhook → Ouro → benchmark

This instruction should give devs one alignment argument: external resolution events become routed evidence, routed evidence becomes an Ouro execution state, and Ouro execution state is validated by the benchmark stack before it is treated as proof.

The bridge is:

1. Polymarket Resolution → Outbound Webhook is the event ingress. It emits marketId, outcome, voteWeights, and settlementTx as a signed resolution packet.
2. ‣ is the operator surface. It gives the dev team a shared control plane for seeing the event become a task, not just another webhook payload.
3. Ouroboros Gym — Phase 0+2+3+4 Validation Benchmark is the validation argument. It tells devs which claims are benchmarked, which are negative/partial, and which should remain parked until the validation gate passes.
4. DVLO is the alignment contract across those three surfaces: Evidence plane receives the webhook, tool-risk plane decides whether to dispatch, and relational / continuity plane explains the result to humans without collapsing plan into status.

Argument to use between devs

Do not debate whether Polymarket, Ouro, and Ouroboros Gym are separate projects. Treat them as one event-to-proof lane:

• Polymarket webhook: "A resolution happened."
• TAEX / DVLO router: "Is the event signed, relevant, and safe to route?"
• Ouro v1: "Here is the operator-visible execution state."
• Ouroboros Gym: "Here is the benchmark discipline for deciding whether the routed result is validated, failed, or still experimental."
• diamondNode / VDF proof path: "Here is the attestable witness once the lane clears validation."

/maru reframe for the dev dispute

If the dev disagreement is framed as "Should we ship the webhook first, the Ouro interface first, or the benchmark first?", that is the wrong rule. The corrected rule is: