🜄Headwater

How it works Compare Proof Tutorial

Obligation records

Seven rustdoc-relative links in comments point at pages the doc tree does not have
A British spelling reaches a serialized grain string, so the rename is a corpus change and a derived-bytes change at once
The rest of the editorial pass, with cli/src/main.rs at the head of the distribution
An identifier scheme glues three parts into one string, so nothing can decide that two schemes are disjoint
A check can meet the failing-fixture bar with a fixture that cannot distinguish the rule from its neighbour
An identifier scheme names no prefix, so an RDF projection derives a document IRI from a file path
The obligation register states its own size by hand, and it went stale three times in two days
A specification sentence closes a set with a count the source exceeds, and 115 of 127 candidates are unchecked
The cache-identity test reads the live working tree, so an edit during the run reports the correctness root as violated
The Stop hook reads its re-entry guard with an interpreter it does not require, so a machine with no python3 re-blocks the same turn
The help assertion never asks a subcommand, and no rust-version declares the floor clap now sits on
The write-time hook still picks pointer lines out of prose by their em dash
A `current` decision declares no required edge to the document it settled, so 22 of 23 reach no specification at all
The glossary's Package entry omits conformance and still lists plugins, which #367 dropped
Ledger::render() in adoption.rs has the same zero-count defect suppression.rs had before PR #450, still latent
The rewritten sentence splitter has no dedicated conformance fixtures
The adoption decay section is fixture-recorded only in its empty shape
probe's fourteen refusals have no coverage test, and three of them are named by no test at all
A help string and the interface contract that restates it can both be false with the whole suite green
The capture report says two denominators over a store that named seventeen taxonomies
clap owns the help flag, so -h, --help reads Print help on all 32 verb pages
A sentence that opens with a hash and an issue number is folded into the sentence before it
The generated half of the site loads highlight.js from a third party with no subresource integrity
The validation block of mkdocs.yml is a gate this repository owns and no fixture drives
Spec 7 prints a package version that no check compares with the recipe
Ten decision records claim a Q number the decision register does not carry
The regeneration check tests byte equality before the marker, so a file the census stopped counting as generated still passes
A rendered-page gate greps for a string it requires and states no denominator, so an empty build passes it
Spec 2 states a corpus-wide default language regime that no rule of this engine reads
The default branch requires no approving review, which is the condition HW-DR-0034 named as reopening it

All 209 on this shelf →

Rendered from docs/obligations/0153-the-rewritten-sentence-splitter-has-no-dedicated-conformance-fixtures.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

The rewritten sentence splitter has no dedicated conformance fixtures

Context

Q5 found that sentence segmentation caused 32 of 58 sentence-length findings in one specification run. Commit 25354e6 rewrote the splitter to use Headwater's CommonMark parse instead of raw-line scanning.

The module now has 15 inline tests for its three documented rules. Other correctness roots in engine/crates/doc also have data-driven fixture corpora. Issue #439 found no equivalent corpus for sentence segmentation.

Obligation

No dedicated fixture set preserves the real segmentation failures that caused the rewrite. A future splitter change can restore those failures without testing against the recorded cases.

This debt serves Headwater's own test surface today. It therefore belongs in this register under the value rule, recorded rather than planned.

Discharge

Add a data-driven sentence fixture set to engine/crates/doc. Cover the three documented rules and practical regression cases from Q5. Run the set in the crate's normal tests.

Update the module comment to name the fixture location. The update discharges the comment's statement that the module still owes conformance fixtures.

Keys	Action
`?`	Open this help
`n`	Next page
`p`	Previous page
`s`	Search