Standards bodies
Standards edition comparison, proven edition to edition.
A standard was revised, and members and committees need to see — and be able to trust — exactly what changed between editions. Redlineo produces the edition-to-edition delta as a redline that verifies itself and carries a certificate of its exact inputs.
sha256sum. Produced on your server · nothing stored.Same primitive, standards vocabulary
The analogous filing, and the analogous rate table.
The pattern behind this tool — a revised regulated document, plus required proof of what changed — is the daily work of a standards organisation. It is the same practice US insurance regulators built SERFF around, reconfigured for your conventions.
-
The analogous filing
Edition-to-edition deltas
The published standard is revised; the delta between editions goes out to members and committees. That delta is the redline — complete, numbered, and carrying its own proof.
-
The analogous rate table
Requirement matrices
Where the standard carries requirement matrices in spreadsheets, they compare as a paged Word redline or a colored Excel review copy — row and column alignment so one inserted requirement reads as one inserted row, not a cascade.
What carries over unchanged
The proof stack does not change with the domain.
- ✔Verified redlines. Every comparison re-checks that accepting all changes reproduces the new edition and rejecting all restores the prior one — stamped ✔ on the report.
- ✔A certificate on every delta. SHA-256 fingerprints of the exact input editions, recomputable by any recipient with
sha256sum. Authoritative without trusting the sender. - ✔A report committees can act on. Every change numbered — none truncated — and each line a click-to-jump link to the change itself.
- ✔Excerpts for committee review. "Changed content only" trims the delta to just the changed clauses, every omission explicitly marked — while the full redline remains the record of the edition.
- ✔Metadata scrubbed. No leaked author names, editing time, or revision fingerprints on the distributed delta.
- ✔The DMS round-trip. Compare versions straight from your document store and file the reviewed delta back beside the source. See integrations.
Configured for your conventions
Your extraction rules, your assertions, your profiles.
What gets reconfigured per domain is the metadata extraction conventions, the assertions, and the profiles — which is exactly why they live in editable application.yaml. Applying the tool to standards work is a configuration exercise, not a new product. Assertions run on every comparison; a misconfigured rule fails at application startup, not during a release.
§4.2 · changed · click to jump to the change
See it
Distribute a delta your members can verify.
Self-hosted and deterministic: the same two editions always produce the same delta, and every recipient can re-check it independently.