Deployment Manifest Update

Scope

Use this runbook whenever a deployed address, chain id, token, controller, hook, or executor value changes.

Authority Required

Repository write access and deployment authority for the chain being changed.

Procedure

1. Generate the manifest from the deployment script when possible.
2. Review the diff for chain id, address, token decimals, hook, controller, and signer-related values.
3. Check the interface catalog if the frontend needs to expose the market.
4. Run local docs and secret checks before merging.
5. Use the manifest path explicitly in operational commands until the default is intentionally changed.

Verification

make env-check MANIFEST=deployments/manifests/11155111-registered-issuer-m1-staging-active.json
pnpm --filter docs types:check
git diff --check

Rollback

Revert the manifest change and restart any services that cached it. If the wrong manifest was used for live signing, stop quote issuance until payloads expire or policy invalidates them.

Source Files

• deployments/manifests/
• interface/public/manifests/catalog.json
• interface/src/lib/manifest.ts
• Makefile