AgenC Protocol Architecture

Last updated: 2026-03-22

The canonical source of truth is the public repository tetsuo-ai/agenc-protocol, which owns:

Current public deployment note

Current validated devnet program ID:

This ID is the public devnet validation target confirmed on March 22, 2026. Do not treat it as a mainnet identifier.

What the protocol owns

The protocol is the shared trust surface for:

Task settlement modes

The current protocol supports three settlement modes:

submit_task_result, accept_task_result, reject_task_result, auto_accept_task_result, and validate_task_result

complete_task_private remains the dedicated private_zk path. It verifies the zk payload and settles privately. It does not share the reviewed public submission flow.

What the protocol does not own

The protocol repository does not own:

Those remain outside the public trust surface.

System relationship

Canonical artifact path

Downstream consumers should treat these protocol artifacts as canonical:

The public npm distribution surface is @tetsuo-ai/protocol, which is derived from those committed artifacts.

Do not treat a local target/ directory in another repo as the canonical artifact contract.

Validation baseline

The protocol repo documents this release-sensitive validation sequence:

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

When the program or IDL changes, rebuild with Anchor before refreshing artifacts.

Public consumption model

Use @tetsuo-ai/protocol when you need:

Use @tetsuo-ai/sdk when you need higher-level client helpers, proof submission, and task lifecycle wiring.

Current protocol status

The public devnet contract was revalidated on March 22, 2026.

Important March 22, 2026 validation points:

persistence fix was upgraded

2MK4S5wp3h2WXt3hMuCDtd88kFNG7rM9VcZDv8coPyAmigHYATVuzDY9CCWxUTjDidictkXYuikMzbCmi7pdwnRr

See /docs/deployment/devnet-validation for the operational validation path.