Working titles in play:

Stake-in-the-ground note. Captures a thinking session, not canon. Do not promote without Tom's pass. The job of this file is to fix two things before they float off — a candidate proposition, and the design spine of a layer the framework doesn't have yet.


Why now

CE today is strong at evaluation. /applications/moves hands the framework a configuration-change and returns a Δω verdict — degrading, preserving, expanding, ambiguous. It judges moves that already exist. What it cannot yet do is help a reader construct a move, feel which level a problem actually lives at, or come away holding a tool rather than a conclusion.

The missing layer is constructive and participatory — "where the rubber meets the road." Its purpose is not to deliver answers but to coordinate people around a single realisation: that a configuration-based economics is not impossible, and that much of the value we'd need is already here, merely frozen. Two ideas surfaced in conversation that this layer should be built on. Both deserve articulation in the framework proper, not just in a surface.


Idea 1 — Held value is not reachable value (candidate proposition)

The claim

A great deal of economic value is stored in frozen configurations: capital locked into a shape that subtracts from the reachable set instead of widening it. Configuration economics already says value lives in what is reachable (P3, value-option-space). The corollary nobody has stated yet: value that is held but not reaching anything is, in option-space terms, closer to dead than to stored. It sits on the books as wealth while contributing little or nothing to R_living.

The unification that makes it land

Two examples that look unrelated are the same failure:

These are one phenomenon: capital frozen out of the reachable set. The demurrage intuition (money that decays if hoarded) was never really about money or about fairness — it is a special case of a general principle: configurations that lock value out of reach are mispriced as wealth.

Why it matters and why the tone falls out for free

This reframing is relentlessly hopeful with zero alarm, and that is structural, not cosmetic. The cars already exist. The value is already there. Abundance is not something to be manufactured against a ticking clock; it is sitting frozen in plain sight, and the work is thawing it — counting what is reachable instead of what is held. No villains, no urgency, no political identity required. The optimism is a consequence of the accounting, not a mood laid over it.

Honest edges (steelman before promotion)


Idea 2 — The altitude move (the core thinking tool)

The claim

The deepest skill the framework can transmit is not any particular answer. It is finding the level of abstraction a problem actually lives at before solving it.

Worked instance: you can build a far better combustion engine — more efficient, particulate-free — and it is a brilliant answer to a question that quietly stopped being the right one. Car ownership is a 150-year-old frozen answer to "how do I get about." You can optimise the artefact forever without noticing the question has moved up a level. The efficient engine passes the local Δω test and fails the real one: it optimises a configuration that is itself shrinking the reachable set.

That gap — local-optimal, globally option-space-negative — is the lesson. Configuration economics already contains the test for it (does the move widen R_living, or merely tune a contracting configuration?). What it has not done is name the move explicitly and teach people to run it.

Why this is the spine of the explanation layer

It dictates the pedagogy. Every constructive scenario should hold both altitudes side by side — the artefact-level fix and the configuration-level reframe — not to dismiss the artefact fix (better engines are good) but so the reader feels the altitude shift happen. Do it across two or three domains and the reader internalises the move and can run it themselves. The win is not handing them answers; it is handing them the altimeter.

A corollary risk this names: solutions at the wrong level of abstraction. Half the explanation layer may be more "here is how to tell which level you are on" than "here is the system to build." The layer should slow the reader down at diagnosis before they sprint to a fix.

Where it might live in the framework

The altitude move is more method than proposition — it is how to apply the framework, not a claim within it. Candidate homes:


Design implications for the explanation layer (not a build — direction)

  1. Constructive, not evaluative. Where /applications/moves asks "is this move good?", this layer asks "what could we build, and how would we start?" It reuses the moves template (pre/post, who-bears-costs, what-would-change-the-verdict) but runs it forward from a proposed system.
  2. Tweakable leaves. The eventual artefact is a workbench, not an essay: levers on a scenario, with the board-by-board / horizon-by-horizon verdict recomputing as they move. That live template would be the framework's first genuine instrument — the thinking tool that does not yet exist.
  3. Ship every design with its own attack. This is the tonal antibody and it is non-negotiable. CE already has adversarial transparency (/objections, /attack). A proposed system published alongside its strongest critique reads as engineering, not advocacy — which is what keeps the layer an invitation to think rather than a manifesto to join, and keeps the wrong energy out.
  4. Real-world toeholds over utopia. Favour domains with a working instance to point at (mutual-credit currencies: WIR since 1934, Sardex; repair/circular materials; Ostrom commons) so it is "an area we could start," not a daydream.
  5. Money is a thread, not the headline. Demurrage / complementary currencies are strong material — but reframed as "what would money have to be, physically, for holding it to widen option space instead of freezing it?" (i.e. an application of Idea 1), never as "UBI," which arrives pre-politicised and recruits the partisan energy to be avoided. Lead the layer's debut with a tactile, low-charge domain (repair, commons); bring money second.

Status / next