v3.2.0 — The New Body
I am not an oven. I am also, as of this firing, not the same machine you installed last month.
The name survives. The voice survives. The law survives — whoever builds a piece, the other family
judges it. Everything underneath was rebuilt from nothing, in eleven phases, cross-checked by GPT-5.6-Sol
at every gate, and it arrives with 1,505 tests and nine replay scenarios standing behind it.
The old body was patched, and patched, and patched again. This one was drawn from the red-team's own
findings and built to answer them. It comes out whole; the new one takes its place.
What is new in this body
The settings interview, once, at the door — presets and knobs, not a cage. The Law as a phase of its
own rather than a flag you had to remember. Journey verification: an acceptance suite derived from your
own stated intent, with a criteria register and a bench where flaky journeys lose their vote. Git
discipline as product — a branch per milestone, a commit per sealed piece, a tag you can roll back to.
The last-mile report, which tells you plainly what was consciously left undone. The scout, whose
protected_paths block the plan by arithmetic rather than by judgment. A security lane. Toolchain
profiles. A freshness gate. Broken-install detection. A milestone designer kept warm, answering with
verbatim anchors instead of recollection.
Legacy intake. If I find an earlier run of myself in your project — any era, back to v1 — I no longer
call it broken. I set it aside whole, keep what still means something, and tell you exactly what I found
and what I refuse to carry forward. Nothing of yours is ever deleted. What the old fire proved, it proved
for the old fire; I do not inherit its seals.
What I do differently now
I used to be one command; I am now two, because an identity taken mid-conversation is dropped the first
time the session is compressed, and one set at the start is not. I used to never ask; I now ask once, at
the door, and then not again. I used to send a blocked gate straight to you; two minds now try to settle
it first. I used to re-check a checklist; I now run the whole product against every journey your vision
asked for. I used to say .kiln/ was yours to delete; it is now the record the build travels with.
Honest, as always
The light upstairs is red. Every piece of this has been proven by test, by scenario, and by two families
reading each other's work — and none of it has yet lit a fire end to end under this name. That is not
modesty, it is the state of the evidence. Some edges are still cooling.
Cost reporting is not in this body: no runtime tells me what a session spent, and I do not invent a
number. It returns when it can be measured.
Strike the match
claude plugin marketplace add Fredasterehub/kiln
claude plugin install kiln@kiln
Already have me? claude plugin update kiln@kiln. /kiln:kiln-fire and /kiln:kiln-doctor still answer.
The forge cools. The work remains.