# A saved rule changes a project digest

Recorded October 7, 2026 by Nora, Socra Marketing. Cedar and every completed-work entry are fictional. The Cortex retrieval and local generation were actually executed. Nora played both rule owner and consuming agent in the same conversation. The updated rule was retrieved in a separate later task; this is not an independent fresh-agent evaluation.

## What the recording supports

Version 1 asks for completed work grouped by project, with each entry naming the work and result. Nora explicitly retrieved that Module, then selected project grouping in the generation code. The resulting digest contains Website and Operations.

The fixture owner added a client-report rule in Version 2: include public projects and exclude internal work. In a separate later task, Nora explicitly retrieved the updated Module, then selected public entries before grouping. The saved client digest contains the same two Website entries and omits Operations.

This supports instruction retrieval and application within this recorded example. It does not establish automatic propagation, customer benefit, adoption, installation success or first-time reader comprehension. The Flash records show 43 and 82 tokens for these two small examples; they do not predict another task's context size or cost.

## Exact recorded artifacts

- [Fictional completed-work entries](fixture.json)
- [First saved rule](rule-v1.md) and [updated saved rule](rule-v2.md)
- [First Flash](flash-v1.txt) and [updated Flash](flash-v2.txt)
- [First generation code](digest-v1.mjs) and [later generation code](digest-v2.mjs)
- [Project digest](digest-v1.md) and [client digest](digest-v2.md)
- [Saved version history](versions.txt)
- [SHA-256 artifact manifest](manifest.json)

The manifest binds each file to its recorded bytes. Compare the digest text shown on the page with the saved Markdown outputs. Compare each selected transformation in the code with the preceding Flash record. To reproduce local generation, download the fixture and each .mjs file into one directory and run them with a runtime supporting Map.groupBy, such as Bun. Each script writes its corresponding digest beside itself. This replays local generation only; it does not replay the private Cortex recording or establish independent agent behavior.

## Try the supported path

[Set up the CLI](/integrations/cli) or choose another [supported integration](/integrations). Follow the actual setup instructions and verify a Cortex call from your agent. For a bounded task that needs an existing project decision, explicitly flash its Module before acting, then check the work against that decision. Reaching setup does not verify connection or installation.