Deployment records and authority
For a first release, follow Deploy a new instance. This page explains what its retained files mean and what must remain private.
Defaults do not rewrite saved work
Keep one operator-owned instance directory outside the checkout, mode 0700. Protected configurations are owner-only 0600 regular files, not symlinks. Commands allocate their own output directories; do not pre-create empty phase outputs.
instance/
config.json
instance.json
deployments/
updates/instance.json points to configurations, the selected publication and unfinished work. It is not a second address registry or a live-readiness certificate. A saved operation's selection.json and retained inputs/ identify its chosen components, source revision, settings and exact approval image. Input records reference the protected credential file rather than copying its key or private RPC URL.
Setup offers full, business-creator, projection-deployer and CAM-owner configurations. Separate business-config.json, ui-config.json and cam-config.json can assign different actors; instance.json retains their references. A full configuration can supply all phases. Editing those defaults does not change an already saved operation.
Each phase owns its evidence
| Artifact in a full operation | What it records |
|---|---|
contracts/artifact/contract-deployment.json | Business creation and required initialization, including observed administration and pending handoffs. |
ui/artifact/ui-deployment.json | The read-only projection's creation, runtime and backing dependency. |
cam-bundle/artifact/cam-bundle.json | Selected component evidence, original ABIs and hashes of prepared publication resources. |
cam/artifact/cam-publication.json | The completed CAM root publication. Only matching completion advances the instance's selected publication. |
Independent operations retain only their relevant phases. Signed phases also retain plans, broadcasts, approval evidence and logs. Keep the whole instance, including failed attempts; a later UI deployment can depend on an earlier business artifact.
Original artifacts choose original source and ABI export. A projection may use an earlier compatible backing contract; verification of identity does not prove arbitrary interface compatibility. Historical verification preserves completed artifact bytes and does not certify current owners, roles, balances or pause state.
Minimal inputs differ by operation
A signed schema-version-3 configuration supplies the app, selected sourceCommit, RPC, protected deployer key, approval image and operation-specific settings. Chain and expected-deployer settings are strings. confirmDeploy: true is not transaction approval.
Keyless bundle preparation instead needs the app, authored CAM source, RPC and expected chain; it needs no signing key, approval image, output directory or CAM URI. Setup offers the signed purposes above; a protected read-only configuration can be written explicitly. On records-only machines, use the paths referenced by the saved operation, not replacement top-level defaults.
Persistent-local configurations retain their selected Docker network, http://release-anvil:8545 and chain 31338. These are different from the disposable browser demos on chain 31337. See local release practice.
Approval images are saved signing inputs
Setup and new signing operations resolve the approval tool automatically. An installed saved image remains pinned. Otherwise, compatible tool inputs can reuse an image or build one through the locked dependency stage. The tool's source revision need not equal the app's source revision.
A saved signing operation requires its recorded image: restore that exact image if removed. Keyless record verification does not need it. Operator images remain available to other instances; a rehearsal removes only its own tagged image after its processes and containers stop.
For an explicit image build, use make release/approval/image/build. It records the source and image identity in its printed external directory. SOURCE_COMMIT chooses a committed tool revision; RELEASE_APPROVAL_IMAGE_OUTPUT_DIR chooses an explicit external records location. A build record is an output, not a second approval decision.
Private files and the selected Docker engine
Host-owned release and CAM-maintenance tools measure the selected Linux engine's default user namespace and choose the container UID/GID that maps to the invoking host owner. Rootful and operator-owned rootless engines do not require chmod, chown or LOCAL_UID=0 workarounds. Unknown mappings or unconfirmed probe cleanup stop before private inputs are opened.
make tests/live/release-identity DOCKER_CONTEXT=your-local-contextThis checks a synthetic 0700 directory and 0600 files: read, create, replace and delete, including host ownership and cleanup. It mounts no deployment instance and uses no signing credential. Qualify each engine separately; a rootful CI result does not qualify a workstation's rootless engine.
The host probe needs Python 3.11+ and checksum-pinned linux-idmap 0.3.1. First use acquires its wheel under ~/.cache/release-idmap/; later runs check and reuse it without pip. The selected engine also needs the pinned probe image, acquired by release commands before probing. This supports local Linux engines, not remote-Docker or Docker Desktop bind-mount semantics.
Successful checks remove their scratch resources. Failed or cancelled checks attempt bounded cleanup and report any retained directory/log. Image and wheel caches remain reusable. Fixed-identity services retain their own policy.
Nomination is not acceptance
Business administration and CAM publication ownership can belong to different accounts. Each nominee accepts on the specific contract identified by its phase artifact. Bike Components and Manager administrator transfers also observe their configured chain-time delays. Until acceptance, the current authority remains in control.
CAM ownership changes use transferOwnership(newOwner) followed by the nominee's acceptOwnership(). A proposed owner cannot publish before accepting. Editing a configuration or verifying a historical nomination changes no deployed authority.
Source: artifact selection and configuration ownership, publication completion, and identity mapping. Use Recover an interrupted release for the decision procedure.