A Stepped Model with Plateaus
Picking up from the last post ā I want to get more concrete about what I actually think is missing, because on reflection itās much smaller than it might have sounded.
Most of the hard work is already done. Michael Beckerās video library is, honestly, a remarkable resource. Itās thorough, itās patient, itās deeply informed, and for anyone willing to sit with it, you can learn the fundamentals of Tinderbox in a surprisingly short amount of time. Layer on top of that the forum ā which, for all the ānew users feel out of their depthā observations, remains genuinely generous when asked clear questions ā and the raw material for learning the tool is all there.
So what Iām really proposing isnāt a new curriculum. Itās a chronology and a leveling laid over what already exists. A map to the resources, not a replacement for them.
The idea behind the structure below is simple: every level should be a place you can genuinely live in. Not a stepping stone youāre forced off as soon as you arrive, but a stable way of working thatās complete in itself. Some people may spend an afternoon on Level 1 and move on. Others may stay there for months, and thatās equally valid. Progression happens when the material itself asks for more structure ā never before. This is essentially Mark Bernsteinās concept of incremental formalization from The Tinderbox Way, applied to the learning curve itself: you add complexity when the content calls for it, not because the tool offers it.
Level 0 ā Introduction: What Tinderbox Actually Is
Most people already know what notes are. You write something down ā a thought, a quote, a task, a piece of research ā give it a title, put it somewhere. Thatās the baseline, and itās what every notes app in the world shares. Tinderbox doesnāt replace that idea. It extends it.
The one shift Tinderbox asks you to make is this: what if every note could also carry information about itself? Not just a title and some text, but also a date, a source, a priority, a status, a category, a color, a confidence level ā whatever the work actually needs. These pieces of information are called attributes, and together with the title and the body text that the note already has, theyāre what makes a Tinderbox note different from a note anywhere else.
Once a note carries attributes, something quietly changes. The note is no longer just a piece of text ā it becomes an object with properties. And once your notes have properties, you can do things with them that a plain notebook canāt: filter them, group them, compare them, connect them, let the system watch for patterns, let it respond when something changes. You can start to set up simple rules that react to those properties, so that the document begins to organize itself as you add to it.
From that point on, a Tinderbox file stops feeling like a list and starts feeling like a network. Every note contributes to the whole. Every attribute gives the system something to work with. Every link expresses a relationship. You build up a multi-dimensional web of your own material ā and because the system understands the metadata youāve given it, it can help you see that material in ways your unaided memory cannot.
That is really the entire underlying idea. Eastgate describes Tinderbox as a tool to visualize, analyze, and share your ideas, and the levels that follow are progressively deeper ways of doing exactly that. Level 1 is the pure notes. Level 2 adds the attributes that give notes context. Level 3 lets the system start organizing itself. Level 4 lets it act on its own. Level 5 connects it outward to the rest of your work.
But the principle at the heart of all of it stays the same throughout: notes with context, arranged into a network, that you can think with rather than just read.
Level 1 ā Capture
Notes, containers, text. Thatās it.
Just writing notes and putting them somewhere. A note has a title and a body. A container holds notes. You can move things around, rename them, delete them. The outline view is enough. No attributes yet, no prototypes, no agents.
This level is already a complete tool. Many people use Tinderbox this way for quick project files and never need more. If all you want is a flexible, outline-capable notebook with spatial rearrangement, you can stop here.
Level 2 ā Context
Adding attributes to notes. Using views to see them differently.
This is the first real Tinderbox-specific shift. A note stops being just text and starts carrying metadata: a date, a status, a source, a priority, a color, whatever the work asks for. Once attributes exist, the Attribute Browser becomes useful, the Outline view gets more informative, and the Map view starts showing patterns you couldnāt see before.
This level is where Tinderbox begins to feel clearly different from other note apps. And critically, itās already enormously powerful. A reading-notes system, a research log, a meeting-notes archive, a project tracker ā all of these work beautifully at Level 2 alone. You can live here for a long time.
Level 3 ā Structure
Prototypes for inheritance, links for meaning, agents as smart filters.
Now the system starts organizing itself. Prototypes mean you define a kind of note once and all notes of that kind inherit from it ā change the prototype, and every note that uses it updates. Typed links mean connections between notes carry meaning, not just existence. Agents continuously watch your document and gather notes that match a query, updating themselves as your material changes.
This is where the famous Tinderbox āaha momentā usually happens. Watching an agent pull notes together automatically, based on attributes you set, is genuinely different from anything most people have used. Plenty of experienced users operate at Level 3 indefinitely and never feel theyāre missing anything.
Level 4 ā Behavior
Rules, edicts, OnAdd actions, Action Code as something you actually write.
At Level 3 the system reacts to how you categorize things. At Level 4 the system acts on its own. A rule recalculates an attribute every time the note changes. An OnAdd action applies a prototype the moment a note is dropped into a container. An edict runs on a slower schedule for expensive computations.
This is also where Action Code stops being a curiosity and becomes a working language. Not the full reference ā just a small vocabulary of common patterns. Most users who reach Level 4 use maybe a dozen operators comfortably and leave the rest for when they need them.
Level 5 ā Integration
Import, export, publishing, AI, cross-tool workflows.
Finally, Tinderbox as part of a wider ecosystem. Pulling data in from DEVONthink, Bookends, spreadsheets, or plain files. Exporting to HTML, Markdown, or fully designed PDFs. Using the AI features. Building templates that produce polished documents. Moving notes to and from other tools in your stack.
This is the most open-ended level, and itās also the one where paths diverge sharply depending on what you actually do. There isnāt really one Level 5 ā there are many, shaped by each personās work.
Why this shape, and why plateaus matter
The reason this is split into five working levels (plus the introduction) rather than a shorter sequence is that each one represents a genuinely different mode of working ā which maps, I think, onto the distinction Mark Bernstein draws in The Tinderbox Way between taking notes, thinking with notes, and analyzing through structure. Level 1 is capture. Level 2 is giving your material enough context to be thought about. Level 3 is letting structure emerge from the material. Level 4 is letting the system carry some of the cognitive load. Level 5 is connecting the whole thing outward.
The plateau idea matters because it gives people permission to stop. One of the quiet frustrations of learning Tinderbox is the sense that youāre supposed to eventually āuse everything.ā You arenāt. The tool is designed to be useful at any depth, and a Level 2 user doing careful, attribute-driven reading notes is not doing Tinderbox āwrongā because they havenāt written an agent yet. Theyāre simply at the level their work currently needs.
Incremental formalization, in this framing, is the engine that moves you between levels ā but only when the content itself calls for it.
Closing thought
I realize this is a lot, and I want to be clear about what Iām actually proposing. Not a new curriculum. Not a criticism of any existing resource. Just a front door ā a short, explicit, leveled path through the material that already exists, with the early levels stripped down to the absolute minimum a new user needs to feel theyāve arrived.
If any of this is useful to anyone building or revisiting introductory material, Iād be glad to contribute. And if it isnāt ā no harm done, and thank you again for the discussion that got me thinking about it in the first place.