Skip to main content

Give coding agents the same contract as developers

Kam State adds versioned application state to Amazon Bedrock AgentCore.

Give developers and coding agents the same Kam State contract for AgentCore integration, with version-matched guidance and bounded local inspection.

Merged · local onlyBackend review 2026-10-14 · prelaunchRead this guide as Markdown
Guide context

Give coding agents version-matched Kam State guidance for an Amazon Bedrock AgentCore project. Shared documentation and local read-only MCP tools support contract checks during development.

Give a coding agent the same Kam State contract a developer reads for an AgentCore application. Version-matched guides and five local read-only MCP tools expose State definitions, fixtures and limits, helping teams check guidance and configuration together. Connecting these development tools does not register deployed agent tools or create an AgentCore Gateway integration.

On this page · 3 sections

Give the coding agent the right tools

  1. Read the same contract

    Use version-matched Markdown when planning the AgentCore State integration.

  2. Inspect locally

    The documented MCP tools read bounded local evidence; they do not execute agents.

  3. Authorize remote reads separately

    History access needs its own approved identity and service connection.

Five tools, not a shell proxy#

The server uses stdio with initialization and bounded framing, not a public TCP endpoint. Unknown, null, cross-tool, write, shell, and arbitrary-path arguments fail before project reads.

  1. kam_project_status

    Local configuration and generated-file drift. No live account or IAM check.

  2. kam_view_manifest

    A normalized manifest and configuration fingerprint, not deployed authority.

  3. kam_replay_fixture

    Re-evaluate supplied synthetic scenarios with the real Rust engine, without executing an agent.

  4. kam_reference_atlas

    Selected-reference JSON bytes and explicit omissions, not model-token counts.

  5. kam_docs

    Bundled version-matched documentation.

Generated instructions are reviewable local files#

Generation produces versioned Markdown, llms.txt, llms-full.txt, skills, and a managed AGENTS.md block. Surrounding customer instructions are preserved. Edits to managed content and concurrent source changes are detected.

Generating guidance does not install packages, activate an agent configuration, or register a GitHub workflow. The customer reviews the proposed artifacts and explicitly chooses integration steps.

Read these website guides as Markdown#

Each public guide has a Markdown equivalent generated from the same typed content as the HTML page. The documentation manifest lists both addresses. Availability labels and reviewed source identities are included; unpublished tools are not presented as installed services.

Agent-readable documentation manifest