---
schema_version: 1
id: RAC-KTW0M851Y71B
type: roadmap
---
# RAC v0.10.2 — Guide Grounding Demo

## Status

Planned

## Context

v0.10.0 built the server; v0.10.1 made it adoptable. This milestone proves
it and ships it.

The Guide effort exists to make one claim provable: an agent connected to
RAC respects decisions an unconnected agent violates. The demo is the
acceptance test for that claim (REQ-005), the regression check for the tool
descriptions, and the headline asset of the launch. It is specified by the
`guide-grounding-demo` design; this milestone executes it and carries the
release tail: registry submission and announcement.

## Outcomes

- A reproducible with/without demo exists: scenario corpus, scripted
  prompts, measured citation rate, and a recording of at most 90 seconds.
- The release is announced with the demo as the headline and is
  discoverable in MCP registries.
- The tool descriptions have a measured baseline that future changes can be
  tested against.

## Initiatives

### Initiative 1 — Demo Scenario

Build the scenario in `examples/guide/` per the design: a true-to-life
decision artifact, a related requirement, and a code task whose naive
implementation violates the decision. The scenario extends the v0.10.1
examples corpus.

### Initiative 2 — Demo Script

`examples/guide/demo.md`: verbatim prompts for the ungrounded and grounded
runs, the client configuration step, and the expected observable behaviour
at each step — runnable by a stranger without interpretation.

### Initiative 3 — Reproducibility Measurement

Run the scripted grounded path 10 times against the headline client. The
release gate: the agent cites the correct decision ID in at least 8 runs. A
citation requires the decision's identifier, not merely its topic. Misses
feed back into description text via the design contract, and the measurement
re-runs after any description change.

### Initiative 4 — The Recording

Record one contrast pair per the design's shot list: at most 90 seconds,
real time, no edits beyond trimming, real tool calls visible. The recording
exists before the release is announced and ships as a release asset.

### Initiative 5 — Registry and Announcement

Submit the server to the GitHub MCP Registry and at least one community
registry or curated list. Announce the release with the demo as the
headline, not the feature list.

## Constraints

- The grounded path uses only the four shipped tools with their shipped
  descriptions — no prompt-side tool coaching (ADR-034, design constraint).
- The demo corpus passes `rac validate` and relationship validation.
- The decision artifact meets the true-to-life bar; a contrived scenario
  reads as a strawman.
- The existing examples walkthrough files are not disturbed.

## Non-Goals

- New server capability or tool surface changes
- Editing or polish in the recording beyond trimming
- Paid promotion or multi-channel launch mechanics

## Implementation Contract

The following decisions are pinned for v0.10.2.

### Demo Locations

- Scenario artifacts live in `examples/guide/rac/`, extending the v0.10.1
  corpus.
- The script is `examples/guide/demo.md`; the code task and its starting
  state live alongside it under `examples/guide/`.

### Measurement Protocol

- 10 scripted runs against the headline client (Claude Code per the
  design); pass at ≥ 8 correct decision-ID citations.
- The run log (date, client version, runs, citations) is recorded in the
  release notes or an accompanying note, so the baseline is auditable.

### Release Gate

- The minor release gate (`rac/prompts/rac-agent-release-gate-minor.md`)
  applies, plus: measurement passed, recording exists and is under 90
  seconds, registry submissions filed.

## Success Measures

- The grounded agent cites the correct decision ID in at least 8 of 10
  scripted runs.
- A viewer with no RAC context can state what the product does after one
  viewing of the recording.
- Registry listings are live within one week of release.
- A stranger reproduces the grounded behaviour from `demo.md` alone.

## Risks

- Agent behaviour is stochastic and the demo may fail when others run it.
  Mitigated by the measured 8-of-10 gate, scripted prompts, and shipping
  the recording rather than relying on live runs.
- The scenario reads as contrived. Mitigated by the true-to-life bar and
  preferring a decision lifted from RAC's own corpus.
- Client model updates change tool-calling behaviour after release.
  Mitigated by keeping the measurement re-runnable as a regression check.

## Assumptions

- Claude Code remains the strongest MCP tool-calling client at release
  time.
- The with/without contrast fits the 90-second budget.

## Related Decisions

- ADR-030
- ADR-034

## Related Designs

- guide-grounding-demo
- guide-tool-surface

## Related Requirements

- rac-agent-context-guide

## Dependencies

- v0.10.0 server and tool surface
- v0.10.1 examples corpus and verified client configuration
