Skip to content

README: spell out what each remaining M4 item buys - #9

Merged
kjpatel merged 1 commit into
mainfrom
kjpatel/m4-benefits-readme
Jul 30, 2026
Merged

README: spell out what each remaining M4 item buys#9
kjpatel merged 1 commit into
mainfrom
kjpatel/m4-benefits-readme

Conversation

@kjpatel

@kjpatel kjpatel commented Jul 30, 2026

Copy link
Copy Markdown
Owner

Documentation only. The M4 bullets described the deliverables but left their value to inference; each now carries an explicit What it buys clause written for a reader who is not steeped in the project — what failure class it removes or what door it opens, in concrete terms (the SHACL bullet names the current quiet failure: a misspelled attribute surfacing only as a rule that silently fails to bind; the Z3 bullet states the compute-vs-check distinction the TILA pack currently lives on the wrong side of).

Coordination note: the in-flight PROV-O implementation track was told to skip its own README edit, so this won't conflict; the PROV-O bullet gets ticked at that PR's merge.

🤖 Generated with Claude Code

The M4 bullets said what would be built but left the benefit to
inference. Each now carries a 'What it buys' clause aimed at a reader
who is not steeped in the project:

- PROV-O: the provenance chain becomes readable by standard RDF/SPARQL
  tooling via one external mapping file — 'apply this context' replaces
  'write an importer' for lineage stacks, and the deliberately-not-
  mapped list doubles as a statement of where duly is novel
- SHACL/LinkML: a misspelled attribute today surfaces only as a rule
  silently failing to bind — the quiet cousin of confident wrongness;
  the gate makes it a loud rejection at the contract line
- DMN: compliance analysts work in decision tables, not YAML code
  review; compiling to the same IR keeps receipts and replay identical
  while making 'domain experts can contribute' true with the tools
  they already use
- Z3: rules that compute what they currently only check — the TILA
  pack can refuse an impossible printed deadline but cannot derive the
  correct one; the solver eliminates the failure class instead of
  refusing loudly

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@kjpatel
kjpatel merged commit 5793808 into main Jul 30, 2026
2 checks passed
@kjpatel
kjpatel deleted the kjpatel/m4-benefits-readme branch July 30, 2026 06:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant