Guide System

Guides in the store

One guide per app, enforced by the address — app_guides/<package>.md is the only place a guide for that app can go. The bar is length against the 2,000-character cap.

What the gates refused

Every refusal is attributed to the gate that fired. A proposal refused here cost a model call and changed nothing — the trade for not putting a filter in front of the brain that also turns away the evidence worth reading.

Every app-turn

One row per app per window, including the turns that wrote nothing — those cannot appear in the guide store, because there is no guide to store.

App guides in Production

Impact in production

None of these guides is served by production yet. The guide-promote job syncs the store into the shadow database and, when run with --commit, upserts new or changed guides into agents.app_guides — until one lands, no change in an app’s failure rate can be attributed to it, which makes the answer not attributable rather than no effect.

Checked 2026-09-14T05:33:47Z · guide-promote job, live agents.app_guides · promote-20260914-053347 · dry run, production not written. Nothing here is randomised: an app whose guide was rewritten because it was failing drifts back toward its own average whether or not the edit helped. A separable interval is grounds for measuring properly on handsets, not the measurement.

Failures

Which guide was in play when an episode failed — not which guide was at fault. Nothing in this pipeline attributes cause; the loop forwards a failure because a guide was there, not because it was blamed.

Supported Apps

One guide per app. Version counts how many times that app’s guide has been written; the comparison shows the guide it replaced, recompiled from the knowledge it was rendered from.