Private reference
Approved direction, pauses, and limits extracted from the scope-change log.
Sources: SCOPE_CHANGE_LOG.md · Last refreshed:
- Status: Approved and Applied to the package/register, 2026-09-23; implementation and its bounded acceptance cases are complete. C38 remains open. - Approval evidence: Brian: “ok, do so,” after the proposed custom /bug command that privately acknowledges a concise report and writes it to…
- Brian's direction: "ok, we should do another review after batch 4 and it should happen prior to handoff". - Applied: the existing world/items report's Batch 4 handoff requirements require a final process/efficiency comparison after independent Batch 4 acceptance, saved in that report…
- Recommendation acceptance: in the Batch 4 successor, after the final evaluation was presented, Brian said: "I accept reccomendation, have you updated the plan where needed". Applied to the standing delivery policy, master register, rule-engine handoff and existing world/items report.…
- Brian's direction: “instead of moving active work chats to past work, I want them to archive. make this automatic in dev policy”. - Applied: future completed Active Work package tasks are archived in Codex after their finish line, evidence, disposition and final handoff are recorded.…
- Status: Applied to delivery policy, 2026-09-22; capability baseline 0.8, scope and acceptance gates unchanged. No batch has been executed by this update. - Approval: Brian: "ok, this is a good plan", in response to the concrete two-block trial, single-block exceptions, approximate…
Planning follow-through, 2026-09-22: Brian agreed to the goal-linked high-level route and the next step of mapping representative scenarios and selecting the first useful proof. The existing architecture map now contains seven connected scenario groups covering retained P/S/D/A…
- Status: Applied to planning, 2026-09-22; baseline 0.8. Implementation pending. - Approval: in "Streamline rules implementation", Brian: "anything else we need to discuss, I approve this new direction and would like you to set it up for development". This follows explicit agreement to…
- Status: Applied; explicit user direction, 2026-09-21. - Approval evidence: Brian: “I would classify grinding as a must have for the 1.0 release not the pilot release ... handled through the existing architecture.” - Before: GAP placed montage/grinding aids in nice-to-have…