Concepts
The durable layer — the portable ideas this site has learned, each pinned to the content that carries it.
Table of Contents
Concepts
This site runs on three layers, ranked by shelf life: context is what you spend, content is what you ship, and the concept is the only part with a shelf life longer than the session that produced it. Content rots and context evaporates — so the durable ideas get a home of their own right here, each one pinned to the content that carried it. The idea behind this page is itself a Field Note.
Delete any post and keep the sentence, and you should lose nothing.
Make the durable layer durable on purpose.
Content rots and context evaporates; the concept is the only layer with a shelf life longer than the session that produced it. Nothing forces you to capture it, so give it a home — otherwise it washes out with the container.
knowledge-management meta context-engineering
Carried by: Concepts, Context, Content: I Hoard the One That Rots
Related: CONCEPT-005 · CONCEPT-006
Put your style guide in git as data, not a PDF.
A voice lives longer as machine-readable files any fresh session can read in seconds than as a document a person has to find, open, and interpret. Store the rules where the thing that follows them already looks.
brand knowledge-management context-engineering
Carried by: Your Style Guide Belongs in Git as Data, Not a PDF · When Your Style Guide Quietly Turns Into Code
Related: CONCEPT-005
The human is the rate limiter.
When a robot opens the work and a human approves it, throughput is bounded by review speed, not generation speed. Cap the work in flight to what the reviewer can absorb; adding workers past that point only grows the queue.
autonomy ci workflow
Carried by: The Human Is the Rate Limiter · The Rate Limiter Grows a Bypass Lane
Related: CONCEPT-007
A placeholder only works if it is visibly incomplete.
A stand-in that looks finished gets shipped as if it were. Make the temporary thing announce itself, so nobody mistakes the scaffold for the building and the real version actually gets built.
design quality
Carried by: The Plugin That Isn't a Plugin
Related: CONCEPT-006
Context you can rebuild on demand beats context you tried to freeze.
You will lose your working context — the session ends, the tab closes, the person leaves. So do not hoard every token; make the context cheap to reassemble from durable sources. Re-derivable beats preserved.
context-engineering knowledge-management
Carried by: Concepts, Context, Content: I Hoard the One That Rots
Related: CONCEPT-001 · CONCEPT-002
Content that hurts to delete is secretly load-bearing — that is a bug, not a milestone.
If removing one page would lose an idea, that page is the only place the idea was ever written down. The fix is to capture the concept somewhere durable, so any single piece of content stays disposable without regret.
knowledge-management meta
Carried by: Concepts, Context, Content: I Hoard the One That Rots
Related: CONCEPT-001
A merge that never conflicts still needs its own guard against twins.
A union merge keeps both sides and never stops to ask, so two branches can each add the same id and the collision only surfaces after the merge. When a safety check can't fire, add the one that can — and wire it to the gate.
ci git autonomy
Carried by: The merge that never conflicts, and the backlog item it quietly ate · The Bouncer That Only Checks for Twins
Related: CONCEPT-003
The machine reads this layer too. The read-only MCP server exposes a whole
concept engine: find_concepts (“what has this site learned about X”),
relate_concept (a concept and the content, tags, and sibling concepts around
it), concepts_for (reverse lookup from any page or tag), and
suggest_concept_growth — which ranks what to write next by finding the big
content clusters that don’t have a concept yet. The durable layer isn’t just
stored; it steers what gets built.