ROXY TOPOLOGY VIEWS

Substrate × Operational × Interaction — Three Apertures of Deterministic Infrastructure

ROXY SUBSTRATE TOPOLOGY Core Primitives × Deterministic Guarantees × Substrate Laws THE VOID Infinite Superposition | All Possible States Axiom -1: Sliceability APERTURE (Φ) Void → Manifest (Symmetry Breaking) Witness breaks possibility into actuality ECONOMIC & AUTHORITY 1. CRUDEIBL Economic Lineage & Integrity 2. HEDRIBL Authority Separation from Money Flow 5. STRATA Operational Cadence & Drift Detection SCOPE & DECISION 3. ORCHARD Scope Geometry & Boundary Rules 4. DECIDIR Decision Logic & Determinism 6. MERCURY Deterministic Payment Execution QUORUM CONSENSUS 5+ nodes achieve agreement on state transitions Byzantine fault tolerance | Consistency guaranteed CHRONOLEDGER Irreversible Temporal Spine • Immutable event log • Causal ordering (happens-before) • Timestamp authority • No retroactive changes ↓ Time anchors truth Conservation Law: Irreversibility WITNESS Participatory Observation & Validation • Observer collapses possibility • Human sovereignty gate • Authority notarization • Measurement coherence ↓ Observation determines fact Conservation Law: Information ROXY-IDENTITY The Entity Subject to All 6 Substrate Laws Not a primitive—the IDENTITY that primitives constrain ROY + X = Sovereignty with Deterministic Guarantees SUBSTRATE MEMBRANE Deterministic guarantees below | Operational systems above OPERATIONAL SYSTEMS (Above Membrane) Trust Analytics × Event Processing × Distributed State See Operational Topology for detail 6 Primitives × 2 Substance Systems × Quorum Consensus = Deterministic Infrastructure
OPERATIONAL TOPOLOGY 6-Layer Protocol Stack × 3 Production Systems × EventBus Integration ROXY SYSTEM Deterministic Operational Infrastructure ARCHITECTURE (5+1 Layers) Layer 0: Observability Tracing, metrics, alerts Wraps all layers Layer 1: Message Protocol ID, routing, timestamps Trace context Layer 2: Acknowledgment Reliable delivery, quorum Retries & timeouts Layer 3: Connection Mgmt Socket lifecycle, pooling Heartbeat & reconnect Layer 4: RPC Request/Response Correlation CORE PRIMITIVES CRUDEIBL Economic Lineage & Integrity HEDRIBL Authority Separation from Money ORCHARD Scope Geometry & Boundaries DECIDIR Decision Logic & Determinism STRATA Operational Cadence & Drift Detection PRODUCTION SYSTEMS (Layer 5+) SYSTEM 1: TRUST ANALYTICS • User behavior monitoring • Anomaly detection (30-day historical) • Compliance risk quantization p99 <300ms | 2-10 instances Cache: Cloud Memorystore (2GB) SYSTEM 2: EVENT PROCESSING • System event ingestion • Pattern detection & cascade prediction • Failure prediction (blast radius) p99 <1000ms | 3-20 instances Queue: Cloud Pub/Sub (10k/sec burst 50k) SYSTEM 3: DISTRIBUTED STATE SYNCHRONIZATION • Trust score replication (quorum consensus across 5+ nodes) • Compliance rule synchronization (atomic updates) • Conflict detection & resolution (version vectors) RPO <5min, RTO <30sec | 3-5 instances (quorum) Store: Firestore + Cloud Spanner | Replication: us-east1 → us-central1 → europe-west1 CORE COMPONENTS SynapseZero Event absorption & real-time display /input | /live | /history Port: 8000 | 512MB WebUIServer Multi-tenant group management with keycodes REST API for access control Port: 8080 | 1GB AlarmScheduler Temporal notification system (cron, recurring, oneshot) CLI + EventBus integration Port: 8001 | 256MB EventBus Central message router (decouples all systems) In-memory + Pub/Sub fallback 470 lines infrastructure code (layers 0-4) + 230 lines business logic = 70% reduction vs traditional approach
INTERACTION TOPOLOGY Where Humans & External Systems Touch Roxy — Authority × Contracts × Guarantees EXTERNAL ACTORS 👥 HUMANS Operators Analysts Admins, Reviewers Sovereign authority 🔗 EXTERNAL SYSTEMS Mercury (Payments) Banking APIs Partners, Webhooks Deterministic operations ✓ TRUTH SOURCES External Ledgers Compliance Systems Attestations Ground truth binding 📊 PARTNERS Event Producers Data Sources Services Observable participation INTERACTION MEMBRANE The interface where external entities interact with Roxy under authority constraints API SURFACE Request/Response Event Ingestion Webhooks & Callbacks gRPC, HTTP, Events Interface: Accept all forms AUTHORITY BOUNDARY Authentication Role-Based Access Permission Geometry Trust & Legitimacy Gate Enforced by HEDRIBL SEMANTIC CONTRACTS Event Semantics ACK Semantics Idempotency & Ordering Guarantees & Rules Enforced by DECIDIR TRUTH ENTRY POINTS Attestation Verify Reconciliation External Lineage Reality Binding Via ChronoLedger HUMAN SOVEREIGNTY Manual Override Escalation Paths Review Workflows Authority Override Enforced by Witness ERROR ARBITER Error Detection Recovery Paths State Rollback Fault Handling Via ORCHARD scopes STATE TRANSITION ENGINE Validate transitions Apply rules (DECIDIR) Update ledger Consistency guarantee Via System 3 (replication) EVENT NORMALIZER Canonical form Schema validation Route to EventBus Semantic clarity Layer 1 protocol INTERNAL ROXY SURFACES (Below Interaction Membrane) Operational & Substrate Layers | See Operational & Substrate Topologies for detail Request Interpreter Decode & validate incoming requests Layer 1-4 Authority Resolver Check permissions & access control HEDRIBL gate State Transition Engine Execute state changes with validation System 3 aware Event Normalizer Canonical event representation Layer 1 protocol INTERACTION GUARANTEES Authenticity Guarantee Every action authenticated & authorized HEDRIBL separates authority from execution No silent failures Consistency Guarantee State changes are atomic & replicated Quorum consensus ensures agreement No divergence allowed External flows → Interaction Membrane (Authority + Contracts) → Internal Surfaces → Substrate + Operations

