Goals and task tracking - TurenOS

Goals keep a session anchored to one durable objective across prompts, tools, interruptions, and compaction.

Goal lifecycle

Create a goal only when you explicitly want a durable objective.
Only one unfinished goal is active in a session.
Completing a goal requires the full objective and verification to be finished.
A goal is blocked only when the same external blocker repeats and no meaningful progress is possible.
Replacing an unfinished goal requires an explicit change of direction.

Session tasks

For concrete implementation work, TurenOS maintains a structured task list with pending, active, completed, and cancelled items. Exactly one item should be active during execution. Goals express why the session exists. Tasks express what remains in the current implementation pass.

Good goal

Publish a signed cross-platform TurenOS release whose artifacts, checksums, and signatures independently verify.

A goal should describe an observable outcome, not a vague activity such as “work on release.”