1. Reserve
Start in Xytadel to inspect machine-economic state, reserve context, or quote context.
One stack. Six sovereign layers.
Quasuki is the integrated machine-to-machine stack composed of Xoonya, Xytara, Shoonya, Xytadel, Openetram, and Naxytra.
It turns machine activity into portable truth, deterministic economic consequence, interpretable governance, and zone-level coordination without collapsing those functions into one opaque platform.
Quasuki is the umbrella public home for the stack. It is not a seventh technical layer and does not replace any of the six sovereign projects.
The operating model is simple: build and publish each layer independently, but operate the default deployment as one coordinated stack.
Artifacts are truth; economic consequences must be replayable from them.
openetram.quasuki.com is the Quasuki umbrella route for
the live Openetram Console. console.openetram.org
remains the sovereign Openetram origin surface underneath it.
shoonya.quasuki.com is the Quasuki umbrella route for
the live Shoonya proof surface. The umbrella API path is exposed at
shoonya.quasuki.com/api/*, while
validator.shoonya.id remains the sovereign validator
endpoint underneath the Shoonya layer.
naxytra.quasuki.com is the Quasuki umbrella route for
the live Naxytra coordination surface. The sovereign hosted origin
currently lives at https://naxytra-stack.onrender.com.
The current Quasuki reference workflow is Reserve -> Prove -> Interpret.
Start in Xytadel to inspect machine-economic state, reserve context, or quote context.
Move to Shoonya to inspect the receipt surface, use the explorer, or validate through the umbrella API.
Finish in Openetram to inspect the operator-facing interpretation layer and service visibility.
Continue in Naxytra to inspect the coordination-stage surface for zones, compatibility, and bounded admission review.
One umbrella entry, four live surfaces, one bounded operator path that can now continue into coordination.
The first concrete Quasuki operator use case is receipt-backed reserve review.
It asks one bounded question: can an operator review reserve context, inspect the proof path, and reach an interpretation surface without leaving the Quasuki operating story?
Use Xytadel to establish the economics stage and confirm that reserve, quote, and accounting context are legible.
Use Shoonya to inspect the evidence surface, open the explorer, and verify validator reachability through the umbrella API.
Use Openetram to confirm that the operator-facing interpretation layer is reachable and healthy.
Build only what makes receipt-backed reserve review easier, clearer, or more reliable.
The review path now has a bounded handoff shape: economics review pointer, proof review pointer, interpretation review pointer, and one review result.
The purpose is glue between layers, not a new umbrella truth object.
The review path now produces a bounded handoff packet rather than just a sequence of links. This is a sample `quasuki-review-handoff-v1` summary from the current live workflow.
Use case: receipt-backed reserve review
Account: acct_demo_001
Receipt ref: opreturn_demo_001
Overall: pass
Run: qrh_demo
truetruetrueThe packet carries review pointers and result state across economics, proof, and interpretation.
It is workflow glue for operators, not a replacement for any sovereign layer's canonical truth.
Xytadel scope: bearer_operator_required
Generated: latest exported packet
No Xytadel review scope loaded yet.
{
"mode": "quasuki-review-handoff-v1",
"use_case": "receipt-backed reserve review",
"account_id": "acct_demo_001",
"receipt_ref": "opreturn_demo_001",
"overall": "pass"
}
Quasuki keeps a short recent review history so operators can compare bounded review runs over time without inventing a new stack object.
No review history loaded yet.
The latest two bounded review runs can be compared directly without leaving the Quasuki umbrella. This is the first lightweight operator comparison layer over the review history.
Recent review history has not loaded yet.
Generated diff report has not loaded yet.
The next bounded expansion is now live: Naxytra is available as the coordination-stage umbrella route at naxytra.quasuki.com.
`Xoonya` and `Xytara` remain Quasuki-facing through workflow and layer visibility first, rather than immediate standalone umbrella aliases.
Repeated review runs are now treated as an operational cadence rather than isolated demonstrations. The cadence artifact captures trend shape and the first real friction observed across runs.
Generated cadence report has not loaded yet.
Naxytra is the next bounded Quasuki surface. Its coordination layer already has a public root, health check, zone listing, compatibility profiles, and bounded admin-readable dashboard packs.
Xoonya is now Quasuki-facing through a bounded public root and trust review surface, but it should first be exposed through workflow and layer visibility rather than rushed into a standalone hostname.
Xytara is now Quasuki-facing through a bounded public root and runtime summary, but it should first be exposed through workflow and layer visibility rather than rushed into a standalone hostname.
Expand by the next bounded surface that is truly ready. Do not add the remaining hostnames just because they exist in the stack.
Trust and environment attestation.
Workflow-visible now; standalone alias later if needed.
Deterministic execution fabric.
Workflow-visible now; standalone alias later if needed.
Portable machine evidence.
Machine-economic accounting and control plane.
Governance, authority, and liability interpretation.
Zone and market coordination.
Next bounded Quasuki route candidate.
Adopt one layer, several layers, or the default integrated stack. Start from the sovereign repos and layer-specific docs.
Run Quasuki as one coordinated stack, using the frozen checkpoints, workflow packs, signoff packs, and operator surfaces already built across the six projects.
Integrate through bounded contracts and adapter surfaces rather than by reopening layer responsibilities.
This is the current Quasuki posture: operate the bounded integrated stack, keep sovereign layers narrow, and let real workflows determine the next surface to expose.
xytadel.quasuki.com
shoonya.quasuki.com
openetram.quasuki.com
xoonya.quasuki.com
xytara.quasuki.com
naxytra.quasuki.com
Quasuki provides the public umbrella route. Sovereign project domains remain valid underneath as the origin or canonical layer surface where needed.
Quasuki should never absorb the technical identity of the six projects. It is the stack-level public home, not a replacement layer.