meltaRecords and the weekly review
Chief v2 keeps track of its own work so you can check it, and it improves its rules only with your yes.
Records
Every task gets one record: the task, where it went, the model, the tokens and how it ended. The outcome is landed, needs you, reverted or unknown. melta-chief records lists them.
STATE.md and the reset
Chief keeps a short ledger, STATE.md, with four parts: open tasks, what is waiting on you, decisions today, and the last 20 records. When Chief's own chat reaches 90K tokens, or 60% of its window, or a new day starts, it writes the ledger and clears its chat. The fresh chat reads STATE.md and goes on. Nothing in the ledger is lost.
melta-chief staterewrites the ledger now.melta-chief note "text"adds a line to decisions today.melta-chief reset-selfwrites the ledger and clears Chief's chat now.
The Monday review
On Monday Chief says the weekly review is due. It shows the week's numbers, then proposes changes to its rules, its pack template, your project notes or its settings. Each change comes with a reason and a number it should improve.
Approving a change
Chief asks yes or no for each change, one at a time, never as a batch. Each yes applies that one change and keeps the old file as a backup. Chief never edits its own rules any other way.
Rollback
Every applied change has an id, and Chief keeps a list of them. melta-chief rollback <changeId> puts the old file back.
Common questions
Does Chief change its rules on its own?
No. Every change needs your yes.
What if I say no?
Nothing changes. The next review can propose it again.
Can I run the review on another day?
Yes: melta-chief review, or ask Chief.
Does it fine-tune a model?
No. Your records and your yes are the whole loop.