Drift is caught, not discovered
The record is checked on a schedule rather than when somebody happens to notice a color has changed.
Context Management
The shared context and your first team, kept correct month by month.
Re-runweeklyDrift foundpersistent onlyProposedthrough a gateLiveapproved by you
Claims
claims/pricing.mdre-rundrift foundproposedlivepositioning.mdre-rundrift foundproposedliveclaims/security.mdre-rundrift foundproposedliveclaims/tone.mdre-rundrift foundproposedlive
Evals
eval/refusalsre-rundrift foundproposedliveeval/claims-50re-rundrift foundproposedliveeval/escalationre-rundrift foundproposedliveeval/pricing-qre-rundrift foundproposedlive
Reads from it
tokens/color.jsonre-rundrift foundproposedliveemail/launch.htmlre-rundrift foundproposedlivebanner-728x90re-rundrift foundproposedlivevoice/lexicon.mdre-rundrift foundproposedlive
Findings per week12 weeks · transcripts archivedThrough the gate9 approved3 with you12 proposed · none applied without youEval regression50 scenarios · re-run on every changeAgents running3 current1 updatingmonthly report · what changed, what is stale
How it runs
Context Management, step by step.
On a schedule, against the record itself, without anybody remembering to start it.
- Today, 06:002 changes proposed
- Mon, 06:001 change proposed
- Last Mon, 06:00Nothing changed
- 2 weeks ago4 changes proposed
What changes
afterwards
Nothing goes stale quietly
A claim whose source went away arrives as a change to approve, while it still matters.
You can see it working
The same questions re-scored every quarter, by the outside — the one measure here that is not us marking our own work.
One page a month
What was made, what changed, what is stale. Nothing you have to remember to open.