@hassangameryt/freeflow 0.3.0 → 0.4.0

package/skills/tdd/SKILL.md

@@ -0,0 +1,96 @@
+---
+name: tdd
+description: Use when implementing or changing behavior test-first, fixing a bug with regression evidence, protecting behavior during refactoring, or when a test is difficult to write or starts shaping production design.
+---
+
+# Test-Driven Development
+
+Use one observed failing behavior check to guide the smallest complete implementation for one accepted behavior.
+
+TDD is an execution method inside [Execute Work](../execute-work/SKILL.md). One vertical RED/GREEN/REFACTOR loop is a bounded action, not automatically a Track Work slice. Several accepted behavior loops may remain inside one coherent current slice.
+
+TDD does not define intended behavior. The accepted request, source truth, and user decisions establish what should happen.
+
+## Follow The Behavior Loop
+
+```text
+[Accepted behavior with settled expectation]
+-> [Choose stable seam and independent oracle]
+-> [RED: write and run the smallest behavior check]
+   -> fails for expected missing behavior -> GREEN
+   -> passes immediately -> inspect test, boundary, or existing behavior
+   -> errors for unrelated reason -> correct harness or diagnose
+-> [GREEN: smallest complete implementation]
+-> [Verify focused behavior]
+-> [REFACTOR when useful, without behavior change]
+-> [Verify original path and affected boundary]
+-> [Route]
+   -> another accepted behavior in this slice -> next TDD loop
+   -> coherent extension -> approve and record when needed
+   -> unclear cause or structural pressure -> Workflow
+   -> supported bounded action -> return to Execute Work
+```
+
+Do not write all tests first and all implementation later. Finish, verify, and route one accepted behavior before starting another.
+
+## Use Or Exit Deliberately
+
+Use TDD for accepted behavior changes, bug fixes with a supported cause, consequential logic, and refactors whose behavior needs protection.
+
+Do not force test-first work onto documentation, static content, mechanical formatting, generated output, or a disposable learning prototype whose result is not selected production behavior.
+
+Stop before RED when expected behavior, failure semantics, or a public contract is unsettled. Return the missing direction to [Workflow](../workflow/SKILL.md) rather than encoding a guess as a test.
+
+## Choose The Seam And Oracle
+
+Test observable behavior through the highest stable interface that exercises the real requirement.
+
+A useful seam:
+
+- is used by callers rather than created only for tests;
+- survives internal refactoring;
+- reaches the real behavior or failure path;
+- keeps setup proportionate;
+- can disagree with the implementation.
+
+Derive expected results from source truth, a worked example, protocol contract, or independent calculation—not the implementation algorithm.
+
+Read [Test Design](references/test-design.md) when the test level, oracle, double, rejected state, composed failure, time or concurrency boundary, or legacy seam is unclear.
+
+If testing requires owned internals, duplicated caller choreography, or production hooks used only by tests, return the evidence to Workflow. Use [Design for Depth](../design-for-depth/SKILL.md) only when it establishes design-bearing interface or ownership pressure; do not redesign merely because one test is inconvenient.
+
+## Enforce The Test-First Evidence
+
+- Observe RED failing for the intended missing behavior before changing production code.
+- If RED passes immediately, inspect the test, observing boundary, and existing behavior; do not proceed to GREEN automatically.
+- If RED fails because of syntax, setup, environment, or unrelated behavior, correct the harness or diagnose before implementation.
+- Implement the smallest complete GREEN behavior. Read [Code Practices](../execute-work/references/code-practices.md) while changing code.
+- Refactor only when it improves the result while the focused behavior check remains green.
+- Re-run the original path and smallest affected boundary before returning the supported action and evidence to Execute Work.
+- Do not claim TDD when the check was written after implementation or RED was never observed for the intended reason.
+
+## Keep Tests About Accepted Behavior
+
+Prefer observable outcomes over internal call sequences, real implementations before doubles, independent expected values, descriptive domain names, and one behavior concept per test.
+
+Use fakes, stubs, mocks, or spies only at a boundary where replacement is necessary and the double preserves the fields, effects, invariants, and failure behavior the test needs.
+
+Do not copy the implementation into the expected value, add production methods used only by tests, change a valid test merely to make implementation pass, or treat coverage and test count as proof.
+
+Add an edge-case check only when accepted behavior, observed failure, material safety, or a settled failure contract requires it. If behavior is undefined, return it to Workflow. When related cases keep adding states, flags, setup, or patches, stop the behavior-loop stream and diagnose the shared contract, cause, ownership, or interface.
+
+## Fix Bugs Through The Reported Boundary
+
+First reproduce the reported symptom through the correct seam. A nearby failing path is not the bug.
+
+If no reliable diagnostic loop or supported cause exists, use [Diagnose Failure](../diagnose-failure/SKILL.md) before selecting a production correction. After RED and GREEN, rerun both the minimized regression check and the original unminimized symptom or strongest available observer.
+
+## Stop When Tests Start Designing The System
+
+Return evidence to Workflow when test setup grows faster than behavior coverage, each case requires another public state or fallback, tests protect machinery introduced by earlier patches, the next check requires an unplanned subsystem, or making it pass expands accepted scope.
+
+A green local loop does not prove the global design is right. Diagnose repeated or unexplained failure before redesigning.
+
+## Report
+
+Report the accepted behavior and seam, observed RED result, GREEN implementation, refactor if any, original-path and broader verification, current slice effect, and remaining unverified behavior. Return route-changing evidence rather than silently beginning another behavior or slice.

