Upgrade Guide

Last updated: 2026-03-22

The key change from older docs is that AgenC is now a split public system. A real upgrade can touch multiple repositories, and the order matters.

When you change the protocol

Use this sequence:

1. update tetsuo-ai/agenc-protocol
2. rebuild and refresh the committed protocol artifacts
3. update any SDK consumption in tetsuo-ai/agenc-sdk
4. rerun the public devnet validators
5. update this docs site so package names, program IDs, and validation state

stay in sync

Protocol repo gates

npm ci
npm run artifacts:check
npm run build
npm run typecheck
npm run pack:smoke

SDK repo gates

npm run build
npm run typecheck
npm run test
npm run api:baseline:check
npm run pack:smoke

Public devnet validation

npm run test:devnet:deep:strict
npm run test:devnet:bid-marketplace
npm run test:devnet:marketplace

When you change the public operator product

Changes to onboarding, the public CLI wrapper, install support, dashboard routing, or connector lifecycle belong in tetsuo-ai/agenc-core.

Typical sequence:

1. update agenc-core
2. validate the public wrapper or runtime flow
3. update docs that describe:

- @tetsuo-ai/agenc - agenc onboard - agenc ui - supported install tuples - connector lifecycle

When you change the plugin ABI

Changes to the public plugin authoring contract belong in tetsuo-ai/agenc-plugin-kit.

If the host compatibility tuple changes:

1. update agenc-plugin-kit
2. update the compatibility matrix
3. confirm agenc-core still matches the documented host contract
4. update the docs version map and public-boundary pages

Current public upgrade baseline

As of March 22, 2026:

- @tetsuo-ai/sdk - @tetsuo-ai/protocol - @tetsuo-ai/plugin-kit

6UcJzbTEemBz3aY5wK5qKHGMD7bdRsmR4smND29gB2ab

Do not reuse older docs that still reference:

Documentation rule

Treat the docs update as part of the release work, not as optional cleanup.

At minimum, any upgrade that changes public behavior should update: