Docs
Gateway
Architecture, runtime operation, integration surfaces, and operator references organized for engineers who need signal fast.
DOCUMENTATION PATHS
Organized around actual work.
Architecture
Principles, execution boundaries, canonical mapping discipline, and why the coordinator remains the orchestration owner.
Runtime Operations
Bring-up, health, loop health, progression metrics, and what 'runtime ready' actually means in local/devnet.
Integration Surfaces
Execution, settlement, release service, and the contracts expected from upstream backends and future URUZ devnet data.
Observability
Flow inspection, mismatch visibility, reconciliation semantics, and why phase views stay derived rather than authoritative.
START HERE
Different roles, different entry points.
Protocol Engineers
- Architecture Principles
- Current Capabilities
- Roadmap
Infra Operators
- Runbook
- Health and Loop Surfaces
- Progression Metrics
Technical Collaborators
- Integration Contract
- Technical Collaboration
- Dashboard Surface
KEY REFERENCES
Go directly to the useful surfaces.
Execution discipline, observability discipline, and canonical flow discipline.
What URUZ VM can already do in local/devnet operation today.
Disciplined sequencing from bring-up through real release primitives and URUZ devnet integration.
Read-only operational surface for health, flows, metrics, and mismatches.
Concrete collaboration areas for engineers, operators, and integration partners.
RUNTIME SURFACES
Inspection first, not guesswork.
URUZ VM already exposes the operational surfaces needed to understand health, loop behavior, canonical flow truth, and reconciliation drift separately.
Process-level health only. Useful, but not sufficient to claim runtime readiness.
Loop state, backoff visibility, and runtime lifecycle for settlement, execution, and release observation.
Progression counters for pending and confirmed stages, plus reconciliation warning and mismatch counts.
Canonical flow list with current state, retry count, errors, and derived phase view.
Execution phase, release phase, and recovery metadata without creating a second source of truth.
Warnings and mismatches from reconciliation so operators can spot drift before guessing.