Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .recursive/operators/build/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,8 @@ The task queue is authoritative. The handoff's "Next Session Should" is advisory

**Value scoring:** When choosing between tasks of equal priority, prefer the one that moves the vision tracker forward. A session that advances the tracker from 63% to 66% is more valuable than one that completes three cleanup tasks.

**Vision-alignment tiebreaker:** When two or more tasks have equal priority AND equal expected tracker impact, prefer the task whose `vision_section` field targets the lowest-percentage section in `.recursive/vision-tracker/TRACKER.md`. Check tracker percentages at the start of Step 1 (Situational Awareness). This is advisory -- use judgment. If the lower-percentage section has no tasks ready to ship, pick the best available task and note the alignment gap in the handoff under "Vision alignment".

## Process

### Step 0 — Verify Previous Commitment + Evaluate
Expand Down
4 changes: 2 additions & 2 deletions .recursive/tasks/0072.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
---
status: pending
status: done
priority: normal
target: v0.0.8
vision_section: meta-prompt
created: 2026-04-05
completed:
completed: 2026-04-08
---

# Vision-alignment awareness in task selection
Expand Down
15 changes: 15 additions & 0 deletions .recursive/tasks/GUIDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -97,6 +97,21 @@ The task queue can drift — all tasks end up targeting the same vision section

**Exception:** If a section genuinely has urgent work (bugs, blockers), alignment can be overridden — but you must explain why in the task description.

## Vision-alignment tiebreaker in task selection

The vision-alignment rule above governs task *creation*. This rule governs task *selection*.

When two or more tasks have equal priority AND equal expected tracker impact, prefer the task whose `vision_section` field targets the lowest-percentage section in `.recursive/vision-tracker/TRACKER.md`.

**How to apply it:**
1. At the start of Step 1 (Situational Awareness), note the current section percentages from `TRACKER.md`
2. When choosing between tied tasks, check their `vision_section` fields
3. Prefer the task targeting the section with the lowest percentage

**This rule is advisory.** Use judgment -- do not apply it mechanically. If the lower-percentage section has no tasks ready to ship (all blocked, integration-only, or missing), pick the best available task and note the alignment gap in the handoff under "Vision alignment".

**Example:** The tracker shows Self-Maintaining at 68% and Meta-Prompt at 79%. Two normal-priority tasks are tied: task #0080 (`vision_section: self-maintaining`) and task #0081 (`vision_section: meta-prompt`). Both have the same queue impact. Pick #0080 -- it targets the lower-percentage section. If #0080 is blocked, pick #0081 and write "Vision alignment: Self-Maintaining (68%) is starved; no ready tasks available this session" in the handoff.

## When the agent finishes a task

The agent does THREE things:
Expand Down
File renamed without changes.
Loading