diff --git a/docs/agents/PROGRAM.md.kit b/docs/agents/PROGRAM.md.kit deleted file mode 100644 index c6835dfa..00000000 --- a/docs/agents/PROGRAM.md.kit +++ /dev/null @@ -1,32 +0,0 @@ -# Program — the owner's priorities and rulings - -Kept by the session manager. Short on purpose: the backlog holds the tasks, RESUME-BRIEF.md -what is mid-flight. Every ruling is DATED and QUOTES the owner; session-manager calls are -marked vetoable. - -Last updated: YYYY-MM-DD - -## Current milestone - -TODO: one paragraph. - -## Priorities (owner's order) - -1. TODO -2. TODO - -## Rulings log (newest first) - - - -## Standing rules - -- Approvals for spend, publishing and deploys are typed by the owner in the session that acts. -- Agreed work is never silently dropped: a priority change defers it; only the owner cancels, with a reason. diff --git a/docs/agents/RESUME-BRIEF.md.kit b/docs/agents/RESUME-BRIEF.md.kit deleted file mode 100644 index 63dd8f7c..00000000 --- a/docs/agents/RESUME-BRIEF.md.kit +++ /dev/null @@ -1,23 +0,0 @@ -# RESUME BRIEF — written YYYY-MM-DD HH:MM () - -Written by the dispatcher at every wind-down; read first by every session at restart. - -## First reads on restart - -1. `git log --oneline
-20` — what landed while the fleet was dark. -2. Remove `/PAUSED` (the restart job does this). -3. TODO: anything scheduled to run while dark, and where its output is. - -## Mid-flight (per area) - -| area | item | state | SHA / branch | next step | -| --- | --- | --- | --- | --- | -| TODO | | | | | - -## Waiting on the owner - -- TODO - -## Held (do not land until) - -- TODO diff --git a/docs/agents/STRIKES.md.kit b/docs/agents/STRIKES.md.kit deleted file mode 100644 index 24b2da23..00000000 --- a/docs/agents/STRIKES.md.kit +++ /dev/null @@ -1,12 +0,0 @@ -# Model tier strikes - -Evidence loop for per-area model tiers. A strike is one of: red landing, withdrawn -submission, reviewer rejection, peer-caught false green, owner-reported regression. - -- Two strikes in a week (week = from the usage reset) -> propose moving the area UP a tier. -- Two clean weeks -> offer moving it DOWN a tier. -- Loses the thread after compaction -> raise its context. -Changes go into fleet.config.json (area `tier` / `context`) and need a fresh start of that area. - -| date | area | tier | strike | evidence (SHA, check, who caught it) | -|---|---|---|---|---| diff --git a/fleet/RULE-CHANGES.md.kit b/fleet/RULE-CHANGES.md.kit deleted file mode 100644 index 0bd4dad0..00000000 --- a/fleet/RULE-CHANGES.md.kit +++ /dev/null @@ -1,8 +0,0 @@ -# Rule changes - -Newest first. One `## YYYY-MM-DD` heading per day, then a line per change. -Read this file newest first now and before every backlog item. These lines -override a stale system prompt. Nothing filters them down to a window of days. - -The session manager adds a line here whenever a rule, a prompt, a tool's usage, or -a landing rule changes.