package/skills/tdd/references/test-design.md

@@ -0,0 +1,96 @@
+# Test Design
+
+Read this when the right test level is unclear, a dependency needs a double, legacy behavior lacks a seam, or test setup starts driving production design.
+
+The goal is confidence in accepted behavior, not maximal isolation or a fixed unit/integration/end-to-end ratio. One TDD behavior loop is a bounded action and may remain inside a larger coherent Track Work slice.
+
+## Choose The Confidence Boundary
+
+Start from the highest stable interface used by callers, then choose the smallest test environment that still exercises its real behavior and failure path:
+
+- **Focused behavior test:** deterministic logic or one stable public operation can prove the requirement.
+- **Integration test:** correctness depends on collaborating components, persistence, serialization, process boundaries, or a real adapter contract.
+- **End-to-end or user-path check:** the requirement is a critical flow whose value depends on the assembled system.
+- **Characterization test:** existing behavior must be observed and protected before a behavior-preserving refactor.
+
+A characterization test records current behavior; it does not make that behavior desired or authoritative. Stop when intended behavior conflicts with source truth or remains user-owned.
+
+A smaller environment is not better when it mocks away the behavior being claimed. A larger environment is not better when its extra machinery adds noise without proving more.
+
+## Build An Independent Oracle
+
+Expected results should come from source truth, a worked example, a protocol contract, or an independently calculated value.
+
+Do not compute the expected value with the same algorithm as the implementation. That produces agreement by construction.
+
+Prefer observable state, outputs, errors, persisted effects, and caller-visible behavior. Assert an interaction only when that interaction is itself part of the accepted contract or the real effect cannot be observed safely at this test boundary.
+
+Keep one behavior concept per test. Multiple assertions are fine when they jointly describe one outcome.
+
+## Rejection And Composed Failures
+
+For authority, persistence, canonical evidence, retry, cancellation, or recovery behavior, identify the dimensions that materially change the outcome:
+
+```text
+entry point
+× valid or invalid input
+× empty or existing accepted state
+× pre-commit or post-commit failure
+× first call or retry/replay
+```
+
+Do not expand this into an exhaustive matrix by habit. Select the smallest rows that can disprove the accepted failure contract. For each selected row, assert:
+
+- returned result;
+- allowed writes or effects;
+- forbidden writes or effects;
+- preservation of prior accepted state;
+- required diagnostic or recovery evidence.
+
+When two accepted conditions can coincide, test the composition rather than assuming isolated cases commute. Examples include cancellation plus integrity failure, successful commit plus failed reconciliation, invalid replacement plus existing valid state, or bounded recovery plus continuation redemption.
+
+## Choose A Test Double
+
+Preference order:
+
+1. **Real implementation:** use when deterministic, fast enough, safe, and controllable.
+2. **Fake:** a lightweight working implementation that preserves the relevant contract.
+3. **Stub:** returns fixed data needed to reach the behavior under test.
+4. **Mock or spy:** records interactions; use sparingly when the interaction itself matters.
+
+Before replacing a dependency, identify:
+
+- the behavior and side effects it owns;
+- which of those effects the test depends on;
+- the boundary being isolated;
+- how the double stays faithful to the real contract and failure modes.
+
+Mock the slow, external, destructive, privileged, or nondeterministic boundary—not a higher-level operation whose behavior the test needs.
+
+Useful double boundaries often include external APIs, email or payment delivery, uncontrollable clocks or randomness, destructive infrastructure, and unavailable remote services. Databases and filesystems may be cheaper and more trustworthy to use for real than to imitate.
+
+A fake or stub must preserve the fields, invariants, errors, and side effects relevant downstream. Validate it against a schema, recorded contract, or shared contract tests when drift would create false confidence.
+
+Do not add public production methods, flags, branches, or lifecycle operations used only by tests. Keep cleanup and fixture construction in test utilities unless production genuinely owns that behavior.
+
+## Time, Randomness, And Concurrency
+
+Prefer an existing controllable boundary for clocks, randomness, scheduling, and external events. Do not expose new public test hooks merely to make assertions convenient.
+
+Avoid arbitrary sleeps as proof. Use observable synchronization, deterministic inputs, bounded eventual assertions, or the real diagnostic loop.
+
+When a race or flaky path cannot be made deterministic, use [Diagnose Failure](../../diagnose-failure/SKILL.md) to raise the reproduction rate and gather evidence before changing production behavior.
+
+## Pressure Signals
+
+Question the seam before adding more test machinery when:
+
+- mock setup is longer or more conditional than the behavior;
+- removing a mock changes what the test is actually proving;
+- many owned internals must be exposed or replaced;
+- doubles duplicate production orchestration;
+- test-only production APIs appear;
+- integration repeatedly fails despite isolated tests passing;
+- fixtures must know internal states, ordering, or cleanup protocols callers should not coordinate.
+
+A real integration test may be simpler than a network of mocks. If the difficulty reflects caller choreography or a shallow interface, use [Design for Depth](../../design-for-depth/SKILL.md) rather than designing production around the test framework.

