Main idea

A method taken as a block lends itself to no precise question. "Has anyone already imagined a persistent workspace?" has no usable answer: the phrasing is too broad to sort anything, and too dependent on the author to turn up an antecedent.

The book describing the Contexte method was therefore cut into twenty-four concepts and twelve structuring relations. The questions then become askable one by one: has anyone already separated the raw source from the derived knowledge? does any system distinguish the present from the historical log? what happens when a piece of knowledge is copied from one autonomous space into another?

The breaking-down is not there to simplify the method. It is there to produce objects small enough for an answer to exist.

Why it matters

This changes the nature of what can be established. On a block, you can only conclude by feel — "it looks like it" or "it doesn't". On components, each element gets a separate verdict, and the result stops being an overall impression.

It also makes relations appear as objects in their own right: two systems can share all their building blocks and differ entirely in the way those blocks connect. Without the breakdown, that difference stays invisible.

Nuances and limits

The breakdown is itself an act of interpretation: it is the author who decides where the joints run, and a different breakdown would give different questions, and therefore different antecedents.

And it says nothing at all about one thing: a method whose every component has an antecedent can still be distinct through its assembly, which no question asked component by component will ever show.

Open questions

• Do two people breaking down the same method end up with the same number of components, and what does the gap tell us?