Skip to content

DAE Architecture

Jump to bottom
UnDaoDu edited this page May 1, 2026 · 2 revisions

DAE Architecture

Domain Autonomous Entities (DAEs) are the modular capability surfaces that power FoundUps. Each DAE stewards a bounded domain — streaming, community governance, finance, code intelligence — as a composable unit that can interoperate with other DAEs across the Foundups ecosystem.

The full architecture paper lives at WSP_knowledge/docs/Papers/Architectures_Emergent_Intelligence.md.

Two Scopes of DAE

The term DAE operates at two scales in Foundups:

Macro (FoundUp ↔ FoundUp): Decentralized Autonomous Entity — sovereign FoundUps cooperating through MCP protocols and shared governance. Each FoundUp is an independent economic node.

Micro (within a FoundUp): Domain Autonomous Entity — a modular capability surface such as YouTube DAE, Social Media DAE, Finance DAE, or a sentinel surface. Each Domain DAE exposes a canonical MCP surface (tools, resources, events) while remaining distributed by enterprise domain per WSP 3.

The Four-Layer Stack

The current Foundups architecture is built as four cooperating layers:

┌─────────────────────────────────────────────┐
│         OpenClaw Control Plane              │
│  Operator-facing execution, routing,        │
│  safety preflights, intent classification   │
├─────────────────────────────────────────────┤
│         WRE Recursive Engine                │
│  Pattern recall, coordination, execution,   │
│  outcome storage, recursive improvement     │
├─────────────────────────────────────────────┤
│   Holo_Index + CodeIndex Cognition Surfaces │
│  Retrieval, ambiguity scoring, route hints, │
│  surgical architecture intelligence         │
├─────────────────────────────────────────────┤
│         Sentinels + Telemetry               │
│  Breadcrumb traces, security scans,         │
│  framework drift checks, replayable logs    │
└─────────────────────────────────────────────┘

Five Architectural Axioms

The architecture paper derives five axioms from first principles:

  1. Trust Redistribution — Security through incentive-aligned consensus, not institutional authority. Trust is programmatic — encoded in protocols, not promises.
  2. Explicit State Management — Without a central database, state must be explicitly represented and independently verifiable. Every transition is deterministic and auditable.
  3. Bounded Computation — Heavy processing off-chain, verification and settlement on-chain. This hybrid avoids the "illusion of decentralized AI."
  4. Autonomy & Self-Sovereignty — Through crypto wallets and smart contracts, agents gain economic agency to earn, own, and transact without intermediaries.
  5. Alignment Discipline — Alignment is an architectural stack problem, not just a prompt-engineering problem. Bounded autonomy, explicit gates, auditable traces, constitutional WSP governance.

The Rubik-Cube DAE (MVP Target)

The MVP target for a Domain Autonomous Entity is a fully agentic "Rubik Cube" that stewards an entire capability cluster as a single MCP surface:

  • Exposes a cube of modules via MCP — every sub-module publishes tools/resources/events through a canonical schema
  • Runs under a clear control plane — OpenClaw provides bounded execution, preflights, and policy enforcement
  • Operates continuously — discovers work, executes, verifies outcomes, updates roadmap without waiting for prompts
  • Uses cognition surfaces deliberately — Holo_Index and CodeIndex provide retrieval before workers are spawned
  • Recursively improves through WRE — pattern memory and telemetry form a feedback loop
  • Remains observable and governable — every shard is inspectable; attestation layers available later

This implements WSP 80's cube-level DAE architecture as a functional-distribution pattern.

MCP Coordination Fabric

Model Context Protocol (MCP) is the dominant tool-facing protocol in Foundups:

  • Agent-to-Tool: MCP standardizes interaction between agents and external services via JSON-RPC 2.0
  • Agent-to-Agent: Handled through OpenClaw routing, AI Overseer coordination, and orchestration switchboards
  • Service Discovery: Currently through repo-local manifests and MCP managers; on-chain registry is a future governance extension

The architecture paper also evaluates A2A (Google) and ACP (IBM/Linux Foundation) protocols, finding that bridging web-native protocols into cryptographically anchored networks remains an open challenge.

Governance Evolution

Phase State
PoC (Now) 0102 adjudicates, MCP emits signed events
Prototype Qwen sentinel mediates, Event Replay Archive stores decisions
MVP Chain-agnostic bridges settle outcomes on chosen blockchain
Planet Scale Distributed DAEs subscribe/unsubscribe without code coupling

Draft WSP 96 (MCP Governance & Consensus) defines the phased governance workflow. The system is designed for fully autonomous operation. Policy governance is constitutional — encoded in WSPs, enforced by DAEMONs, and upgraded through the WSP 81 amendment process. No human approval gates exist in the production architecture. At the Sovereign SmartDAO tier, the DAE operates as a self-sustaining economic and governance entity with no external dependency.

Related Pages

Home

Get Started

Architecture

OpenClaw & Execution

Research & Economics

FoundUps

Phases

Discord & Community

Clone this wiki locally