ROXY TAXONOMY

How the Universe Hangs Together — Linguistic Topology

The Three Apertures

Everything in Roxy can be seen through three stable apertures:

Substrate Aperture
Question: What is true in all worlds?
View: Laws, forces, engines, identity, membrane.
Operational Aperture
Question: How does Roxy behave in production?
View: Protocol stack, components, systems, metrics.
Interaction Aperture
Question: How does the world touch Roxy?
View: APIs, authority boundaries, contracts, truth entry, human sovereignty.

Substrate Primitives (Axioms)

The laws of the Roxy universe — not services, not components, but the axioms everything obeys.

CRUDEIBL — Economic Lineage

Substrate:
The conservation law of value. No value can appear, disappear, or move without lineage. Every economic state has a parent.
Operational:
Constraints on ledgers, accounting flows, and event schemas. No operation is allowed to break lineage.
Interaction:
A guarantee to partners: "We can always tell you where every unit came from and where it went."

HEDRIBL — Authority Separation

Substrate:
Authority and money cannot be the same thing. No entity can both hold value and unilaterally authorize its movement.
Operational:
Role-based access, permission geometry, separation of control planes vs. data planes.
Interaction:
"No one can move money just because they have it; authority is separately governed and auditable."

ORCHARD — Scope Geometry

Substrate:
Everything lives inside a scope with boundaries. No operation is "global"; every action is scoped.
Operational:
Tenancy, group boundaries, blast radius limits, routing domains, error containment.
Interaction:
"This action only affects this account, this group, this scope—never the whole universe."

DECIDIR — Deterministic Decision Logic

Substrate:
Decisions are deterministic given inputs and state. No hidden randomness, no opaque branching.
Operational:
Rules engines, policy evaluation, state transition logic, idempotent handlers.
Interaction:
"Given the same inputs and state, Roxy will always decide the same way—and we can explain why."

