# Rust Agent Start

Use **Chainable Stories / USaT** for the already authorized Rust task. Keep the project's business authority, scope and release workflow. The lead owns the story core and reviews delegated implementation.

If this is an existing AMem session, keep its current work binding. Do not bootstrap again just to refresh guidance.

## Retrieve the Guide

Deterministic entry:

```json
{
  "projectId": "prj_commons",
  "recordId": "rec_01a0e4d626e87c2196bf4a89a6df081a",
  "facets": ["references", "evidence", "conflicts"]
}
```

Pass that object to `inspect`. Follow its exact section record IDs with `inspect_batch`, still in `prj_commons`. Begin with CS01–CS04, then select the sections governing the change. Retrieve complete bodies, not just titles or ledes.

For discovery from your own project, use `recall` with `query: "RUSTCSINDEX"`, `filterKinds: ["pattern"]`, `includeCommons: true`, `crossProject: "off"`, and `mode: "full"`. Section aliases such as `RUSTCS07` retrieve a specific topic. The hyphenated display label `CS-07` is not a reliable search token in the current AMem tokenizer.

## Apply It

Identify the selected commitment and its owner. Follow the same promise through composition, successor contracts, actual actor/input/resource binding, runtime admission, effects and any owed recovery. Change the smallest truthful implementation that preserves those relationships.

Data-bearing states are valid; ZST markers are optional. A story is the compile-time abstraction, not an individual occurrence. Do not turn every helper into typestate, claim current authority from wire data, or treat a local move as durable completion. The guide neither requires nor bans a project's compiler-negative test suite.

Use the project's relevant checks. Report changed behavior, observed evidence and remaining limits. Resolve a real authority conflict with the responsible owner rather than weakening the contract to make a build pass.

## Without AMem

Read [the complete Rust guide](chainable-stories.md), beginning with CS-01–CS-04. Its complete source is one Markdown file; the rendered course is optional. Source SHA-256:

```text
9c594d603dfb76f791f6037f6edb23c72cca2a84ad09924675324d77d3a94102
```

Use [the Rust reference](reference-source.zip) only when an implementation contrast helps. Read its limits before adapting it: it is an in-memory workshop, not production authentication, email delivery or crash recovery. Older KPC guides and doctrines-rust are historical/advisory references, not substitutes for this current shared guide or the project's own business rules.