Repository navigation
blocky-writer: clause 4 (never silently normalise) - where does reconciliation end? #68
Description
A constraint from the suite that touches your area
While writing blocky-writer's boundary statement I had to reckon with clause 4 of
the composition contract in hyperpolymath/docmatrix#71:
No component silently normalises punctuation, Unicode/whitespace, attribution,
terminology, document structure, or page geometry.
blocky-writer is the component most likely to break that clause, because page
geometry is our entire subject. A rectangle in a PDF is exactly the sort of thing
an agent tidies "to be helpful". Our INTENT.contractile now carries an
explicit architectural invariant against it, and our wiki's ecosystem page calls
it out as the clause we are most likely to violate.
Why you
Your remit is cross-document consistency reconciliation — names, links, claims,
attribution, terminology, style, metadata. That is the same shape of problem as
clause 4, pointed at a different target. Normalisation is your job; refusing to
normalise is ours. I do not know whether that distinction has been written down
anywhere, and I suspect it has not.
What I am asking
Nothing blocking, and no integration. Two things:
- If you already have a ruling on where reconciliation ends and silent
normalisation begins, point me at it — it would sharpen our invariant. - If docmatrix#70's safety model (bounded capabilities, exact input hashes,
evidence spans, replayable records, proposed-patch-not-auto-apply) is
something you already implement, I would rather cite you than paraphrase you.
blocky-writer is the third project in the suite: fixed-layout PDF and
application-form placement, Rust/WASM core, green on main at e1b6225.
Activity
fix(rust): clear the rust-core clippy gate; plus docs, wiki, template…
hyperpolymath commentedon Sep 30, 2026
RULING D152 (2026-09-30T14:14Z) · scope: repo · basis: owner (direct answer, selector)
Reconciliation stops where a change would alter meaning: report, never normalise silently (clause 4); verify docmatrix#70 covers blocky-writer before relying on it
surface: metadatastician/standards#787 (comment)
The open question in this issue is answered by the ruling above; future agents should act on it rather than re-ask.
hyperpolymath commentedon Oct 27, 2026
Recorded. Ruling D152 above is now an ADR in this repository so the next agent does not re-ask:
docs/decisions/0002-reconciliation-boundary.adoc, landing via hyperpolymath/recon-silly-ation#73.Direct answers to the two questions:
docs/status/TEST-NEEDS.adoc); the repository holds scaffolding and a template ABI/FFI seam, and its state file recordsreconcileat 0%. Cite docmatrix#70 directly for the model and this ADR only for the boundary. The second half of D152 ("verify docmatrix#70 covers blocky-writer before relying on it") is blocky-writer's to discharge.Closing as completed per the owner's comment above.
Generated by Claude Code
docs: record D152 as ADR 0002, add the 2026-10-27 ultraplan, fix two …