Map what must be byte-identical

The cache matches prefixes; know exactly what is in yours.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule

Write out the full request structure your provider sees, in order: system prompt, tool definitions, conversation messages, and (last) the new content. Everything before the first differing byte is cacheable prefix - so the design goal is pushing all per-child variation to the very end. Inventory your current dispatch path for prefix pollution: timestamps or run ids in the system prompt, tool arrays rebuilt per child (set iteration order!), serialization that does not guarantee key order, permission-dependent tool filtering that differs per child, and configuration fields (thinking settings, verbosity) that default differently for children than the parent. Each finding is a work item for the next step. Also confirm your provider's cache granularity and minimum-prefix rules so you aim at real boundaries.

Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

A request-structure map with every source of prefix variation identified.

Should NOT happen

An existing feature broke
A button only logs to console
Data disappears after refresh
Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Your notes for this step

Track what changed, failed, or needs follow-up. Notes export with the flow.

Pass the Verify Gate to complete this step

Verify before continuing

Do not move on until every check is true. The complete button stays locked until then.

Request field order documentedAll per-child variations found and listedProvider cache rules confirmed

Do not continue if…

! Per-child placeholder text ('processing task 1 of 3') breaking prefix identity
! Re-running tool filtering for each child, changing array order and killing the cache
! Injecting the child directive before the shared history instead of after
! Assuming savings without measuring - one serialization change and you pay full price silently

If the AI messes this up

Use this when:

- it only made visual forms or placeholder UI
- buttons do nothing or only log to console
- data is not persisted - state disappears on refresh
- something that worked before is now broken

Use this when the AI fakes progress or breaks the feature. It forces a real fix.

You cannot find the variation but caches still miss. Capture two sibling requests raw (exact bytes on the wire) and binary-diff them - the culprit is usually invisible in logs: whitespace, field ordering, or a library re-serializing floats differently.