Summary
The scratchpad becomes a record with fields, not a paragraph to re-read.
Because every step carries its own assumptions, dependencies and uncertainty, the place a line of reasoning went wrong is somewhere you can point at rather than something you reconstruct. Revision is part of the structure: a later step can be marked as revising an earlier one, or send you back to recheck a step, which is what separates this from a numbered list.
What it is
A single tool that holds one structured record per step of a problem: the thought itself, its type, its number out of a running total, and the assumptions, dependencies and uncertainty attached to it.
What you get
- A numbered thought with a thoughtType and a totalThoughts, so a chain of reasoning has a shape rather than just a length
- Assumptions and dependencies recorded against each step instead of left implicit
- An uncertainty value carried alongside the step it belongs to
- proofElements for a claim you can argue, experimentalElements for one that has to be tested
- implementationNotes for the practical end of the chain
- Revision in place: isRevision and revisesThought point a new step at an earlier one, and recheckStep reopens a step already passed
- nextThoughtNeeded to declare the chain unfinished
Requirements
Node on your PATH. No account and no key.
Setup effort
One command — npx -y server-shannon-thinking