30 Concepts, One Architecture: The DUAL Platform Overview

We've covered five core principles:

• Tokens with mutable state that evolves as assets change
• Compliance rules embedded in token logic, executed in constant time
• An Event Bus that atomically coordinates token state changes across ecosystems
• Geofencing that locks tokens to physical boundaries
• Agent Mandates that govern autonomous AI with embedded governance

These five properties combine into a single unified architecture. The proof is that DUAL handles 30+ completely different tokenization patterns—from pharma supply chains to carbon credits to water rights to AI procurement—using the same four-layer stack.

This is our finale: showing how diverse concepts unite under one architecture.

The Four-Layer Stack

Every DUAL token, regardless of industry, follows this pattern:

Concept Mapping: Same Stack, Different Industries

Let's map four concepts from different industries to the four-layer architecture. All use the same stack; only the data and rules change:

Concept 1: PharmChain (Healthcare Supply Chain)

Layer	PharmChain Implementation
Asset Definition	Pharmaceutical batch with cold-chain requirements (2-8°C), custody chain, manufacturer, patient destination
State Logic	MANUFACTURED → PACKED → IN_TRANSIT → IN_WAREHOUSE → DISPENSED. On state transition, verify cold-chain compliance. If temperature breach exceeds 15 min, transition to QUARANTINED.
Integration	IoT temperature sensors fire events. Event Bus receives sensor data. Token evaluates compliance rule. If breach detected, emit TEMPERATURE_EXCURSION event. Webhook alerts manufacturer & FDA audit system.
Query & Audit	FDA auditor queries token. Sees full state transition history with timestamps and signatures. Proof of integrity: every state change is immutable, every event logged.

Concept 2: Perpetual Yield (DeFi Sustainable Finance)

Layer	Perpetual Yield Implementation
Asset Definition	Sustainable income token backed by real-world cashflows (renewable energy, agriculture, forestry). Includes payment schedule, investor allocation, risk tier.
State Logic	ACCRUING → PAYMENT_DUE → DISTRIBUTED. Each month, accrue interest. On distribution day, verify escrow has sufficient funds. If yes, transition to DISTRIBUTED and calculate payouts.
Integration	Oracle fires monthly event: "Underlying asset generated $X revenue." Token recalculates yield. Event Bus emits YIELD_CALCULATED. Payment service subscribes and executes transfers to investor wallets.
Query & Audit	Investor queries token to see YTD yield earned, next payment date, escrow balance, underlying asset performance. All data is deterministic from the token state.

Concept 3: Conditional Trade (Cross-Border Commerce)

Layer	Conditional Trade Implementation
Asset Definition	Trade contract token with conditions: buyer sends $X, seller ships goods, shipping company provides proof of delivery, insurance approves claim. Only then does payment release.
State Logic	PENDING_CONDITIONS. On each event (shipment created, delivery confirmed, insurance approved), evaluate remaining conditions. When all true, transition to FUNDS_RELEASE_AUTHORIZED.
Integration	Shipping API fires DELIVERY_CONFIRMED event with GPS proof. Insurance system fires CLAIM_APPROVED event. Token receives both, verifies conditions met, emits PAYMENT_READY. Payment service executes transfer.
Query & Audit	Buyer, seller, and insurer all query token to see current state: "What conditions are pending?" Token returns: "Delivery confirmed ✓, Insurance pending ✗, payment waiting for insurance."

Concept 4: Agent Mandates (AI Procurement)

Layer	Agent Mandate Implementation
Asset Definition	Governance token for AI agent. Includes spending limits, approved vendors, compliance rules (SOX, AML), escalation thresholds.
State Logic	On transaction attempt, check: spending limit OK? Vendor approved? Pricing within cap? AML check pass? If all true, allow; update YTD_SPENT. If any false, deny with reason.
Integration	Agent submits transaction to Event Bus. Token receives transaction event, evaluates rules in O(1) time. Emits TRANSACTION_APPROVED or TRANSACTION_DENIED. Payment service or rejection service reacts accordingly.
Query & Audit	CFO queries mandate token: "How much has agent spent? What vendors used? Any compliance violations?" Token returns full audit trail with transaction-level detail and reason for approval/denial.

The Pattern Library: Five Universal Patterns

Across all 30 concepts, we see five recurring patterns:

Why This Architecture Scales Across Industries

The genius of DUAL's architecture is that the substrate is universal while the semantics are domain-specific.

Universal substrate:

• Mutable state transitions
• Embedded compliance rules (O(1) execution)
• Event-driven coordination
• Immutable audit trail
• Geofencing support (optional)

Domain-specific semantics (defined by each concept):

• PharmChain: cold-chain compliance semantics
• Carbon Integrity: forest coverage & biodiversity semantics
• AquaAlloc: watershed-based water law semantics
• Agent Mandates: procurement & AML semantics

You build a new concept by:

1. Define Layer 1 (asset schema) specific to your domain
2. Define Layer 2 (state logic) with your compliance rules
3. Plug into Layer 3 (Event Bus) for real-world data
4. Query via Layer 4 (audit API)

The same Event Bus handles temperature sensors (pharma), satellite imagery (carbon), government waterflow data (water rights), and API calls (AI agents). The same compliance engine executes FDA rules, carbon project rules, water law rules, and procurement rules. Same architecture, different data.

The Unified Narrative

Here's what makes DUAL unique compared to other tokenization platforms:

