HYBRID DEVNET · PUBLIC EVIDENCE LIVEVerifiable infrastructure for value, markets, identity, and operational dataInspect the network

Products & integrations

Does preparing a contract in Contract Studio deploy it?

3 min read

No. Preparation returns an unsigned deployment request. It does not sign, broadcast, or deploy the contract. Artifact review, authority analysis, and governance evidence must not be represented as completed execution.

Preparation creates something to review

Contract Studio’s preparation boundary returns an unsigned deployment request. That gives a team material to inspect before a consequential action. It is not evidence that a contract exists on the destination network. Think of the difference between preparing a document for signature and completing the signed agreement: the preparation may be important, but it does not perform the later step. The interface and any report should preserve that distinction.

Review more than the visible name

The team should identify the exact artifact, intended network, relevant configuration, and authority involved. An artifact is the specific software or prepared object being reviewed, not just its friendly title. Ask who can approve the version, what can change afterward, and what separate process would sign and broadcast it. A governance decision about one version should not silently apply to a different version. Keep the review reference attached to the actual subject considered.

Establish completion through the owning workflow

If deployment is separately enabled, its signing, broadcast, and confirmation conditions must be checked through that workflow. A successful preparation response does not establish any of those outcomes. During evaluation, test that the application presents an unsigned request as unsigned and does not claim a live contract prematurely. If a later request has an uncertain outcome, reconcile the existing reference before retrying. Keep deployment authority separate from the ability to browse or prepare an artifact.

In plain language

Permission, signing, and completion are different

Think of a business bank payment: preparing the instruction, approving it, and seeing it complete are separate events. A wallet workflow also has distinct responsibilities. Authorization means the required person or policy permits a particular action. Signing means the participating systems produce the cryptographic signature needed for that action. Completion means the relevant system has accepted or settled the result under its rules. A screen displaying a wallet, or a service responding successfully, does not combine these steps into one. In Hybrid-Chain, customer authorization is separate from distributed signing participation. When reviewing a status, ask which of these stages it describes, which asset and network it concerns, and whether the evidence is current. This distinction helps prevent a common mistake: treating an informational record as permission to move money. An operator should be able to explain the stage in ordinary language without asking you to share any secret material.

In plain language

What an API contract tells your team

An API is a way for one application to ask another system for information or an action. The operation contract is the detailed description of that particular request: what information to send, what access is required, what a response means, and which errors can occur. It is more precise than a product overview. A read normally retrieves information; a write can create or change something and therefore needs more careful handling. Developers should use the current contract for the deployed environment rather than guessing from a similar endpoint or an old example. Business users can help by stating the outcome in ordinary language and naming who may authorize it. Both sides should agree how to identify the request later, what happens if a response is delayed, and which record establishes completion. These details turn a demonstration into an integration that people can operate responsibly.

What to do next

Review the exact operation and network availability before arranging a separately authorized release.

Contract Studio ↗Governance & Approvals ↗