Private reference
The current working policy for planning and delivery.
Sources: DEVELOPMENT_DELIVERY.md · Last refreshed:
This view is a generated guide to the active delivery policy. The policy document remains controlling for implementation, review, repair, and closure.
SC-009/baseline 0.8 makes the bounded rule-engine path the current priority. Pause additional gameplay breadth while preserving its scope and gates. Reuse retained register/context/action/storage/delivery owners; do not restart the architecture. RULEENGINEPACKAGE.md owns the bounded…
Brian approved these adjustments after a quick review of repeated Group 2 discovery/repair cycles. Apply them within the existing acceptance contract; they change review execution, not scope, required evidence or gate strength. 1. Review underway: identify the bounded package, complete…
Brian clarified that Astra High is consuming too many plan credits: he values it but wants its use minimized. This supersedes keeping long Astra work stretches merely to avoid switches. Preserve every required review and acceptance case. Original world/items routing (2026-09-21;…
Brian approved Astra High requirements/implementation preparation, Sol High build and ordinary repairs, then Astra High implementation review, with effectiveness evaluated during existing package reviews. Optimize total effort and credit cost through acceptance, including preparation,…
Brian requested that the proposed comparison be carried into planned packages and handoffs. First use Astra High preparation -> Sol High implementation -> Astra High review on the next complex package to establish evidence for the improved blueprint. Then trial Terra High on the next…
Apply the methodology review's four execution recommendations through existing acceptance records: exercise the connected one/six-human setup-to-consumer path early; inspect the same invariant across affected preparation/commit/replay/recovery entry points; reuse the working…
Brian approved the GPT-6 run review proposals with "implement proposals". Apply these refinements to the current WI14 repair and subsequent applicable packages; the run review retains the timing, defects and limits behind this decision. - Executable example first: for a shared…
1. Observe at existing checkpoints. Use the package's existing review/closure record, or its repeated-defect reassessment. Record the costly recurring symptom and evidence: escaped contract, repair batches, repeated runs, harness errors, collected versus distinct tests, and available…