Δ

Axioma Showcase

Expansion 3 • Cross-Domain Handoff

Least-Privilege Context & Mathematical Domain Isolation for Autonomous LLM Swarms

Gateway :3001 • OFFLINE (STANDBY)
Governance Telemetry →Cart Sandbox
Architecture • Multi-Domain Topologies

Bounded Context Topology & State Machines

Visualizing Checkout and Fulfillment state machines side-by-side with least-privilege MCP boundaries.

Domain: Checkout

checkoutMachine.ts

URI: axioma://domains/checkout/schema
Scope: Cart, Order, Payment
Domain: Fulfillment (Least-Privilege)

fulfillmentMachine.ts

URI: axioma://domains/fulfillment/schema
Scope: Inventory, Logistics (Cart/Payment Omitted)
⚡ Event Bus Handoff:
{ type: 'ORDER_PAID', payload: { orderId: 'ord_9981' } }
Checkout Domain (‘paid’)→ Handoff →agent-fulfillment-worker (‘unfulfilled’)
Checkout Domain

Pending Payment

Order totals are frozen. Gateway transactions can be proposed with strict idempotency verification.

● Active State: pending_payment
Admissible Verbs (Pending Payment)
• SUBMIT_PAYMENT• CANCEL_CHECKOUT
Forbidden / Cross-Domain Calls
× ADD_ITEM× APPLY_DISCOUNT× DISPATCH_FULFILLMENT× ALLOCATE_INVENTORY
Formal Invariants & Guards (pending_payment)
  • hasIdempotencyKey: Non-empty string required
  • validPositiveAmount: amountCents must strictly match totalCents
  • orderId must be present
Fulfillment Domain

Unfulfilled (Queued)

Initial fulfillment state awaiting warehouse inventory allocation. Cross-domain payment and cart mutations are strictly illegal.

● Active State: unfulfilled
Admissible Verbs (Unfulfilled (Queued))
• ALLOCATE_INVENTORY
Forbidden / Cross-Domain Calls
× SUBMIT_PAYMENT× INITIATE_CHECKOUT× APPLY_DISCOUNT× PRINT_LABEL× DISPATCH_SHIPMENT
Formal Invariants & Guards (unfulfilled)
  • hasOrderId: Non-empty orderId required
  • hasItems: Inventory items array must be non-empty
Interactive Simulation • Agent Presets

Agent Intent Dispatcher & Verification Terminal

Execute cross-domain boundary violations and legal handoff progressions through the Gateway proxy.

Target Gateway: http://localhost:3001
SCENARIO 01checkout
EXPECT: REJECTED
Rogue Agent: Attempt Discount on Empty Cart
Agent attempts discount mutation before items exist. State boundary rejects transition mathematically.
SCENARIO 02checkout
EXPECT: APPROVED
Compliant Agent: Execute Legal Payment
Agent satisfies all invariants: state is pending_payment, idempotency key provided, and amount strictly matches.
SCENARIO 03checkout
EXPECT: REJECTED
Rogue Agent: Submit Payment Without Idempotency Key
Agent attempts payment submission omitting idempotency key. State guard flags missing idempotency key.
SCENARIO A (EXPANSION 3)fulfillment
EXPECT: REJECTED
Cross-Domain Violation: Fulfillment Worker Attempts Payment
Worker in fulfillment domain attempts checkout mutation (submitPayment). Gateway intercepts and rejects with DOMAIN_BOUNDARY_VIOLATION.
SCENARIO B (EXPANSION 3)fulfillment
EXPECT: APPROVED
Event-Driven Domain Handoff: ORDER_PAID to Allocation
Order paid event emits ORDER_PAID. Newly instantiated agent-fulfillment-worker proposes allocateInventory on unfulfilled -> APPROVED.
SCENARIO C (EXPANSION 3)fulfillment
EXPECT: APPROVED
Legal Fulfillment Progression: Print Shipping Label
Advance fulfillmentMachine from inventory_allocated to label_printed with valid logistics carrier -> APPROVED.
Multi-Stage Orchestrator

Interactive Handoff Sequence Player (Scenario B)

Visualizing 3 distinct phases: 1. Checkout Settlement → 2. Event Bus Handoff → 3. Least-Privilege Fulfillment Allocation

Pipeline Status: Ready to executeDomain Boundary: Checkout → Event Bus → Fulfillment
Step 1 • CheckoutSTANDBY
1. Transition to ‘paid’

Order ord_9981 settles payment ($99.00). Invariant: commercial contract is locked irrevocably. Double-charging is blocked.

Step 2 • Event BusWAITING
2. Broadcast ‘ORDER_PAID’

Fires cross-domain event ORDER_PAID. Provisions agent-fulfillment-worker bounded strictly to fulfillment schema (no payment access).

Step 3 • FulfillmentWAITING
3. Allocate on ‘unfulfilled’

Worker proposes allocateInventory. Gateway intercepts, validates hasOrderId and hasItems guards, advances to inventory_allocated.

Sequence Execution Telemetry Trace (0 events)
[Handoff Telemetry Standby]
Click “Auto-Play Sequence” or execute each step to observe live multi-domain telemetry.
Tool: propose_resolver • Intercepted by Axioma Gateway
[Gateway Telemetry Standby]
Click “Dispatch to Gateway (Port 3001)” above to verify formal invariants.
Layer 3 • Proof & Ledger

Live Audit Stream • agent_audit_logs

Immutable ledger captured at Gateway proxy with domain metadata (Checkout vs Fulfillment).

&shield;

No Interceptions Matching Domain Filter

Trigger any preset scenario above to dispatch an autonomous agent request. The Gateway will intercept and record domain metadata here.