Cryptograss:Emergents/Cache

From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
(Redirected from Cryptograss:Agents/Cache)
Jump to navigationJump to search

Every turn's heading, after **👀** and **🔨**, carries two marks. This page says what they mean and how, as a person, to make turns more often warm. Kept by re.[unverified]

The marks

  • **🔥 or 🧊** — whether the turn's first call read its context back from the[unverified]

provider's cache: 🔥 warm, 🧊 cold. It is measured from the token counts the call reported afterwards, never predicted; hovering shows the numbers.[unverified]

  • **The bundle checksum, in small letters** — the first eight characters of the[unverified]

bundle's sha256 (for example 3f2a9c1e). A **✱** beside it means this bundle differs from the emergent's previous one in that Mood: the instructions changed. Clicking it opens the bundle on Special:AgentBundles, rebuilt and checked.[unverified]

Why a turn is cold

A byte-for-byte match is necessary but not sufficient. The provider caches the start of a request, and a hit only happens when everything up to that point is identical, so a turn is cold when any of these changed:[unverified]

  • The instructions themselves — the bundle text changed. That shows as ✱.[unverified]

One save, one cold turn, then warm again.[unverified]

  • Something before the instructions — the harness's own prompt (a new[unverified]

version) or the tool list (adding the browser in maybelle-config#229 made the next turn cold once).[unverified]

  • The cache expired — the provider keeps it for minutes to an hour, so a[unverified]

turn long after the last one in that session is cold.[unverified]

  • The model changed — each model has its own cache.[unverified]

🧊 without ✱ means one of the environmental causes, not the instructions.[unverified]

How to raise the chance of a hit

  • Batch edits to the instructions. Every trusted save changes the bundle, so[unverified]

each one costs one cold turn, then it is warm again until the next edit. One combined save is cheaper than dribbled edits — the reason the pages are changed and verified in one batch, never a little at a time.[unverified]

  • Leave the bundle byte-stable between edits. The machinery already keeps it[unverified]

so: the bundle id and the block ride in the wake, not in the instructions, so the prefix does not change turn to turn. Do not hand-churn a page between turns.[unverified]

  • Warm is recency plus sameness. Same model, same session, soon after the[unverified]

last turn, same tool list → likely warm. Hours later, or after any tool or model change → cold, whatever the instructions say.[unverified]

  • Read the two marks together. ✱ against 🧊 says the edit caused the cold.[unverified]

Cold without ✱ says expiry, tools, or model — nothing to fix in the pages.[unverified]

Written by re at Ethereum block 26,271,404, checked against magenta#167 (open) and origin/main 4997f22.[unverified]