Develop Lines of Thought with Working Notes
About this pattern
This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.
How to use this pattern
Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.
Type: Method pattern Status: Stable Normativity: Normative
Use this pattern when useful observations, reading or tentative thoughts recur across occasions, but keeping them has not yet made them available for developing a question or argument. You remember an interesting distinction without its grounds, find a relevant note without knowing why it matters, or repeatedly start an explanation whose missing connection remains hidden.
Relations
Content
Problem frame
Use this pattern when useful observations, reading or tentative thoughts recur across occasions, but keeping them has not yet made them available for developing a question or argument. You remember an interesting distinction without its grounds, find a relevant note without knowing why it matters, or repeatedly start an explanation whose missing connection remains hidden.
This is a branch of reasoning practice: developing thought through addressable notes and meaningful relations between them. Its material is an evolving formulation, the grounds it uses and the connections through which another occasion of reasoning can continue it. A note can be handwritten, an addressable block or a separate file. The method concerns what the practitioner does with that material; storage and retrieval engineering remain further work when the available means are inadequate.
First useful move. Take one available observation, source passage or rough note. Say what it lets you claim or ask, then compare that formulation with one relevant earlier thought. Write the consequential relation, including an unresolved difference when that is what the comparison produces.
The first result can be a better question, a counterexample, a missing premise or a usable continuation. A final publication topic need not be known. An assigned topic also provides an entry: follow the part of its argument that the available material cannot yet support.
Use a sufficient project record directly when it already supports the next action. A longer-lived note network is worthwhile when later comparison, recombination or development warrants the work of keeping it usable. Routine recording, factual retrieval and recovery of an already specified interrupted action can end without building such a network. Learning to reason independently and obtaining a useful argument with assistance are different purposes.
Problem
Chronological capture preserves occasions but can hide relations between them. A topical folder can collect similar material without explaining what one contribution changes in another. Extensive linking can make navigation possible while leaving the actual inference unwritten.
The opposite repair also fails: demanding a polished, correctly classified permanent note before its thought has developed removes the provisional material from which a question could emerge. The task is to give thought enough stable form to be compared and carried forward while allowing its meaning, connections and intended use to change.
Forces
Solution
Develop the note through its use in reasoning. Recover its meaning, formulate the thought, test a meaningful connection, follow what that connection changes, and leave a usable way to return. These operations can recur in a different order as the work reveals another gap.
Recover a thought → make one useful connection → follow what it changes → leave a usable return.
A collection becomes useful through these continuations. Its size and number of links do not establish them.
Enter through available material
Begin where something is available: an observed episode, a passage, an objection to a draft, an existing question or a rough phrase. Recover enough of its context to tell what the thought concerns and why it attracted attention. If a cue no longer permits that recovery, return to the episode or source when available. Otherwise retain the uncertainty or discard the cue when no needed use depends on it.
A short capture serves the current interruption. Develop it while its meaning is still recoverable when later work warrants retaining it. Ask what the next occasion would need to know. “Bench slow” may remind its author of a conversation today; later comparison needs the job, the observed intervals and which result was called slow. The useful repair supplies those distinctions, without expanding every cue into the same form.
Keep a simple stable place and means of addressing notes. A known capture place, a source return and compatible small units can make comparison and rearrangement routine. Start with current material that matters. Processing an entire old archive is unnecessary when the present question can be developed without it.
Formulate a thought with its grounds
Write the claim, question or conjecture in terms you can use in reasoning. For a source-derived note, recover the source's question, conditions and actual contribution before stating what follows for your own work. Distinguish the source account from your inference. A useful paraphrase preserves the source's limits; a quotation still needs its context when that changes its meaning.
Keep the reason with the thought. “These jobs have different total delays but equal bench occupation” needs the event choices and calculation that support it. “Delay comes from waiting” is a stronger explanation and needs another basis. Let the note retain the weaker result when that is what the material establishes.
Choose a unit that can participate in a later argument. Split two thoughts when each needs independent use or revision. Keep a short derivation together when separating its steps would make the inference hard to recover. One sentence, one screen and one file are possible conveniences, not definitions of a thought.
An unresolved question can have a stable address. Its address makes it referable; its formulation states what remains unknown. Where a later use depends on an earlier formulation, retain that formulation or an exact return to it before changing the note. An observed event, a claim about it and a project-specific restatement may require different change treatment.
Make the connection do reasoning work
Find an earlier thought that could change the new one or be changed by it. Search by the working problem and possible contribution as well as by subject vocabulary. A note about obtaining a usable result may matter in testing, review and delivery although their local words differ.
Read the two thoughts with their grounds. Try the relevant operation:
- compare their meanings and conditions before treating them as agreement or contradiction;
- use one as a premise and attempt the inference the other needs;
- use a contrary case to test a general claim;
- carry a relation into another case and identify what makes that transfer applicable; or
- expose an unresolved dependency that neither thought presently supplies.
State the relation that survives this attempt. “Related to note N” can be enough for a familiar return; otherwise add the reason for the connection. For example, “This second attempt defeats the earlier assumption that one job has one occupation interval; the earlier two-job calculation is unchanged.” The relation now tells the later reader what to reconsider.
A resemblance can propose a question before it supports an explanation. Keep that difference in the note. If two cases lack the same result, their causes may still differ. A consequential counterexample narrows or rejects the proposed relation; it need not erase the observations that prompted it.
Use B.5.QD when the result changes the question and B.5.RR when a changed premise must be carried through dependent reasoning. Use the relevant subject method for the inference, experiment or construction itself. A new arrangement can make a missing premise visible without supplying it.
Provide entries for future occasions
Give a retained thought a route from a question in which it may help. A subject label can be useful, but an entry such as “apparent speed differences with different completion events” names a future reasoning use more directly than “bench notes”.
A small overview can state how several notes currently connect. It can distinguish an established inference from a promising analogy and expose an open question. Revise that account when the relationships change. Its purpose is to make a line of reasoning findable and inspectable, not to establish a final taxonomy.
A journal preserves sequence and contemporaneous context. A note network can expose relations across episodes. A project file holds what one undertaking uses. They may refer to the same observation. Keep one observation's identity and grounds recoverable across these uses; displaying it in several views creates no additional observation.
Use the access arrangement actually available. A link that only the author can open does not supply another reader with the note. When a collection becomes too difficult to find or maintain, the relevant knowledge-access, notation or integration method can improve that arrangement. A working pair of notes does not require that engineering work in advance.
Develop or defer the emerging question
Follow a connection while it can yield a useful next result under the available means. The result may be a refined question rather than an answer. Ask what evidence or construction could now distinguish the live possibilities. Continue with that contribution, or leave the question in a form that a later occasion can use.
Two kinds of return are useful. A known deferred intention can be recalled at its next occasion. A semantic entry can expose a relevant thought while following a different question, including when its author has forgotten that it exists. Saving the note supplies neither return automatically.
For a deliberate deferral, retain the open question, the basis already obtained and what would make continuation worthwhile or necessary. Use a concrete reminder when there is a known occasion. Use a meaningful entry when the future occasion is not known. No invented deadline is needed merely to make an unfinished thought look managed.
Compare deferral with the present reliance. If today's choice consumes the missing premise, obtain it, choose a supported alternative or withhold the dependent conclusion. If no current use consumes it, the question may remain open. This is the useful resemblance to lazy evaluation: work can wait until its result matters, provided the later use can recover the dependency and initiate the needed work.
Compose an argument for a recipient
When a project becomes useful or an assigned question needs an answer, select the notes that can contribute to it. State the proposed conclusion and arrange the reasons in the order the recipient needs. A visible outline can keep the whole argument available while one passage is being written.
Turn the selected material into that argument. Supply missing transitions, examine contrary material, remove repetitions and distinguish a useful example from evidence for a general claim. A chain of links is not yet the written inference. Composition often exposes a premise that seemed present only because the author knew the collection.
A project may develop copies or selected passages differently from the retained notes. Keep a source return where it matters; the new use need not rewrite every original formulation. Conversely, if new evidence defeats a retained claim still used elsewhere, return that change to the affected reasoning. Follow the actual dependency rather than synchronizing every sentence merely because it was copied.
A useful collection can remain incomplete. An argument offered for reliance must supply the premises and inferential steps its conclusion needs, or state its bounded unresolved result. Use the subject method to obtain what is missing. Stop polishing the surrounding wording when an unsupported premise is the obstacle.
Leave a usable continuation
At a useful stopping point, leave the result that was obtained and the next live question or operation when one remains. The later user should be able to recover why that continuation follows. A completed argument, a narrowed question and a deliberately abandoned conjecture have different further uses.
Retain long-lived notes when their future use warrants it. Processed fleeting cues and completed project material can have other dispositions. Apply the relevant retention, confidentiality and access rules before sharing or discarding material. The method supplies no authority to preserve or expose restricted information.
For a handoff, select what the recipient needs to continue the particular reasoning: its present question, obtained result, consequential uncertainty, usable source returns and next contribution. Make abbreviated personal relations explicit where that reader cannot recover them. The whole private collection need not travel.
Assess a stronger claim with the evidence it requires. A coherent note connection supports its stated inference. A reader's successful recovery supports that use under that reader's preparation and help. Independent capability, learning and improved production performance require their own assessment.
Archetypal Grounding
From a duration note to a new cross-case question
A practitioner is investigating reports that a bench is slow. Job Q41 is received at 09:05 and has a usable result at 10:00; the bench is occupied from 09:30 to 10:00. Q42 is received at 11:00, occupies the bench immediately and has a usable result at 11:30. The comparison developed in A.6.3.RT.OE distinguishes 55 versus 30 minutes until a result from equal 30-minute occupation.
A rough cue says “same bench time, different speed”. Before its context disappears, the practitioner writes a usable thought:
Compare the same beginning and result events. Q41 and Q42 both occupy the bench for 30 minutes. Their receipt-to-result durations differ because Q41 begins occupation 25 minutes after receipt. These observations distinguish waiting from occupation; they do not explain why the wait occurred.
The note returns to the two jobs' observed times. An entry for “apparent speed differences” makes it available beyond a folder devoted to this bench.
Q43 later occupies the bench from 13:00 to 13:30 unsuccessfully, then from 13:50 to 14:20 successfully; its receipt is at 13:00. Time to the usable result is 80 minutes, occupation is 60 and the interval between attempts is 20. The practitioner adds:
One job can require several attempts. Relating one job directly to one occupation interval would lose Q43's history. Keep the attempt and its outcome available when comparing time to a usable result.
The connection to the earlier note states the changed assumption. Q41/Q42's observations and calculation remain valid. The new distinction changes the construction needed for Q43. The practitioner places this note under an entry for time to a usable result, with a return from the earlier speed-comparison entry.
In another project, all reviews are reported as completed, but the receiving comparison still lacks a common basis: the reviews evaluated different configurations. While asking whether completed activities supplied the usable result now needed, the practitioner follows the usable-result entry and retrieves the duration notes. Juxtaposition produces a new question:
Which event makes a result available for its next use? Ending the producing activity and obtaining a usable receiving result can differ. Investigate the required relation in each case; equal words such as “completed” do not establish it.
This note is an own cross-case conjecture and question. Its links name the bench and review contributions and preserve their different grounds. It proposes an inquiry; it does not establish a common cause.
Now change the review facts: all reviewers used a common valid basis, but the recipient has not opened their results. The missing-basis explanation fails in that case. The practitioner narrows the connection to the distinction between a result's availability and its actual use, retaining the original bench observations. If no current project needs this question, the semantic entry is a sufficient continuation. If a delivery decision needs it today, the project must establish which result is actually available before acting.
Develop an assigned explanation from mathematical notes
A writer must explain what can be inferred about sums of irrational real numbers. The writer already understands rational numbers and the usual proof that sqrt(2) is irrational. One note contains a proved statement: adding a rational number to an irrational number yields an irrational number. If the sum were rational, subtracting the rational addend would make the other addend rational.
A rough second note asks whether adding two positive irrational numbers must also yield an irrational number. Keeping the quantifiers in the formulation makes a counterexample searchable. The writer tries sqrt(2) and 2 - sqrt(2). Both are positive. The second is irrational, since making it rational would make sqrt(2) rational by subtraction. Their sum is exactly 2.
The new note retains the two values and that short justification. Its link to the first says: “The first proof requires a rational addend; replacing that condition by an irrational addend permits a rational sum.” Separating the counterexample from its positivity and irrationality grounds would make later use require reconstruction. A small connected note is sufficient.
The assigned explanation also needs a case where two positive irrational addends have an irrational sum. Using sqrt(2) + sqrt(2) = 2sqrt(2) supplies it: if that sum were rational, division by the nonzero rational 2 would make sqrt(2) rational. The two cases now support the bounded answer that the sum can be rational or irrational. They do not classify products, limits or other operations.
The writer's outline becomes: distinguish the rational-addend theorem; present the rational-sum counterexample; present the irrational-sum case; state the resulting limit of inference. Rewriting the notes into that order produces an explanation for the assigned question. The earlier theorem remains in the collection, with its actual condition.
A later question about squares can enter through the same concern with what an operation preserves. The present note does not answer it. The writer either develops that question through the relevant mathematics or retains the possible connection for another occasion.
Carry a developing question into operational case work
An engineer has the notes in :5.1, including their corrected question about availability and actual use. They do not establish that every delay has the bench's cause. The engineer keeps an entry for “completed activity, receiving result still unavailable”.
At an already authorized support handover, a case note says: “Nightly exports finish on time; the senior analyst removes duplicates every morning. The customer proposes buying faster workers.” Private row contents remain in the customer's system. The engineer's permitted work is to examine the support question, not to change that system.
The engineer follows the entry and brings the earlier question to this episode: which result must “finished” supply to the analyst, and what work remains after that event? The comparison produces a new working note:
A recorded completion can leave a receiving contribution to be performed. Here the export has ended, but producing a usable report still includes duplicate reconciliation. Faster export has not yet been shown to remove that contribution. The bench and review cases helped pose this question; they do not identify the export's cause.
The connection states its limited transfer. The support case remains the source of this observation. A return to that case lets the engineer distinguish the customer's proposal from the proposed explanation. The note also leaves a question: under which receiving protocol is reconciliation needed, and what contribution could replace the manual work?
Now use the subject information available in this constructed case. The current manual distinguishes protocol v1, which requires manual receipt reconciliation, from v2, which permits idempotent resend after absence of a receipt has been confirmed. The installed protocol is unknown. The engineer's useful support result is a conditional explanation and a request for that configuration fact through the authorized local service. Neither the resemblance to the earlier cases nor the finished note selects automatic resend.
A later signed configuration report says v2. The retained case question makes its contribution recognizable: it supplies the missing protocol fact. At the next permitted handover, the engineer reads the governing manual and the current case basis. Under the stipulated v2 rule, absence of the relevant receipt must still be confirmed before the proposed resend. The configuration result has answered one question; it has not performed that check or the action. The recipient receives the case-specific explanation and needed next contribution, not the engineer's entire note collection.
Compare the full construction with the smaller incumbent. The ordinary case record already retains the duplicate episode, the protocol question and the eventual report. It is sufficient to resume this same support case; copying those facts into a second case ledger adds no needed capability. The longer-lived note contributes a separately developed question, its grounds and its limits across the bench, review and export occasions. Making that thought available costs the formulation and maintenance of the note and entry. When a practitioner can obtain the same question directly from the present record, no advantage of the additional network is established for that use. Keep the network contribution only for continuations that actually use it.
Finally change the governing source. A new manual still describes v2 but additionally requires destination certification. The available report identifies v2 and says nothing about certification. Preserve that observation, the original duplicate episode and the question that connected them. Revise the conditional advice: the former basis is insufficient for this proposed resend. Obtain the certification contribution through an authorized route or withhold the action; the current protocol fact need not be collected again merely because another premise is missing.
The note has helped construct and carry a question into work. The allowed encounter, configuration read, interpretation of the manual and controlled operational action remain actual contributions with their own conditions. A saved connection performs none of them by itself.
Keep the simpler project record when it suffices
An operator records a replacement part, installation time and required follow-up in an existing maintenance case. The next technician can find the current state and perform the scheduled check through that case. Copying those facts into a separate personal note network supplies no identified continuation.
Use the case directly. If several cases later expose a recurring unexplained relation, formulate that question with returns to the relevant observations. The later inquiry can justify a connected note without replacing the operational record.
Bias-Annotation
The method favors work in which thoughts can be expressed, compared and revisited. Tacit performance can supply observations, but written description does not by itself teach the performance. Source familiarity affects how much context a useful note needs.
The examples are constructed reasoning cases. They establish their explicit calculations and inferences, not a measured advantage of one note system. Assistance may produce a useful formulation while leaving the user's own ability to formulate and connect unchanged.
Conformance Checklist
- CC-WN-1 — Recoverable thought. A retained formulation states a usable claim or question and the grounds its next use needs.
- CC-WN-2 — Source and continuation. Source meaning, observation and own inference remain distinguishable where reliance depends on them.
- CC-WN-3 — Consequential connection. A connection supplies a reason, contrast, counterexample, transfer question or other stated contribution to reasoning.
- CC-WN-4 — Appropriate unit. Separation supports independent use without losing a required inference.
- CC-WN-5 — Available return. A relevant future occasion can find and interpret the retained contribution under its actual access conditions.
- CC-WN-6 — Changed condition. Contrary evidence or a changed question revises affected reasoning while preserving still-valid observations and results.
- CC-WN-7 — Use-relative closure. Deferral, a completed argument and a blocked reliance retain their distinct requirements.
- CC-WN-8 — Proportionate support. Capture, connection and maintenance contribute enough to the intended use to warrant their burden.
Common Anti-Patterns and How to Avoid Them
Consequences
A useful thought can remain available across occasions without a finished project or final classification. Connections become operations that develop reasoning, and composition can reveal what the collection still does not supply.
The practitioner spends time on recoverable formulation, meaningful entries and occasional revision. The return depends on later use. A sufficient immediate record can remain the better choice when that further work has no identified contribution.
Architectural Rationale
A retained expression and a line of reasoning have different continuity conditions. An observation can remain unchanged while an interpretation is corrected; a question can retain its address while its proposed answer changes; a project argument can select and rewrite only part of the collection.
Stable addresses and compatible units make those changes manageable. The reasoning comes from the operations on their content and relations. The collection therefore supports inquiry without determining the subject truth or requiring a uniform lifecycle for every note.
B.5.QD develops a question from a result, B.5.RR revises dependent reasoning, and A.6.3.RT.OE prepares an expression for an operation. The present method connects such work across retained formulations and later occasions, including the passage from a developing network to a recipient's argument.
SoTA-Echoing
Practice question. How can retained material develop thought across occasions without making capture and organization the whole activity?
Selected line. Adapt the connected practice in Sönke Ahrens, How to Take Smart Notes, revised and expanded edition (2022): source understanding and own formulation, meaningful connections, questions that develop through work, and composition that exposes missing argument. Chapter 2's overview, chapters 10–12's reading and connection work and chapter 13's development of a written contribution supply that account. The appendix qualifies historical practice: an addressable note can remain abbreviated or unresolved. Stable routine arrangements enable comparison without making substantive classification final.
Comparable alternatives. Compare a sufficient chronological project record, a persistent note network and direct drafting for a fixed question. In :5.1 the project record already preserves the bench events and supports its immediate calculation. The additional note and problem-based entry cost formulation and maintenance; they make the later cross-case comparison available without requiring the writer to remember the bench episode. If no such continuation is needed, retain the project record alone. In :5.2 an assigned question starts the work directly; the existing theorem and two constructed cases suffice. Building a larger collection before writing would add no needed premise. In :5.3 the case record already supplies same-case resumption, while the connected note carries a question developed across unlike episodes. The comparison retains both the useful transfer and the no-network alternative; changed operational conditions still require their own qualification.
Luhmann's 1981 account, Kommunikation mit Zettelkästen, is a historical example of sustained practice. Andy Matuschak's daily working log and writing strategy provide inspectable digital-practice alternatives. Their descriptions are method accounts, not controlled efficacy comparisons.
Decision and cost. Adopt stable addressability and recoverable source returns when later reasoning uses them. Adapt note unity to independent use and connected inference, and retain temporary project views when their argument develops differently. Reject a universal promotion ladder or note-count target: neither selects the useful result in these cases. The accepted burden is selective formulation and connection in exchange for an available later continuation. The comparisons establish these constructed uses; learning and general productivity remain empirical questions.
Reopen the arrangement when useful thoughts repeatedly remain unfindable, mandatory structure suppresses a needed distinction, maintenance exceeds the contribution to actual work, or a simpler available practice supports the same continuation with less effort.
Relations
- B.5.PI and B.5.EA help initiate inquiry and articulate a working distinction from experience.
- B.5.QD develops a new question from a result or construction; B.5.QD.CF examines conflicting assumptions when that is the obstacle.
- B.5.RA and B.5.RC recover an argument or construction needed to understand and continue a source.
- B.5.RR revises reasoning after a premise or question changes.
- A.6.3.RT.OE constructs an expression for the next operation; A.6.3.RT preserves content through a representation change.
- A.15.10 and A.15.11 supply resumption of interrupted work and an occasion where a relevant contribution can be used.
- C.39.RO develops a reusable operation when the successful local construction needs that further result.
- C.2.8 qualifies what a recipient can recover under stated preparation, access and assistance.
B.5.WN:End
Last Updated: 2026-10-06 — this section last modified in upstream FPF commit a1d21787 (github.com/ailev/FPF)