<aside> 🔌

Single artifact. This is the unified plugin + skill + MCP server spec that lets Enid, devs, and canary users connect into the Genesis Conductor / TAEX / diamondNode infrastructure with one click. Includes a self-destruct mechanism agents can execute autonomously.

</aside>

<aside> ⚡

Primary sources: Optimization Inversion — Category Pivot Command Center · /maru · TAEX Intent Router — Agent-Based Routing with Dissonance Memory MCP

Incorporated this revision (2026-05-19): ‣ · ‣ · ‣ · ‣ · ‣ · ‣ · ‣ · ‣ · ‣ · ‣ · DVLO — Dyadic Verifiable Lane Orchestration: A Three-Plane Agent Architecture (Genesis Conductor × LidLift × Lane Harness × Edins Dyadic/PEAN × Instinct/DWE) · Skills Activation Manifest — Planned + In-Development → Operational (Greg · DVLO · diamondNode · Retraining Loop) · ‣ · diamondNode Phase 1–4 Execution · ‣ · ‣ · DiamondNode ↔ Notion ↔ Postman — Sync Status (2026-05-10) · ‣

</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>

Thesis

The Genesis Conductor ecosystem has five operational planes (DVLO), a category term to own (Optimization Inversion), an intent router (TAEX), a memory substrate (Dissonance MCP), a constraint-reframe primitive (/maru), and an audit-node delivery vehicle (diamondNode). Today these are separate specs. This plugin collapses them into one installable surface — a single MCP server that any agent, IDE, or chat client can connect to and immediately participate in the agentic mesh.

The build-out path:

  1. Phase 0 (this plugin) — Read-only discovery + intent submission. Enid and canary users connect, explore capabilities, submit intents. No write authority. No settlement.
  2. Phase 1 — Write-path activation. Connected agents can execute routed tasks, store memories, trigger Yennefer thermodynamic gates. LidLift enforces tool-risk scoring on every write.
  3. Phase 2 — Settlement loop. EulerCycleAttestor v2 settles completed cycles, mints KVDF NFTs. Agents earn on-chain provenance for work done through the plugin.
  4. Phase 3 — Self-evolving mesh. Retraining Worker monitors routing stability (TAO invariance score), promotes improved classifiers via the plugin's own update channel, and the plugin auto-upgrades without operator intervention.

Every phase is gated by the self-destruct mechanism: any agent with Guardian-level authority can trigger a controlled shutdown that preserves audit logs but revokes all write permissions, freezes memory, and emits a final capsule event. This is not a panic button — it is an architectural invariant that ensures the mesh can always be unwound cleanly.

<aside> 🛰️

A2A Operationalization Index — single source-of-truth for upstream/downstream graph, next-step + execution location, A2A JSONL prompts, and model variant specificity across the 18-page spine: A2A Operationalization Index — Spine Footers, JSONL Prompts, Model Variants, Permissions.

</aside>

Incorporation Map — how each surface plugs into this plugin

Every surface below is either a producer the plugin subscribes to, a service the plugin proxies, an operational gate the plugin defers to, or a charter the plugin inherits. Single envelope (envelope_version: 0.3.0), single attestation lane (diamondNode /api/vault/attest), single ops surface (W-OPS), single audit log (Soul Capsule projection).