Aspect	Traditional Blockchains	DUAL
State Model	Immutable-only (NFTs) or global ledger (Bitcoin/Eth)	Mutable state + immutable history
Compliance	External systems (Oracle, court, auditor)	Embedded in token logic
Coordination	Webhooks, polling, eventual consistency	Event Bus with guaranteed ordering
Physical World	Oracle-dependent (slow, expensive)	Native support (geofencing, timestamps)
Governance	External policies, API keys	Tokens embed governance rules
Execution Time	O(n) or O(n²) depending on blockchain	O(1) constant time for local checks
Audit Trail	Implicit in blockchain; hard to query	Explicit, queryable, designed for compliance

From Concept to Deployment

Building a new concept on DUAL requires minutes, not months. Here's the universal deployment flow — the same four API calls whether you're building PharmChain or Agent Mandates:

Step 1: Define the Template

POST /v1/templates
{
  "name": "PharmChain_Shipment",
  "schema": {
    "immutable": {
      "ndc_code": "string",
      "manufacturer_id": "string",
      "lot_number": "string",
      "manufacture_date": "iso8601"
    },
    "mutable": {
      "current_custodian": "string",
      "temperature_celsius": "float",
      "cold_chain_intact": "boolean",
      "custody_chain": "array"
    },
    "compliance": {
      "dscsa_compliant": "boolean",
      "last_verified": "iso8601"
    }
  },
  "states": ["Manufactured","In_Transit","At_Pharmacy","Dispensed","Quarantined"],
  "transitions": [
    {"from": "Manufactured", "to": "In_Transit", "requires": ["custodian_signature"]},
    {"from": "In_Transit", "to": "Quarantined", "condition": "temperature_celsius > 8"}
  ]
}

Now compare — Agent Mandates uses the exact same endpoint, only the schema and rules differ:

POST /v1/templates
{
  "name": "Agent_Procurement_Mandate",
  "schema": {
    "immutable": {
      "agent_id": "string",
      "issuing_authority": "string",
      "max_single_transaction": "decimal"
    },
    "mutable": {
      "ytd_spent": "decimal",
      "remaining_budget": "decimal",
      "approved_vendors": "array",
      "last_transaction_id": "string"
    },
    "compliance": {
      "sox_compliant": "boolean",
      "aml_check_passed": "boolean"
    }
  },
  "states": ["Active","Transaction_Executing","Suspended","Decommissioned"],
  "transitions": [
    {"from": "Active", "to": "Transaction_Executing",
     "condition": "amount <= remaining_budget AND vendor IN approved_vendors"},
    {"from": "Active", "to": "Suspended", "trigger": "compliance_violation"}
  ]
}

Step 2: Mint a Token

POST /v1/tokens
{
  "template": "PharmChain_Shipment",
  "data": {
    "ndc_code": "0069-3150-83",
    "manufacturer_id": "PFIZER-US-042",
    "lot_number": "PF-2026-04-1892",
    "manufacture_date": "2026-04-01T00:00:00Z",
    "current_custodian": "Pfizer Memphis Distribution",
    "temperature_celsius": 4.2,
    "cold_chain_intact": true
  }
}
// Response: { "token_id": "tok_pharm_7x92k", "state": "Manufactured" }

Step 3: Execute a State Transition

PATCH /v1/tokens/tok_pharm_7x92k/transition
{
  "to_state": "In_Transit",
  "updates": {
    "current_custodian": "McKesson Distribution Hub",
    "custody_chain": ["Pfizer Memphis", "McKesson Nashville"]
  },
  "proof": { "custodian_signature": "sig_mck_a8f3..." }
}
// Compliance engine auto-checks: dscsa_compliant remains true
// Event Bus emits: { "event": "STATE_CHANGED", "token": "tok_pharm_7x92k",
//   "from": "Manufactured", "to": "In_Transit" }

Step 4: Subscribe to Events (Same Bus, Any Concept)

POST /v1/subscriptions
{
  "event_type": "STATE_CHANGED",
  "filter": { "template": "PharmChain_Shipment", "to_state": "Quarantined" },
  "webhook_url": "https://fda-alerts.example.gov/dual-webhook",
  "secret": "whsec_fda_..."
}
// This exact pattern works for ANY concept:
// - Carbon Integrity: filter on "Revoked" state → alert registry
// - Agent Mandates: filter on "Suspended" → alert CFO
// - BuildFinance: filter on "Payment_Released" → trigger bank transfer

Four API calls. Same endpoints. Same Event Bus. The only thing that changes between PharmChain and Agent Mandates is the JSON inside the request body. That's what makes one architecture support 30 concepts.

The 30 Concepts and How They Map

The 30 DUAL concepts are organized by industry, but they share the same architecture:

Healthcare: PharmChain, TrialChain, InsuraGuard

Finance: BuildFinance, Conditional Trade, Perpetual Yield, RealYield

Environment: Carbon Integrity, AquaAlloc, SpectrumAlloc

AI & Governance: Agent Mandates, VotePath, Trust Mesh

Supply Chain: Product Identity Graph, WarrantyChain, HarvestChain

Each concept is a specialized instance of the same four-layer architecture, tuned for its domain.

What Comes Next

We've completed the six-part exploration of DUAL's architecture. You now understand:

• Why tokens must have mutable state
• How compliance becomes code
• Why events coordinate everything
• How location awareness unlocks new economies
• How governance embeds in tokens
• How one architecture scales to 30+ concepts

The next step is implementation. DUAL has extensive documentation, starter templates, and a developer community ready to help you build the next tokenization concept. Whether you're tokenizing physical assets (pharma, agriculture, real estate), digital assets (IP, data, credentials), or abstract assets (carbon, water rights, governance), DUAL's architecture is ready.

Welcome to the future of tokenization. It's not immutable. It's not decentralized for its own sake. It's pragmatic, compliant, event-driven, and capable of handling the full complexity of the real world.

Build your concept. Deploy on DUAL.