Rendered from docs/obligations/0015-imported-edge-staleness-is-unmeasured-against-scaffolded-edges.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

Imported edge staleness is unmeasured against scaffolded edges

Context

Q19 rules how an external system of record feeds a corpus. Imported edges should not decay faster than scaffolded ones.

Obligation

Staleness by created_by in taxonomy audit is the instrument.

Discharge

No importer has run against this corpus, so every edge here carries an author rather than an importer, and the comparison has one side.

An importer now exists and neither half of the instrument does. headwater import ships and its refusals carry a fixture set, which is what Q19's other claim rests on. Two things stand between that and this record. taxonomy audit is not a verb of this engine, so nothing reports staleness by creator at all. And this repository declares no relation with created_by: import, so a run of the verb here would have nothing to write. Both are what the first adopter supplies, and the second is a taxonomy choice rather than an engine gap.

The instrument runs now, and the population is still one-sided. headwater taxonomy audit ships, and staleness by created_by is one of its six readings. Over this repository at --now 2026-08-14 it reports 397 edge halves under 9 relations, and 0 of them past the 180-day window the freshness facet declares. The reading walks the closed set of six creators rather than the values in use. So the report names import and states that no relation declares it. That is the arm that is missing, and this record is why the report says so rather than printing a zero.

The paragraph above named two gaps and one of them is closed. What remains is the relation: a corpus that declares one with created_by: import, and an import against it, supplies the second side. Nothing in this repository can supply it, and no further engine work is between the claim and its reading.