Chief v2

Chief v2 is a set of additions that make Chief cheaper to run and easier to check. It is off until you turn it on, and one switch turns on all of it.

What it adds

• Records. Every task gets a record: where it went, which model, how many tokens, and how it ended.
• Task packs and lean workers. Chief hands a new session a short pack of eight fixed sections (goal, which files it may change, what to read, where to look, rules, how to check the work, how to ship, what to report). It stays under 80 lines, with your project's short mission, tech and roadmap notes in front. The session starts in safe mode, so it loads far less at startup.
• Secrets fenced. Workers get deny rules for .env files, keys and credential files, and Chief refuses a pack that names one.
• Routing by rule. Where a task goes and which model does it follow fixed rules. See Chief routing.
• Project map. melta-chief map writes one line per folder of a project, so a pack can point to the right place.
• Self-reset and the weekly review. Chief keeps a short ledger and clears its own chat when it grows big. Each Monday it proposes rule changes for you to approve. See Records and the weekly review.

Turn it on

Set CHIEF_V2=1 on the computer, where Chief and melta-chief start. Adding export CHIEF_V2=1 to your shell profile is the easy way. Then start Chief again. The phone never sets it. Without it, Routing on the host screen says that model routing is part of Chief v2.

Common questions

Is it on by default?

No. Chief works as before until you set the switch.

Does it change sessions that are already running?

No. Packs, lean starts and models apply to sessions Chief starts after you turn it on.

What if I turn it off again?

Remove the line and start Chief again. Chief goes back to its first behaviour; its records stay in its folder.

Where do packs and records live?

In Chief's own folder on your computer. Nothing goes anywhere else.