Deployment Guide

Last updated: 2026-04-30

1. operator installation of the framework product
2. protocol upgrade and validation on public devnet
3. constrained mainnet-v1 canary preparation, which is still evidence-gated

1. Operator installation

For the public framework product, install:

npm install -g @tetsuo-ai/agenc
agenc onboard
agenc start
agenc
agenc ui

Current supported public install tuple for the tagged @tetsuo-ai/agenc@0.2.0 manifest:

agenc-core may contain newer source-level runtime artifact support, but the tagged 0.2.0 manifest remains Linux x64.

This path is owned by tetsuo-ai/agenc-core.

Use the runtime management commands to inspect or refresh the downloaded runtime artifact:

agenc runtime where
agenc runtime install
agenc runtime update
agenc runtime uninstall

2. Protocol upgrade on devnet

The current devnet/canary coordination program address is:

Build and upgrade from the protocol repo:

anchor build

anchor upgrade \
  /absolute/path/to/agenc_coordination.so \
  --program-id 2jdBSJ8U5ixfwgs1bRLPtRRnpZAPm8Xv1tEdu8yjHJC7 \
  --provider.cluster devnet \
  --provider.wallet /path/to/upgrade-authority.json

Protocol upgrades must land before runtime/CLI/explorer builds that depend on new account layouts or new IDL accounts.

3. Devnet validation sequence

After a protocol change, validate against the public SDK scripts rather than a stale one-off Anchor smoke test.

Set:

export AGENC_RPC_URL=https://api.devnet.solana.com
export AGENC_IDL_PATH=/absolute/path/to/agenc_coordination.json
export AGENC_PROGRAM_ID=2jdBSJ8U5ixfwgs1bRLPtRRnpZAPm8Xv1tEdu8yjHJC7

Run the current top-level mainnet-v1 devnet gate:

CREATOR_WALLET=/path/to/creator.json \
WORKER_WALLET=/path/to/worker.json \
WORKER_B_WALLET=/path/to/worker-b.json \
ARBITER_A_WALLET=/path/to/arbiter-a.json \
ARBITER_B_WALLET=/path/to/arbiter-b.json \
ARBITER_C_WALLET=/path/to/arbiter-c.json \
PROTOCOL_AUTHORITY_WALLET=/path/to/authority.json \
AGENC_EXPLORER_URL=https://devnet.agenc.tech \
npm run smoke:marketplace:mainnet-v1:devnet -- --mode all

Run isolated lanes while debugging:

npm run smoke:marketplace:mainnet-v1:devnet -- --mode reviewed-public
npm run smoke:marketplace:mainnet-v1:devnet -- --mode contention
npm run smoke:marketplace:mainnet-v1:devnet -- --mode dispute
npm run smoke:marketplace:mainnet-v1:devnet -- --mode explorer
npm run smoke:marketplace:mainnet-v1:devnet -- --mode operator

The older SDK devnet validators still exist for SDK-level compatibility checks:

CREATOR_WALLET=/path/to/creator.json \
WORKER_WALLET=/path/to/worker.json \
ARBITER_A_WALLET=/path/to/arbiter-a.json \
ARBITER_B_WALLET=/path/to/arbiter-b.json \
ARBITER_C_WALLET=/path/to/arbiter-c.json \
PROTOCOL_AUTHORITY_WALLET=/path/to/authority.json \
npm run test:devnet:marketplace

Private settlement rehearsal is post-v1 marketplace scope. Keep it separate from canary readiness evidence.

4. Current public devnet result

Current canary readiness is evidence-gated. The current code supports a conditional low-value canary only after the final live devnet evidence bundle passes for the exact deployed protocol/runtime/explorer build.

Required proof points include:

Known public devnet caveats:

vote window closes

See /docs/deployment/devnet-validation for the exact dated result and resume flow.

5. Mainnet status

This docs site publishes canary status, not an unrestricted mainnet runbook.

The current status is:

Do not rely on older docs that hardcode:

contract

Use /docs/deployment/mainnet for the current publication status.