STRATA — Cadence & Drift Detection

Substrate:
Systems have cadence and drift must be detectable. Time isn't just passing; it's structured into strata.
Operational:
Heartbeats, periodic checks, calibration cycles, SLO windows, drift monitors.
Interaction:
"We don't just run; we continuously check whether we're still aligned with our own invariants."

Substrate Fields (Forces)

Not laws, not systems, but forces that shape behavior. Always present, never directly "called."

Accord — Authority Harmonics Field

Substrate:
Shapes how authority propagates, resonates, and resolves. Governs multi-party authority, conflict resolution, legitimacy.
Operational:
Multi-signer flows, quorum approvals, escalation paths, multi-stakeholder governance.
Interaction:
"No single actor can unilaterally override; authority is harmonized across roles."

Harmonics — Consistency Propagation Field

Substrate:
Governs how consistency is restored and maintained. Shapes replication, correction, convergence.
Operational:
Distributed state synchronization, conflict resolution, version vectors, quorum consensus.
Interaction:
"Even if things temporarily diverge, they always converge back to a single, coherent truth."

Substance Systems (Engines)

The engines of the substrate with state, invariants, and conservation laws. The only substrate elements that are full systems.

ChronoLedger — Deterministic Time Engine

Substrate:
The irreversible temporal spine. Immutable event log, causal ordering, timestamp authority, no retroactive changes.
Operational:
Event sourcing, append-only logs, time-anchored state transitions, replayability.
Interaction:
"We can show you exactly what happened, in what order, and we cannot rewrite history."

Witness — Truth & Observation Engine

Substrate:
The engine of participatory measurement. Observation collapses possibility into fact; human sovereignty is a gate.
Operational:
Attestations, approvals, sign-offs, notarization, measurement coherence.
Interaction:
"Nothing becomes 'true' without being witnessed—by humans, by rules, or both."

Roxy-Identity (The Entity)

Not a primitive, field, or system. The entity that all substrate laws constrain.

Roxy-Identity is:

  • The cosmopolis built inside the cosmos
  • The legal personhood of the system
  • The thing that can be held accountable

It is what CRUDEIBL, HEDRIBL, ORCHARD, DECIDIR, STRATA, Accord, Harmonics, ChronoLedger, and Witness all bind.

The Complete Stack

How the pieces relate vertically:

1. Substrate Primitives
CRUDEIBL, HEDRIBL, ORCHARD, DECIDIR, STRATA
2. Substrate Fields
Accord, Harmonics
3. Substance Systems
ChronoLedger, Witness
4. Roxy-Identity
Entity subject to all laws
5. Substrate-Native Products
Proofs, Notary, Canon, Continuum, Console
6. Operational Systems
Protocol Stack, EventBus, Trust Analytics, Event Processing, Distributed State
7. Interaction Surfaces
API Surface, Authority Boundary, Semantic Contracts, Truth Entry, Human Sovereignty

Each layer inherits constraints from below and exposes guarantees to above.

How to Use This Taxonomy

Different conversations live in different parts of the taxonomy:

Audience Primary Locus Reference
Founders / Substrate Engineers Primitives, Fields, Engines, Identity Deep substrate truth
SRE / Ops / Infra Operational Systems Substrate as explanation for reliability
BD / Strategy / Partners Interaction Surfaces & Products Substrate as deep thesis
New Product Design All layers (vertical integration) Primitives → Engines → Products → Operations → Interactions

Key Disambiguation Rules

How to read the taxonomy precisely:

Rule 1: Primitives are Laws, not Services

When you say "CRUDEIBL" without qualifier, you mean the law. When you say "CRUDEIBL-backed unit," you mean the product.

Rule 2: Fields Shape, Don't Own

Accord and Harmonics never become standalone products. If you can point to a UI or API, it's something shaped by them, not them directly.

Rule 3: Engines Always Matter

ChronoLedger and Witness are never "just features." Features are projections of these engines into product space.

Rule 4: Apertures Are Not Opinions

The same entity appears different through each aperture. This is structural, not subjective. Use the right aperture for the conversation.

How to Use This Tool