# Develop locally with the real Rust engine

Inspect State definitions for an AgentCore project with the local Rust toolkit and synthetic evidence, before connecting an authorized service.

Status: Merged · local only. Prelaunch; not a live service guarantee.
Native toolkit 0.1.0 is merged into the backend (PR #176) and qualified in CI as a network-disabled Linux x64 artifact. No public binary release, macOS/Windows distribution, or live AWS connection is offered here.

Reviewed: 2026-10-14.
Backend source: e16b81b4a637acec91f3aed8a71cf5b0f42f0c19.
Native toolkit: merged in PR #176, reviewed at e16b81b4a637acec91f3aed8a71cf5b0f42f0c19.
HTML: /docs/toolkit

## In short

Check State definitions for an AgentCore project before connecting a service. The local toolkit runs the real Rust engine against synthetic inputs and shows proposed file changes before writing them. It does not start an agent, call tools or reach AWS.

**Available today:** The merged candidate is locally qualified for Linux x64. There is no public binary download or live AgentCore connection.

> Test State semantics locally before connecting your AgentCore application.

## Inspect the State contract locally

- **Start from a project** — Use the approved toolkit with the AgentCore application's State definitions.
- **Inspect the synthetic result** — Read exact IDs, limits and missing evidence from real Rust evaluation.
- **Keep the boundary visible** — The local tool makes no AWS, model or agent-tool calls.

## Start with the distribution boundary

This guide describes the native toolkit merged into the backend in PR #176. It is not an installer you can run from a public registry: access requires a separately supplied Linux x64 artifact from the qualified backend CI run, with its exact provenance. macOS and Windows distributions are not qualified.

The website is static documentation. It does not run Rust, create files, read credentials, or attach anything to your AWS account.

[Discuss toolkit access](/support)

[Compare source checkpoints](/updates)

## Inspect the plan before writing files

Run inside an existing application directory with the approved binary on your PATH. init is read-only until --write. generate --check detects drift rather than repairing it silently.

The lab supplies synthetic storage observations and explicit fences. It exercises real Rust decisions, not AWS transactions, a cloud emulator, or an agent execution.

### Local workflow — not a public installer

```bash
# Merged toolkit, no public binary. Use an approved Linux x64 artifact.
# No public installer is available. These commands run locally.
kam init --template deployment-agent
kam init --template deployment-agent --write
kam doctor --json
kam generate --check
kam dev --json
kam replay --scenario invalidated --json
kam atlas --scenario corrected --json
kam qualify --json
```

## One namespace, explicit effects

1. **Configure** — init · config · generate · doctor · env. Plan-first local files and diagnostics. kam doctor is not the remote kam-history doctor.

2. **Exercise** — dev · state · replay · atlas · preview · qualify. Synthetic observations and the actual Rust engine. No live source calls, agent replay, or token estimates.

3. **Inspect & explain** — inspect · docs · skills · mcp · capabilities. Private local reports and read-only agent tools. No hosted console or public share link.

4. **Plan integration** — connect agentcore · promote · rollback. Reviewable connection and local channel plans only. No Gateway attachment or remote rollout.

## Local, preview, and production are not interchangeable

The strict static kam.config.json compiles into a normalized, fingerprinted manifest. Profiles contain environment-variable names rather than secret values. Preview and production cannot fall back to synthetic local execution.

kam doctor checks local config, SDK declarations, and generated-file drift. kam-history doctor is the separate existing SDK command for remote account/onboarding metadata and requires explicitly supplied credentials. Neither is proof of effective deployed IAM.

## Connection and channel commands are plans, not deployment

connect agentcore emits a bounded History read-tool plan with authentication, tenant mapping, schema acceptance, and IAM work still to qualify. AgentCore tooling remains responsible for integration infrastructure.

promote and rollback record local review-channel changes. They do not deploy a policy, restore deleted evidence, or restore revoked permissions. qualify reports local fixture checks, not source-package or live AWS release qualification.