From blueprint.To running authority.
Deploy turns a Studio manifest into infrastructure, then refuses to call the network ready until placement, node health, quorum and restart safety match the selected operating model.
Choose where it runs.
Keep the fault model honest.
Infrastructure target and topology are different decisions. Deploy can place the same network architecture on local, Docker, VPS or other qualified infrastructure without pretending the operational guarantees are identical.
BFT4 on Local
Four validator identities are represented independently. A real deployment must preserve authority boundaries and restart-safe identity handling.
Deploy is not “servers are up.”
A MIRCO deployment is ready only when infrastructure and authority agree with the selected operating model.
Infrastructure location is recorded without redefining sovereignty or consensus.
Restart or replacement must not manufacture a new authority identity.
BFT readiness depends on reachable validator quorum, not merely process health.
A network that cannot restart safely is not deployment-ready.
A network that only works once
is not ready.
Stop. Restart. Recover authority. Rejoin safely.
Deploy must treat restart safety as part of the operating contract. Node boot success is insufficient if identities, quorum or recovery state cannot be restored without ambiguity.
Deploy may refuse to continue.
The safest deployment behavior is sometimes to stop, show the reason, and require the architecture or infrastructure to be corrected.
BFT4 needs 3-of-4 quorum. SOLO remains a development/continuity profile and is not BFT.
If a deployment requires a privacy capability that is unavailable in the active environment, Deploy must not silently weaken the request.
Studio may request them. Deploy should realize them only when the active implementation and readiness evidence support the selected profile.
Infrastructure state and network truth
are not the same thing.
Is the node process alive?
Can required authority participate?
Can the selected consensus profile actually make progress?
Can the network recover without authority ambiguity?
Why does MIRCO say this deployment is ready?
Make the blueprint real.
Call it ready only when it is.
From local and Docker to qualified VPS/BFT4 deployment — the deployment surface stays tied to the network’s real fault and authority model. Additional models appear only when their readiness is established.