progress

You can track evolving understanding of a debugging investigation by storing sequentially numbered progression documents that record hypotheses, experiments, corrections, and final synthesis, ensuring future sessions pick up exactly where earlier work left off.

The best way to preserve session history for research workflows is to maintain a sequence of progression documents capturing baselines, deepenings, pivots, and syntheses within a git-backed knowledge repository that remains searchable across the project.

You start tracking an investigative arc by running the CLI start command with a topic name, which initializes the sequential document numbering and injects the active progression into the current session context.

Yes, you can link corrections to original reasoning documents through explicit correction links, ensuring that mistakes and their fixes remain discoverable and preserving the full reasoning arc of the investigation.

Yes, session history tracking integrates directly with a git-backed knowledge repository, allowing active progressions to be injected into session context and remain searchable across the entire project knowledge base.

You need progression documents for design workflows when an investigation spans multiple sessions and requires capturing baselines, recording what was tried, documenting what was wrong, and explaining why conclusions changed over time.