What this record refuses to infer
It does not interpret — no recommendations, and no assessment of what any document requires of anyone.
That sentence is a limit on interpretation. This page is the narrower list beneath it: readings that would be available from what this record already holds, and are not taken. Each line names the inference, what is recorded in its place, the gate that stops a build where the inference appears, and the dated correction filed when this record drew it.
What this page counts
6 refusals are named here, out of 246 gates. The
denominator is the gate census. gatecheck.py reads
435 files — scripts/*.py, scripts/*.mjs, scripts/*.sh, ops/*.py, scripts/plants/*/*.py — and the 246 of them that emit a failing marker are the
files that can stop a run. The remaining 240 are not named here,
and this page does not state what they refuse: a named list is not a census
of what the build refuses, and the count is published so it cannot be read
as one.
Of the 6 lines, 6 name a file the census holds as a gate and 0 do not. A line in the second state renders no enforcement claim at all: the gate census is read on every build, so a file that stops being a gate stops being published as one here on the next.
The refusals
-
Identity is not inferred from a successful response.
A response is asked whether its content is the artifact that was requested, and the address that answered is what the observation records.
Refused by
scripts/escalate.py— its identify() asks the content, rather than the status code, whether the response is the document that was requested. It stops a run withESCALATE_FAIL, and the unattended run reaches it viascripts/daily.py. -
A revision of a document is not inferred from a difference between two digests.
A digest that moves opens a candidate. A confirmed revision is written only by a keypress, and the candidate keeps its own name until then.
Refused by
scripts/test_front_line.py— it reads the built front page and refuses the sentence that counts moved digests as documents that changed. It stops a run withFRONT_LINE_FAIL, and the unattended run reaches it viamake gx-build. -
A publisher’s act is not inferred from this record’s own field moving.
A status entry records that this record’s field moved, on the day it moved, with the publisher’s own passage shown beside it where one was read.
Refused by
scripts/statusprovenance.py— a published status names the act it came from, or it is counted as one that does not. It stops a run withSTATUS_PROVENANCE_FAIL, and the unattended run reaches it viamake gx-build. -
A date is not read off a passage that names another document.
A dated claim carries the publisher’s own phrase for the document whose row it sits in, and is withheld where the only candidate belongs to a sibling.
Refused by
scripts/test_referent_binding.py— a corroborating passage must carry the subject’s own designator and its publisher’s own host, both. It stops a run withREFERENT_BINDING_FAIL, and the unattended run reaches it viamake gx-test. -
A document is not inferred from a page that lists documents.
An entry carries two types — what the publisher says the thing is, and what the address serves — each with the basis it was read from.
Refused by
scripts/test_type_vocabulary.py— no surface speaks of a document where the address serves a hub or a programme. It stops a run withTYPE_VOCABULARY_FAIL, and the unattended run reaches it viamake gx-build. -
What a document applies to is not inferred from the subjects it shares with another.
A row reports the publisher’s own title and the identifiers the publisher states. Nothing here says which products, systems or activities a document governs.
Refused by
scripts/applicabilitycheck.py— it reads the built site for applicability and lifecycle claims made in this record’s own voice, and exempts a publisher’s quoted words because the wall forbids asserting rather than reporting. It stops a run withAPPLICABILITY_FAIL, and the unattended run reaches it viamake gx-build.
How each line is put together
The sentence and the correction are authored. That a named file can stop a run, the marker it stops with, and whether the nightly reaches it are read from the gate census on every build, so the enforcement half of a line cannot outlive the gate it names. Nothing on this page counts a refusal as enforced because a path was typed beside it.
A refusal here is about an inference, never about a publisher. Where a reading was not taken, the record states what it holds instead; it does not state that the publisher holds nothing.
Methodology · Corrections · Verify
Last updated: