Repository navigation
TFW 3.10.1 — Continuous GOAL
Continuous Full GOAL
Start with the usual /tfw-plan and explicitly choose GOAL. The Coordinator keeps the substantive
planning conversation and approved HL, then the main agent executes and corrects the result itself.
Research and fresh independent review use separate contexts; no extra implementation agents or TS
are introduced.
- New contracts propose 100 substantive execution steps and at most 10 between completed
reviews, with earlier checks when needed and a full final review. Explicit owner limits govern. - Steps, review launches/returns, compact recovery and pending work have distinct identities.
REVISE preserves the main Executor; an older APPROVE cannot close a task with a pending review. - Economics preserves measured sources, activities, overlap handling and coverage. Historical
attempt contracts and the other three Full modes retain their meaning.
Daily and Claude coordination
- The optional Daily skill uses a shorter focused economics reference. Capture occurs at returned
deliverables or material revisions, planned pause/handover and close; explanation/status replies
need no separate snapshot. API-equivalent valuation remains the default unless explicitly changed. - The Claude Coordinator profile documents bounded visible-session recipes while preserving
command-only activation, actual address/settings checks and the dated evidence limits.
Upgrade and verification
Follow the 3.10.1 migration guide,
including its ordered route from earlier supported versions. Preserve existing tasks, approved
limits, numeric receipts, project customizations and selected adapters. Installation does not
select GOAL or authorize a run.
The integrated release passed the existing 14 tests, documentation build, 26 installed/source
comparisons and the full-history Git blob guard. The GCONT run was live in Codex; Claude Code and
Antigravity checks cover instructions and supported synthetic formats, not live end-to-end GCONT
runs. The local HTML browser preview and temporary-file cleanup limits remain disclosed in the
accepted task records. No comparative savings are claimed.