package/skills/track-work/SKILL.md

@@ -0,0 +1,84 @@
+---
+name: track-work
+description: Use when deciding whether proposed or ongoing work needs a durable Working Record, or when creating, resuming, or updating one to preserve task state across execution, pauses, or context loss.
+---
+
+# Track Work
+
+Decide whether proposed or ongoing work needs a durable Working Record, then maintain selected records without turning them into a transcript, fixed Plan, or authority over live evidence and user decisions. Deciding or reading an existing record is read-only; create or update one only when the effective mode permits mutation.
+
+Use this route to decide whether to wait, return to Workflow, or continue through [Execute Work](../execute-work/SKILL.md):
+
+```text
+[Proposed or ongoing work]
+-> existing Working Record owns it
+   -> read the required reference
+   -> maintain it
+   -> select an authorized slice and route to Execute Work, or wait
+-> no existing Working Record
+   -> would losing context, decisions, evidence, or the next action risk misalignment?
+      -> no
+         -> authorized work in a mutation-permitting mode -> Execute Work
+         -> otherwise -> Workflow or wait
+      -> yes, but a record is unapproved
+         -> recommend a Working Record
+         -> wait
+      -> yes, and a record is approved
+         -> mode permits durable mutation
+            -> read the required reference
+            -> create the record
+            -> first slice already requested or approved
+               -> select the slice
+               -> Execute Work
+            -> only record creation was approved
+               -> Current Slice: None
+               -> wait
+         -> mode does not permit durable mutation
+            -> recommend the required mode change
+            -> wait
+```
+
+## Read The Required Reference
+
+Before creating, resuming, or updating a Working Record, read the complete [Working Record method and schema](references/working-record-schema.md). This skill and its reference form one method. Do not invent fields, states, or transitions from memory; if the reference is unavailable, do not mutate the record.
+
+## Core Contract
+
+- A record preserves current context, one current slice, revisable proposals, durable history, inert Notes, and one next useful action. It is memory; live evidence and user decisions win.
+- `Current understanding` is a present-state summary, not a running task summary or compressed transcript. Replace superseded prose instead of appending completed events.
+- Give detailed facts one schema-owned home. Other sections summarize or point to that owner rather than repeating findings, hashes, commands, or test inventories.
+- Only the user changes task state. Do not infer `Paused`, `Completed`, `Abandoned`, or renewed `Active` state from inactivity, apparent completion, or failure.
+- A **slice** is one bounded piece of learning, delivery, or structural improvement. One slice may span multiple iterations of [Workflow's](../workflow/SKILL.md) Feedback Loop and calls to other owning skills.
+- Record state changes, not every edit or conversation. Apply authorized in-scope steering and reconcile its meaningful final effect when the slice closes.
+- Before work changes the recorded result, scope, authority, evidence boundary, or stop conditions, decide and record whether it extends the current slice or requires a new one.
+- Questions, criticism, and review findings do not authorize changes. Ordinary in-slice feedback is not a checkpoint or history event merely because work pauses for the user.
+- Workflow establishes slice outcomes. Implementation, verification, self-review, or a review report does not end a slice by itself, and review need not Pass.
+- The record may preserve authority sources, decisions, checkpoints, and evidence; it never creates authority or proof.
+
+## Follow The Lifecycle
+
+After reading the required reference:
+
+1. **Create or resume:** use the established task directory, restore task state after context loss, and orient from live evidence.
+2. **Select or wait:** select a slice only when its concrete work is requested or approved. If only record creation is approved, keep `Current Slice` as `None` and wait. When selected, move one proposal into `Current Slice`, assign its chronological `S-` ID, save the write-ahead state, then route to Execute Work.
+3. **Maintain the slice:** keep small steering out of the event history; record accepted extensions before execution; preserve blockers, review routes, and evidence without replacing a coherent slice.
+4. **Close the slice:** move the Workflow-established outcome to History, preserve the original boundary and accepted extensions, rewrite Current Context from the resulting present state, remove completed-event detail already owned by History, and set `Current Slice` to `None`.
+5. **Preserve what matters:** keep task-local decisions, selected checkpoints, evidence pointers, and Notes in their schema-owned sections.
+
+## Context Boundaries
+
+Before an expected compaction, summarization, pause, clear, or transfer, reconcile the record only when task state changed. The boundary itself is not a record event.
+
+After compaction, summarization, resume, clear, or session navigation, read the complete record before the next task action and compare it with the current conversation and live state. Identify the task from current context or inspect and ask rather than guessing. A record written on another conversation branch is memory, not authority.
+
+## Route Or Stop
+
+Use [Discuss](../discuss/SKILL.md) before selecting a slice when a collaborative question could materially change its result, scope, or route.
+
+Use `Blocked` only when a required decision, dependency, capability, evidence source, stop condition, or other unavailable condition prevents safe continuation. Keep the blocked slice current, record what is needed, then stop. General execution authority does not override a stop condition.
+
+When the user requests a separate point-in-time transfer artifact, read [Handoff](../handoff/SKILL.md). Creating a handoff does not replace living Working Record state.
+
+## Check The Record
+
+After every update, silently compare the record with live evidence and the required reference. Correct clear local issues. Remove historical narration from Current Context once its active consequence is captured, and replace duplicated detail with a compact pointer to its owner. Do not create review history or request review merely because the record changed.

package/skills/track-work/references/working-record-schema.md

@@ -0,0 +1,378 @@
+# Working Record Method And Schema
+
+This is the required companion to Track Work. Read it completely before creating, resuming, or updating a Working Record. It defines both the lifecycle method and the stored shape.
+
+Omit optional fields and sections when they contain no useful information. Preserve detail when forgetting it could misalign later work; compactness means removing repetition, transcripts, and raw output—not continuity.
+
+## Task Directory
+
+Use one stable directory per task:
+
+```text
+.freeflow/tasks/task-NNN-<short-name>/
+├── record.md
+├── specs/   # only when Write Spec creates a task-local artifact
+└── plans/   # only when Write Plan creates a task-local artifact
+```
+
+Use the next unused three-digit number and a short readable name. Track Work owns the directory and `record.md`. Write Spec and Write Plan own their artifact filenames, formats, and contents.
+
+## Record Order
+
+Keep these layers in order:
+
+1. **Current Context:** what is needed to understand the task.
+2. **Current Work:** route, current or blocked slice, blockers, checkpoints, and next action.
+3. **Proposed Slices:** ordered, revisable work that has not started.
+4. **History:** decisions, checkpoint results, and completed, parked, or abandoned slices.
+5. **Notes:** inert context with no active task effect.
+
+Read the complete record after context loss. The order establishes context before action; it does not make later sections disposable.
+
+## Record Template
+
+```markdown
+# Working Record: <task name>
+
+State: Active | Paused | Completed | Abandoned
+Last updated: <optional reliable date or time>
+
+## Current Context
+
+Goal:
+What defines this task:
+Current understanding:
+Current direction:
+Boundaries:
+
+### Active Decisions
+
+- D-001 — <one-line meaning>
+
+### Active Hypotheses
+
+### Open Questions
+
+## Current Work
+
+Current route:
+
+### Current Slice
+
+None
+
+Or:
+- ID: S-001
+- State: In progress | Blocked
+- Type: Learning | Delivery | Deepening
+- Intended result:
+- Authority source:
+- Reason and scope:
+- Expected evidence:
+- Stop condition:
+- Starting code or artifact state:
+- Accepted extensions, if any:
+- Selected checkpoints, if any:
+- Blocker, if blocked:
+- Resume when, if blocked:
+
+Blockers:
+Upcoming checkpoints:
+Next useful action:
+
+## Proposed Slices
+
+### <proposal title>
+
+Type:
+Intended result:
+Expected evidence:
+Dependencies:
+Selected checkpoints, if any:
+
+## History
+
+### Decisions
+
+#### D-001 — <decision title>
+
+State: Active | Superseded | Retired
+Decision:
+Who decided or what established it:
+Rationale and sources:
+Consequences:
+Revisit when:
+Supersedes:
+Superseded by:
+
+### Checkpoints
+
+#### <checkpoint title>
+
+Type: Independent review | Local commit | User decision | Continuity
+Selected by: <approved Plan or explicit discussion>
+Condition:
+Result: Completed | Deferred | Cancelled | Replaced
+Judgment or decision:
+Evidence or result pointer:
+Effect on the task:
+
+### Slices
+
+#### S-001 — <slice title>
+
+State: Completed | Blocked | Abandoned
+Type: Learning | Delivery | Deepening
+Intended result:
+Authority source:
+Accepted extensions and authority, if any:
+Work performed:
+Result:
+Effect on understanding, decisions, or hypotheses:
+Evidence:
+- Tests and other checks: <check, result, and source>
+- Verification: <claim, boundary, check result, claim result, proof limits, and source>
+- Independent review: <review number, judgment, items, adjudication, and source>
+Blocker and required resolution, if historically blocked:
+What happens next:
+
+## Notes
+
+### <note title>
+
+Source: <user request or useful agent observation>
+
+<retained context>
+```
+
+## Create Or Resume
+
+### Minimum Record
+
+A record may begin without decisions, proposals, history, Notes, or a current slice. Add fields only when the task produces information worth preserving. At minimum record:
+
+- task state;
+- goal or central question;
+- current understanding;
+- important open questions;
+- `Current Slice: None` when no slice is running;
+- one next useful action.
+
+If context is too thin, recommend discussion first. If the user still wants a record, write an honest minimal one without inventing intent or state.
+
+### Current Context
+
+- Keep only context that still affects interpretation or later action.
+- Treat `Current understanding` as a present-state summary, not a running task summary or compressed transcript. Rewrite it from what remains true instead of appending completed events.
+- Remove completed-slice narration, superseded failures and corrections, per-review findings, test inventories, hashes, and live-run detail once their active consequence is captured and History owns the evidence.
+- `Current direction` describes remaining strategy, not completed phases.
+- Summarize active decisions by ID; preserve rationale and lineage in History.
+- Update facts when live evidence changes. Moving obsolete context does not require deleting useful history.
+- Use no arbitrary size cap. Keep detail only when removing it could cause the next reader to choose the wrong route.
+
+### Task State
+
+Only the user changes task state:
+
+- `Active`: the task is ongoing.
+- `Paused`: intentionally paused.
+- `Completed`: considered complete.
+- `Abandoned`: intentionally ended without completion.
+
+Do not infer task state from time, inactivity, apparent completion, or failure. Before a user-directed task-state change, make Current Context, Current Work, important History, and the next action accurate; then apply exactly the chosen state. Use `Last updated` only when a reliable date or time is available.
+
+### Context Boundaries
+
+- **Before an expected compaction, summarization, pause, clear, or transfer:** reconcile the record only when task state changed. The boundary itself is not a record event.
+- **After compaction, summarization, resume, clear, or session navigation:** read the complete record before continuing task work and compare it with the current conversation and live state.
+- Identify the task from current context or inspect and ask rather than guessing. A record written on another conversation branch is memory, not authority. Correct clear factual or clerical mistakes, and ask before changing user intent, task lifecycle, or a recorded decision.
+
+## Select A Slice
+
+### Proposals
+
+Proposals remain revisable until selected:
+
+- use one unnumbered heading per proposal;
+- assign no `S-` ID, ordinal label, or state;
+- refer to a proposal by title, not “proposal 2”;
+- express ordering constraints under `Dependencies`;
+- preserve an external Plan phase or identifier only when one exists.
+
+When selected, remove the proposal, assign the next chronological `S-` ID, and write it as the one Current Slice before execution.
+
+### Authority And Write-Ahead State
+
+- Record the source that requested or approved the slice.
+- Approval may cover one slice or a named set; do not ask again while remembered authority clearly covers the work, and do not extend it to invented scope.
+- Approval cadence and reporting cadence are separate.
+- A decision approval, tentative proposal, nearby instruction, or permission to discuss does not authorize implementation unless the interaction clearly establishes that authority.
+- Record the slice fields shown in the template, save the record, then execute. This preserves intent; it does not claim execution occurred.
+- A stop condition overrides general authority. Mark the slice `Blocked` and report before recovery unless the condition or later user direction authorizes a path.
+
+## Maintain The Current Slice
+
+### Current States
+
+Current Slice permits:
+
+- `In progress`: active work, including its in-scope discussion, feedback, review, correction, record maintenance, and checkpoints.
+- `Blocked`: safe continuation is impossible because a required decision, dependency, capability, evidence source, stop condition, or other condition is unavailable.
+
+A slice may span multiple Workflow Feedback Loop iterations and owning skills while its intended result remains coherent. Waiting for ordinary feedback, discussing, reviewing, or correcting within scope does not make it blocked.
+
+### In-Slice Steering
+
+Record state transitions, not every activity:
+
+- do not log every edit, correction, implementation choice, or conversation;
+- questions, criticism, and review findings do not authorize changes;
+- apply authorized in-scope steering and preserve only its meaningful final effect when the slice closes;
+- if feedback would change the recorded result, scope, authority, evidence boundary, or stop conditions, classify and record the change before acting.
+
+Routine implementation feedback is in-slice collaboration, not a checkpoint or history event by default.
+
+### Scope Extensions
+
+Before expanded work begins, decide whether it extends the current slice or needs a new one.
+
+Keep an extension when:
+
+- the intended result remains coherent;
+- existing or new explicit authority covers it;
+- the combined boundary can be verified and reviewed as one unit;
+- no stop condition or owner decision requires another route.
+
+Append the extension before execution. Preserve the original boundary and record:
+
+- authority source;
+- reason and added scope;
+- added evidence;
+- changed stop conditions;
+- extension starting state.
+
+Do not rewrite the original slice to imply the extension was always planned.
+
+Use a new slice when the work needs a distinct result, authority, evidence boundary, or independently useful outcome, or when the original result is no longer pursued. First establish the current slice as `Completed`, historical `Blocked`, or `Abandoned`; then select the new slice before execution. A request to stop does not by itself establish which outcome applies.
+
+### Blocked Work
+
+Keep a newly blocked slice current, record the incident and required resolution, then stop.
+
+- If the blocker resolves and the intended result remains coherent, return the same ID to `In progress`, preserve the incident, and record any accepted extension before execution.
+- If resolution requires a distinct result, authority, or evidence boundary, park the attempt in History as `Blocked` and select a new slice.
+- Resuming a historically blocked attempt creates a new authorized slice that refers to it.
+
+Failure belongs in the result or evidence; it is not a slice state.
+
+### Review And Other Routes
+
+Implementation, verification, self-review, or a review report does not end the slice by itself. Review may support continuation, correction, more evidence, a route change, deferment, or stopping; it need not Pass.
+
+Keep the slice current through accepted in-scope correction, discussion, evidence gathering, and checkpoints that belong to its result. Move it to History only when Workflow establishes the outcome.
+
+## Close A Slice
+
+Historical states are:
+
+- `Completed`: the intended result and selected in-scope methods and checkpoints resolved sufficiently to finish.
+- `Blocked`: the unresolved attempt was parked.
+- `Abandoned`: the intended result is no longer pursued.
+
+When closing:
+
+1. Gather tests, verification, review, and checkpoint results.
+2. Move the slice to History with the established state.
+3. Preserve the original boundary and every accepted extension with its authority.
+4. Record work performed, result, task effect, evidence boundaries, and useful stable pointers.
+5. Rewrite current understanding from the resulting present state. Remove completed-event detail now owned by History rather than appending another slice or review summary.
+6. Reconcile decisions, hypotheses, proposals, blockers, and the next action only where feedback changed them.
+7. Set `Current Slice` to `None`.
+
+A learning slice may complete by disproving its hypothesis.
+
+## Decisions
+
+Use a `D-` ID for a task-local decision that affects later work:
+
+- `Active`: currently affects interpretation or later work.
+- `Superseded`: replaced or narrowed by a later decision; link both records.
+- `Retired`: remains historically valid but no longer affects later work.
+
+List only active decision summaries in Current Context. Keep full rationale and lineage in History.
+
+## Checkpoints
+
+Use checkpoints only for additional boundaries selected in an approved Plan or explicit discussion:
+
+- `Independent review`: broader judgment before dependent work.
+- `Local commit`: coherent rollback and provenance.
+- `User decision`: approval or choice needed before continuing.
+- `Continuity`: record reconciliation, pause, or handoff.
+
+Keep pending checkpoints under Current Work with their approved source and condition. A slice may reference a checkpoint that follows it, and a phase or integration checkpoint may span several slices.
+
+- A selected slice review may be a checkpoint; review between implementation changes is not one merely because work pauses for the user.
+- Record checkpoint completion separately from its judgment or decision.
+- A question, criticism, new topic, temporal proximity, or unrelated authorization is not automatically a checkpoint result.
+- Keep the Current Slice `In progress` when the checkpoint belongs to its result.
+- When a selected phase-, task-, or continuity-level checkpoint follows a completed slice, leave `Current Slice` as `None` and record the checkpoint as the next useful action.
+- After a checkpoint, move its result to History, remove it from the upcoming list, and return its outcome to Workflow.
+- If its conditions no longer hold, return the deviation to Workflow rather than forcing it.
+- A local commit checkpoint does not authorize push or integration.
+
+## Evidence And History
+
+Give each detailed fact one owner. Keep evidence with the slice that produced or used it; when checkpoint history also records that event, one entry owns the findings and exact evidence while the other gives a concise result and pointer rather than duplicating them. Preserve enough detail to recover:
+
+- what was checked or observed;
+- what the result supports and does not support;
+- which code, configuration, artifact, or external state was checked;
+- independent-review judgment and adjudication when review occurred;
+- completed checkpoint results;
+- where exact evidence can be found.
+
+Useful pointers include:
+
+```text
+file:<path>#<section>
+commit:<sha>
+output:<output-id>
+review:<conversation-or-reference>
+session:<session-id>/turn:<turn-id>
+```
+
+Use only identifiers that exist. Do not copy large raw output or create separate history for routine self-review. Preserve detail when it prevents false claims, lost rationale, or repeated investigation; do not optimize history toward an arbitrary line count.
+
+## Notes
+
+Notes preserve context with no active task effect. They normally originate from an explicit user request to note, remember, retain, or defer something.
+
+During authorized record maintenance, add an agent-originated Note only when the information is concrete, task-adjacent, worth preserving across context loss, not already recorded, and has no structured owner. Ask when authorship or retention intent matters.
+
+Notes do not authorize, prioritize, schedule, block, unblock, prove, or require follow-up. Do not periodically triage them or create Specs, Plans, issues, decisions, slices, or artifacts from them by default.
+
+A deferred unselected idea may remain a Note when it does not affect current scope or completion. If deferral changes scope, completion, or a future obligation, record that effect in its owning section while the Note remains inert.
+
+If later user direction independently makes Note content active, create the appropriate structured state from that new direction. Preserve the original user-authored Note unless the user asks to change it; reference it when provenance helps.
+
+Keep Notes last and read them as part of the complete record without treating them as instructions.
+
+## Consistency Check
+
+Before relying on or finishing an update, confirm:
+
+- Current Context agrees with recent evidence, describes the present state rather than accumulated events, and contains only active decision summaries.
+- Completed slice, review, test, hash, and live-run detail has one History owner and is not duplicated in Current Context or parallel history entries.
+- Current Work names no more than one slice and its authority source is clear.
+- Every current or historical slice keeps one stable `S-` ID.
+- Discussion, review, correction, small steering, and in-slice checkpoints do not replace a coherent Current Slice.
+- Small in-scope steering is reconciled at completion rather than logged as an event.
+- Accepted extensions preserve the original boundary and are recorded before execution and in History.
+- Ordinary in-slice feedback is not checkpoint history; selected checkpoints retain their condition and explicit result.
+- `Blocked` means safe continuation is unavailable, not merely that feedback or review is pending.
+- Proposed slices remain ordered, unnumbered, and unidentified.
+- Upcoming checkpoints still match their approved source and condition.
+- Superseded and Retired decisions and finished slices remain recoverable.
+- Notes remain inert and user-authored Notes preserve their meaning.
+- Live code, tests, docs, runtime evidence, and user decisions override contradictory memory.