docs: vision-alignment check for task creation#52
Conversation
Add vision_section frontmatter field and alignment rule to task creation process. Before creating tasks, agents must check the last 5 tasks -- if 3+ target the same vision section, new tasks must prioritize a different section. Updated GUIDE.md, evolve.md Step 6n, and report templates. Moves Meta-Prompt priority engine 50% -> 60%. Also includes prior session housekeeping: handoff compaction (0022-0030 -> weekly), task archival (done tasks -> archive/). Task #31
Reviewer noted the GUIDE.md rule allows overriding alignment for urgent work, but the evolve.md Step 6n constraint was absolute. Add the same exception clause for consistency.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f2a6315d20
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| The task queue can drift — all tasks end up targeting the same vision section while other sections stagnate. Before creating new tasks, check alignment: | ||
|
|
||
| 1. Read the last 5 tasks created (by number, regardless of status) |
There was a problem hiding this comment.
The new rule says to check the “last 5 tasks created (by number, regardless of status),” but completed tasks are moved out of docs/tasks/ into docs/tasks/archive/ between sessions, so this instruction is underspecified and will often count the wrong files if someone scans only the active directory. In practice, that can mis-detect clustering and cause the alignment guard to be skipped or triggered incorrectly; the rule should explicitly say to compute the last five across both active and archived task files (or via .next-id lookback).
Useful? React with 👍 / 👎.
1 participant
Summary
vision_sectionfrontmatter field to task files (loop1,loop2,self-maintaining,meta-prompt,none)docs/tasks/GUIDE.md: before creating tasks, check last 5 — if 3+ target the same section, new tasks must prioritize a different sectionTask #31
Test plan
make checkpasses (663 tests, all green)vision_sectionfield when generating tasks