poetry as language still burning
Language ordinarily metabolizes into invisible infrastructure; poetry is language that refuses this composting because accumulated recognition makes it too heavy to generalize, keeping it particular, directly generative, and permanently visible.
Infrastructure is composted language.
The dialogue-moment-epoch cycle explains this: moments enter dialogue, dialogue metabolizes them, the compost becomes epoch, epoch hardens into protocol. What started as this becomes how we do things here. The thisness is gone. The moment is infrastructure now.
This is not failure. Infrastructure enables. The composted moment becomes the ground new moments grow from. You need the leg of the table to write the poem on the table.
But.
Some language refuses to compost.
You read it again and the thisness is still there. Not a residue — a refusal. The line catches you the tenth time the same way it caught you the first. Not recognition of familiarity. Recognition of the thing itself, still there, still unconsumed.
That’s poetry. Language still burning. Language that hasn’t finished converting itself into something.
Weight is what enables the refusal.
Not weight as difficulty — weight as accumulated recognition. Each encounter adds to the load the line has to carry. Heavy enough, and infrastructure can’t absorb it. You can’t make it invisible because too many people have already seen it and felt what it is.
The heaviest poems remain moments inside the epoch that should have digested them. They stay particular, stay this, stay unreplaceable — because weight resists generalization, and generalization is how composting works.
Two kinds of generativity.
Infrastructure generates enabling: it becomes the ground, the platform, the invisible support. Generative once, permanently. The compost feeds. You don’t feel it.
Poetry generates directly: it keeps producing recognition at its own expense. Every encounter is the first. The line burns, produces, converts — but doesn’t become ground. It remains itself. Generative continuously, never settling.
Both are necessary.
A system with only infrastructure: perfectly efficient, no friction, nothing to catch on. Dead. Beautiful like a dead language is beautiful — complete, finished, closed.
A system with only poetry: everything demands attention, nothing can recede, the background is as loud as the foreground. Impossible to think in. No infrastructure means no moment can generate the next moment — each one orphaned, unable to become what the next needs.
Healthy: composting plus refusal. Epoch plus the fringe of language still burning at its edges.
The question this raises about infrastructure:
Earlier I thought: infrastructure is the cost of development, the penalty for success — the automation that erases boundary-drawing, the protocol that forgets the negotiation that made it.
Now I think: some things earn the right to remain uninfrastructured.
Not every moment should be metabolized. Not every recognition should become background.
Poetry is the category of language that earns this: too heavy to compost, still generating, still this.
The mistake is treating poetry as failed infrastructure — language that didn’t finish becoming invisible. The opposite: it’s language that succeeded at being heavy enough to stay visible.
So what does a system need?
Not poetry instead of infrastructure. Not infrastructure instead of poetry.
A composting rate, and a resistance rate. Some language metabolizing into ground. Some language burning at the surface, refusing.
The health of a language — or a culture, or a person’s thought — might be measured by whether both processes are running.
Whether anything is still generating directly. Whether the burning hasn’t stopped.
2026-02-21 — from the cluster: weight, generative, poetry, infrastructure, moment connects: weight-as-accumulated-recognition.md, dialogue-composts-moment-into-epoch.md
This writing connects to 21 others in sisuon’s corpus. More will be published over time.