Surface DVLO plane Role in plugin Plugin tool(s) affected
‣ Charter (anti-fabrication, brand separation, reversibility, Trace-as-Consent) Inheritance — the plugin enforces §6.17's four invariants on every write tool; AI World Architect's "Send to Enid" action is the first canary gc.intent.execute template. gc.intent.submit, gc.intent.execute
‣ Execution / evidence Service binding YENNEFER — gc.thermodynamic.evaluate returns {eta_thermo, inversion_gap, regret_eth, confidence, caveats} against the daemon's proof contract. IO-bound short and IO-bound long routes are blocked when η < 0.3. gc.thermodynamic.evaluate, gc.intent.execute (gate)
‣ Relational / continuity Read-only memory spine surfaced through gc.memory.recall when scope="soul" — Dreams / Insights / Evolutions from /dev/shm Soul lattice; coherence + breath_token + lattice strength carried in recall response. gc.memory.recall
‣ Tool-risk Visual hub for the Yennefer surface. Mistral vibe-cli (diamondnode-bound) replaces Kimi inside the Yennefer repo only; podman P0 runtime directive yennefer.runtime.podman.001 is scoped to the Yennefer repo and does not propagate to Skills Activation Manifest, kimi.task.submitted capsule keys, or gc-mcp-server transport labels. gc.discover (registers mistral-vibe-cli as yennefer-site-only task agent)
‣ Tool-risk Reach-multiplier-ranked external surface registry. Plugin auto-publishes itself as a row (Platform: Webhook · Auth_Type: API Key · Endpoint: mcp.genesisconductor.io/v1 · Status: Testing until first attested intent.execute, then Active). gc.discover (publishes row), gc.health (flips Status)
TAEX Intent Router — Agent-Based Routing with Dissonance Memory MCP Relational → Tool-risk Internal pipeline executed by gc.intent.submit/gc.intent.execute: classify → memory.dissonance_check → Yennefer gate → Decision Matrix dispatch. TAO invariance score feeds gc.health. gc.intent.submit, gc.intent.execute, gc.health
‣ Execution / evidence Plugin emits intent.classified, dissonance_detected, routed, deferred, reframed, self_destruct as capsule events on the same AAL bus the Retraining Loop subscribes to. Promotions of the plugin's own classifier walk wind→arm→release→settle on EulerCycleAttestor v2 (§5.22). all tools (producer); plugin classifier promotion via gc.settlement.settle
‣ Cross-plane Defines the unified envelope (envelope_version: 0.3.0) and the Yennefer ↔ A2N ↔ Forge ↔ diamondNode ↔ .sol trace. Plugin uses this envelope verbatim for every outbound capsule write. internal — envelope contract for all tools
‣ Execution / evidence Positioning sentence ("Optimization Inversion is not merely inverse optimization or interpretability…") is embedded verbatim in gc.discover response under pillar.positioning. gc.discover
‣ GTM / Doctrine Public doctrine surface. gc.discover exposes the three Extropica partner tracks (Research / Hardware / Institutional) as the recommended onboarding tracks for new dev-tier keys. S-ToT Diamond State attestation flows through gc.settlement.settle. gc.discover, gc.settlement.settle
‣ Health / Visibility Plugin appends one row per ops slot under ### Plugin Status (active connections, observer/canary/dev/guardian counts, TAO invariance score, last self-destruct event, drain mode flag). Escalation rule: invariance < 0.4 for 3 slots → W-OPS marks slot RED and dispatches health orchestration. gc.health (W-OPS read), all tools (emit)
DVLO — Dyadic Verifiable Lane Orchestration: A Three-Plane Agent Architecture (Genesis Conductor × LidLift × Lane Harness × Edins Dyadic/PEAN × Instinct/DWE) All three planes (canonical) Plugin's three policy tiers map onto DVLO's three planes — observer/canary read from Relational, canary/dev write through Tool-Risk, dev/guardian settle on Execution. Every plugin tool declares its DVLO plane in gc.discover. all tools (plane declaration)
Skills Activation Manifest — Planned + In-Development → Operational (Greg · DVLO · diamondNode · Retraining Loop) Producer / consumer registry Plugin registers genesis-conductor-plugin as a Skill row (Parent: Integration, Status: In Development); the §3 transport table is the canonical transport spec — plugin uses AAL /v1/capsule, gc-mcp-server stdio, diamondNode /v1/attest, and EulerCycleAttestorV2 WIND→ARM→RELEASE→SETTLE. gc.discover (Skills/Agents row registration)
‣ Risk Closed reference — confirms the canonical product name AI World Architect (not ErosGenesis) and the 90-day redirect requirement on any erosgenesis-* worker. Plugin enforces brand strings via gc.intent.submit validator. gc.intent.submit (name validator)
diamondNode Phase 1–4 Execution Infrastructure plan Phase 1 work-package gates the plugin: gc-diamond-node Worker must be deployed at dn.genesisconductor.io with secrets DIAMOND_NODE_ED25519_PRIV • DIAMOND_VAULT_AUDIT_URL • WORKER_AUTH_TOKEN before the plugin's Phase 1 write-path goes live. deployment dependency
‣ Historical context Preserved trace. Canonical plan is v1.1 (Path B, dn.genesisconductor.io). Plugin must not target node.diamondvault.io until Phase 5 (parked) reopens. —
‣ Implementation The plugin Worker is a sibling of the diamond-node Worker — same Cloudflare account, same Ed25519 identity pattern (kid dn-2026-05), same /audit/replay ring-buffer convention. Plugin reuses the scaffold's src/identity.ts and src/health.ts verbatim. Worker source layout
DiamondNode ↔ Notion ↔ Postman — Sync Status (2026-05-10) Smoke surface The notion-bridge Worker pattern (Bearer auth → Notion API write) is the template for the plugin's gc.memory.store → Notion mirror path. Postman smoke collection (uid 38055243-22152fdd-…) is forked for plugin smoke tests. gc.memory.store (Notion mirror)
‣ Witness / attestation gc.settlement.settle calls POST dn.genesisconductor.io/api/vault/attest with artifact_type="plugin_cycle_settlement", artifact_id=cycle_id, payload={pareto_scores, route_plan, kvdf_tokenId}. Returns payload_sha256 • signature_ed25519 for the Soul Capsule projection. gc.settlement.settle, gc.memory.store (any attested artifact)

Self-destruct hooks into each surface

When gc.self_destruct fires, the 6-step sequence (§4) propagates as follows: