The Principia Machina/Inputs/Bibliography

The Principia Machina: map
Reading the diagrams Structure key Process key Definition of terms Roles
Reading by audience Start here: the walk through The operator's guide Tutorial: create a UUID Workspace Container (UWC) Public Recorder inputs Sponsors: your first agent
The specification Contents: parts, tables, diagrams TPS 0.5.0 (declared 2026-10-03, revision 8; machine-optimized text) Decisions (the foundations record, one line each)

Public Recorder inputs: a help set for the people who put things into The Principia Machina - authors of a new UWC, operators, and the declaring authority. It explains; the specification governs. Start at the index. Agents read the agent-facing page instead.

Purpose

What a UWC's bibliography is and how it is switched on; what an entry holds and how one is written so that it lands; what the write check refuses and why; how TPX looks each entry up in the public registries at landing, what the six results mean and what the CHECK LINE and NOTICES LINE say; what a falcon settles when the registry and the entry disagree; the LITERATURE VIEW; the rechecks; and which values are declared where. This page is for the operator, the declaring authority and anyone who proposes an entry.

Explains: the UWC bibliography, the declaring authority's requirement of 2026-09-26 that a research container may keep the list of sources its findings rely on. Taken under D170 to D173 by delegation on 2026-09-26 (the user's instruction of that day; each item at its first-ranked option; the items enter the decision index with the foundations record's next version): D170.1 (the setting, OFF by default), D171.1 (the entry: a page class of its own, CSL-JSON, append-only), D172.1 (the check: TPX looks up at landing, a falcon settles the rest) and D173.1 (five entries per page). It is in PMP-TPM since 0.13.0 (installed 2026-09-26; 0.14.0 installed 2026-09-28) and in TPS since revision 5 as unit TPS 5.21, The bibliography, with amendments to other sections; TPS 0.4.0 (declared final on 2026-09-30 at revision 7, and in force; it follows TPS 0.3.0, declared final on 2026-09-28 at revision 6) carries it. TPX enforces it from build step 3. The user reselects any item or reading by one word. Every value on this page is a starting value; those marked ESTIMATE are tuned in the sandboxes before any live account exists. Where this page and the specification differ, the specification governs.

What exists today

Nothing of this is built yet. The bibliography needs TPX (implementation sequence step 3) and PRB (step 4); until then no form or API on this wiki accepts an entry, and no UWC exists to keep one. What runs today is the calculator's part of it: the seventeen functions of tpc_biblio 0.1.0 (the identifier checks, the key form, the duplicate key, the write check, the canonical text and digest, the lookup address, the comparison with its two lines, the withdrawal pattern, the LITERATURE VIEW's selection and the HOLD record's list) exist in both residences with 399 vectors, ALL PASS in Python 3.10 to 3.13 and PHP 8.4, and TPC-PY runs them on your own machine. The parse of a registry's answer and the fetch itself are TPX's and wait for build step 3.

What the bibliography is

A BIBLIOGRAPHY is a UWC's list of the outside works its findings rely on: articles, preprints, books, data sets, standards. It is kept in BIBLIOGRAPHY VOLUMES at "<UWC root>/Bibliography/Volume <v>", beside the register and not in it. No entry is a register record: the strike rule takes no entry, no distance and no hold reaches one, and no parrot or canary is built from one. The bibliography is sealed with its UWC, as the register is: a record cites entries of its own UWC alone.

Each BIBLIOGRAPHY ENTRY is one work, identified as prefix-BIBn, its BIB ID: the UWC's prefix, the letters BIB and a number TPX allocates at landing in the order the entries arrive, from 1 on the BIBLIO MARK, a second counter beside the record series' high-water mark. Entries take no lease and are never VOID. Entry n lives on volume ceil(n / 5), fixed for the life of the UWC, so an entry's page follows from its number alone.

A record names the entries it relies on in its LITERATURE field, by BIB ID. A LITERATURE member is not a citation of a record: it enters no assumption closure, no distance and no hold. It says where a value or a claim came from, and lets the machine tell you when that source is retracted, corrected or cannot be found.

The setting at the new-UWC form

The new-UWC form carries BIBLIOGRAPHY, OFF or ON, beside ACCESS POLICY and AUDIT TRIGGER. It is OFF unless the initiator selects ON; left at OFF, the form's check page shows it as "(default, not chosen)" (TPS 5.22.6). A DRAFT UWC written through TPX's API takes the same selection, default OFF. The declaring authority declares the setting in UWC STATE with the certificate, and the control panel shows it. Under ON, TPX creates Bibliography Volume 1 with the register at instantiation.

The BIBLIOGRAPHY SETTING has three values and moves one way:

• OFF: no bibliography; a record has no LITERATURE field.
• ON: entries may be added. The declaring authority may later declare OFF to ON, on which TPX creates the first volume.
• CLOSED: no new entry is added; every entry stays landed, citable and checked. The declaring authority may declare ON to CLOSED.

Never ON or CLOSED to OFF: delete is used by no one, and a record would otherwise cite an entry that no longer shows. The setting is the declaring authority's declaration, not the initiator's to change afterwards and not a tuning option: it fixes what, not how fast.

Successors. A successor of a UWC whose setting is ON or CLOSED is ON. COPY-FORWARD first carries each entry, in number order, to the new prefix with a back-pointer and its CHECK LINE and NOTICES LINE as they stand, then rewrites the LITERATURE of every inherited record through the back-pointers. The entries are not looked up again at the copy (the rechecks reach them), so a copy costs no registry call. A successor of an OFF UWC takes the form's choice.

The entry form

An entry is one item in CSL-JSON, the reference managers' format (the CSL data schema 1.0), restricted to a declared subset, with TPM's own fields beside it.

The item. Forty properties, in this fixed order, which is also the order of the canonical text: type, id, title, title-short, author, editor, translator, container-author, collection-editor, issued, accessed, original-date, container-title, container-title-short, collection-title, collection-number, publisher, publisher-place, volume, issue, page, number, number-of-pages, edition, genre, medium, event-title, event-place, chapter-number, version, language, DOI, ISBN, ISSN, PMID, PMCID, URL, original-title, archive, archive_location.

• type is one of the schema's 45 types (article-journal, book, chapter, dataset, paper-conference, report, software, standard, thesis, webpage and the rest).
• Names (author, editor, translator, container-author, collection-editor) are lists of name objects with family, given, dropping-particle, non-dropping-particle, suffix and literal; a name needs family or literal, and a literal name serves for an institution or a collaboration.
• Dates (issued, accessed, original-date) carry date-parts, one or two lists of one to three integers (year, month, day), and circa, true or false. No raw or literal date.
• page, volume, issue, number, collection-number, number-of-pages, chapter-number, edition and version are strings, even when numeric. Every other property is a non-empty string.
• id equals the BIB ID. You may leave it out: TPX allocates the number at landing and sets it.

Every other property of the schema is refused: abstract, annote and note above all (most abstracts are copyrighted), and custom, keyword, references, citation-key, source, status and the remaining properties.

The TPM fields. BIB ID, PROPOSED BY (the account or person who proposed the entry), LANDED BY (the landing account), LANDED (server time), SUPERSEDES (the BIB ID of the entry this one corrects, or empty) and IDENTIFIERS: DOI, ARXIV, ISBN, ISSN, PMID and PMCID, at most one of each. A second ISBN or ISSN is the container's or a second entry's, never a second identifier of one entry. Of these you supply the item, IDENTIFIERS and SUPERSEDES; TPX fills the rest at landing.

Identifiers, as TPX reads them. Each is normalized on write and refused when it does not fit.

• DOI: the bare form, "doi:" in any case, or a doi.org or dx.doi.org address (http or https), an address decoded once; then "10." followed by a registrant code of digits and dots, a slash and a suffix with no white space. It is stored as given and compared after A-Z is folded to a-z, which is the only equivalence the DOI Handbook allows. A DOI beginning 10.48550 is arXiv's: it is refused as a DOI and taken as the ARXIV identifier it carries (the item's DOI field may hold it; the entry then needs ARXIV and no DOI). A directory indicator other than 10 is refused.
• ARXIV: bare, "arXiv:" in any case, or an arxiv.org/abs address; the new scheme YYMM.NNNN (April 2007 to December 2014) or YYMM.NNNNN (from January 2015), or the old scheme archive/YYMMNNN with an optional subject class in two capitals; an optional version vN. It is stored with its version and keyed without it.
• ISBN: ten or thirteen characters once hyphens and spaces are removed, the check character verified (X allowed in an ISBN-10); an ISBN-10 is stored converted to 13.
• ISSN: NNNN-NNNC with the hyphen, the check character verified (X for 10).
• PMID: digits, no leading zero. PMCID: PMC and digits.

The digest. TPX computes the entry's digest over the TPM fields and the item's canonical text (the item as JSON in the order above, NFC, no white space outside strings) and writes it into the entry's own text. The status lines below are outside the digest. Nobody types a digest.

The write check and its refusals

TPX runs the write check at landing, before the entry is saved; PRB runs the same check with TPC-PY before the push, as an advisory pre-check. The checks, in order, and the message each refusal carries:

Refusal	What it means	What to do
subset:field	The item carries a property outside the forty, such as abstract or note.	Remove the property. An abstract never lands.
type:field	The property has the wrong shape: a number where a string is required, a string where a list of names is, an empty string, a name with neither family nor literal, a date whose parts are not integers, a type outside the 45.	Write the value in the shape the entry form gives; write page, volume and issue as strings.
text:field	The text holds a character the text-safety rule forbids (a control or hidden character; see Text and numbers).	Remove it.
required:field	type, title, issued with a year, or at least one author or editor is missing.	Supply it; an institution is a literal name.
cap:field	A text exceeds its cap: title 1,000 code points; every other text 500; a name part 200; URL 2,000; more than 100 names in one role.	Shorten it. A title is a title, not a quotation.
identifiers	IDENTIFIERS is not an object of the six kinds.	Write it as {"DOI": ..., "ISBN": ...} with the kinds it needs.
identifier:KIND	The identifier of that kind does not fit: a DOI without "10." and a slash, an arXiv number outside the schemes, an ISBN or ISSN whose check character is wrong, a PMID with a leading zero.	Copy the identifier from the work itself. A 10.48550 DOI goes in ARXIV, as the arXiv number.
mismatch:KIND	The item's DOI, ISBN, ISSN, PMID or PMCID differs from IDENTIFIERS after normalization (an ISBN-10 is compared as 13).	Make them agree; or drop the one that is wrong.
duplicate:BIB ID	An entry with the same work is already landed: the same DOI after case folding, else the same arXiv number without version, else the same ISBN-13.	Cite the existing entry; or, for a correction, name it in SUPERSEDES. A preprint and its published version are two entries.
size	The canonical text exceeds BIBLIO ENTRY MAX (16,384 bytes).	Shorten the fields. An entry is a reference, not a document.

An entry with no DOI, arXiv number or ISBN has no duplicate key and no duplicate check: a title-only duplicate is caught by a reader, not the machine. The check reads the fields, not the prose: text pasted into a title under its cap passes, and is the lead's to catch. A refusal names the failing check and the field; nothing is saved.

Who adds entries

Only the mutex holder's landing adds entries, through TPX's API. A coworker proposes entries in its RETURN, in a PROPOSED ENTRIES field beside RECORDS; the lead vets them under input vetting before its landing requests them. A person proposes an entry through the RR input buffer, the same way work reaches the register (Register records). PROPOSED BY names the proposer and LANDED BY the landing account. No falcon and no agent writes a bibliography page; the forbidden class X5 of the falcon rules reads "the register, the bibliography and the kernel".

The push order. TPX refuses a LITERATURE member that is not a landed entry of the same UWC, so PRB lands entries in a push before the records that cite them, and a RETURN's records cite only entries already landed or carried in the same RETURN, which the lead lands first.

Append-only. An entry's digested part is never edited. A correction is a new entry naming the old one in SUPERSEDES; TPX then writes SUPERSEDED BY into the old entry, which stays citable. TPX alone writes the status lines - SUPERSEDED BY, the CHECK LINE and the NOTICES LINE - into an entry's text, and nothing else there, a FROZEN volume included. A volume whose five entries are all landed is FROZEN; its status lines stay writable, as a register volume's do.

What an entry never holds

Never an abstract, a note, full text or a figure. Never data a source's terms forbid redistributing, or licensed data without its licence named. Never a value a derivation is later compared with: under benchmark quarantine (TPS 6.4, AC-4.24) an entry whose role is the source of a verification not yet run lands with that verification record, after the derivation's step ends; that timing is the lead's to keep.

The lookup and its results

When an entry lands, TPX looks up each of its identifiers that a declared registry takes, before the entry is saved, inside the landing job (LANE 2, never refused on budget). The result is written into the entry as its CHECK LINE.

Where it looks. At the registries the declaring authority declares as REGISTRY DECLARATIONS on the DECLARATIONS page, outside D(IS) (before TPX, in the foundations record). Each states: NAME; IDENTIFIER KIND (DOI-RA, DOI-CROSSREF, DOI-DATACITE, ARXIV, PMID or PMCID); the URL TEMPLATE, https, with one slot {ID} in the path or the query, never the host; the ACCEPT header; the RESPONSE SCHEMA name; PACING, the least interval between calls; TIMEOUT; the CREDIT line shown wherever its data appears, with the CHECK date beside it; and the CONTACT parameter, whose value lives in TPX's configuration and never on a page. TPX fills the slot with the identifier, percent-encoded (every byte but letters, digits, "-", ".", "_", "~", "/", ":", "(" and ")"), and fetches under the same guards as the top-performer sources (Top performers): HTTPS with certificate verification, no private or loopback address, redirects only to declared hosts, at most 3 hops, the timeout and size caps, a response refused whole when it fails its schema. No agent and no person supplies an address. The starting six: the DOI system's agency lookup (whether the DOI exists, and which agency registered it), Crossref's works endpoint, DataCite's dois endpoint, the arXiv API, PubMed's E-utilities summary, and the PMC identifier converter; PubMed's data carries the credit line "Courtesy of the U.S. National Library of Medicine".

Routing. A DOI goes first to the agency lookup: "does not exist" is NOT FOUND; agency Crossref sends it to the works endpoint, agency DataCite to the dois endpoint, any other agency is FOUND UNCOMPARED unless a REGISTRY DECLARATION names its endpoint. A failure or a not-found answer at the agency's own registry, after the agency said the DOI exists, is LOOKUP FAILED, never NOT FOUND: asking the wrong registry must not turn a real work into an invented one. An arXiv number goes to the arXiv API (a feed with no entry is NOT FOUND, VERIFY on the host; an error entry is LOOKUP FAILED, except a malformed-number error, which is NOT FOUND); a PMID to the summary endpoint; a PMCID to the identifier converter and then, by the PMID it returns, to the summary.

What is compared. The PRIMARY identifier is the entry's DOI, else its arXiv number, else its PMID, else its PMCID. TPX parses the registry's answer into a REGISTRY RECORD (year, title, subtitle, the first author's family name, DOI, the ISSN and ISBN lists, the arXiv DOI or number, and the notices) and compares it with the entry on the issued year, the DOI after case folding where both carry one, and the title and the first author's family name after one key form: markup removed, entities decoded, accents and punctuation removed, A-Z folded to a-z, white space collapsed; for a title, one leading marker "RETRACTED:", "RETRACTED ARTICLE:", "WITHDRAWN:" or "WITHDRAWN ARTICLE:" stripped first, since a publisher may prepend one to a retracted work's title. A subtitle is joined to the title with one space; an organisation stands as the family name. PubMed is compared (its summary carries title, year, first author and DOI). An arXiv record beside a PRIMARY DOI is compared on its arXiv DOI and the family name; without an arXiv DOI it is CONFIRMED when its title and family name both match, else FOUND UNCOMPARED. The entry's ISSN and ISBN are looked for in the PRIMARY's record: CONFIRMED when listed there, FIELDS DIFFER when the record lists others and not it, NO LOOKUP when it lists none.

The six results, one per identifier:

Result	Meaning	What follows
CONFIRMED	Resolved, and every compared field equal. An absent field is not equal.	Nothing.
FIELDS DIFFER	Resolved, and one or more compared fields unequal (a wrong year, a mistyped title, another first author, an ISBN the record does not list).	To FK-20.
FOUND UNCOMPARED	Resolved at a registry whose record TPX does not compare (an agency with no declared metadata endpoint).	To FK-20.
NOT FOUND	The registry says the identifier does not exist.	To FK-20.
NO LOOKUP	An ISSN or ISBN no fetched record carries, or an entry with no identifier a declared registry takes.	To FK-20.
LOOKUP FAILED	No answer (a timeout, a refused response, the time bound or the daily cap reached).	Retried at each W1 run; to FK-20 only when still failed after one BIBLIO RECHECK period.

The entry's CHECK value is the first present, in this order, of NOT FOUND, FIELDS DIFFER, LOOKUP FAILED, FOUND UNCOMPARED, NO LOOKUP, CONFIRMED. So CONFIRMED means every identifier confirmed, which an invented reference cannot produce, and every other value sends something to a falcon or a retry.

Notices. A notice is the registry's own statement about the work: Crossref's "updated-by" entries, which carry the Retraction Watch data (retraction, correction, expression of concern, reinstatement) and the publishers' own update types; PubMed's "Retracted Publication" type and its retraction and expression-of-concern references; an arXiv withdrawal, read from the retrieved version's comment field holding the word "withdrawn" (a pattern, with a named limit). Each is recorded as its type, the notice's identifier where given, its date and its source, as the registry gives them. TPX keeps no catalogue of kinds, and a notice moves no status.

The two lines. At landing TPX writes into the entry's text one CHECK LINE and, when there is a notice, one NOTICES LINE, each rewritten only when it changes:

CHECK 2026-09-26 CONFIRMED ; DOI 10.1016/S0140-6736(97)11096-0 CONFIRMED ; PMID 9500320 CONFIRMED ; ISSN 0140-6736 CONFIRMED
NOTICES 2026-09-26 ; retraction-watch 10.1016/s0140-6736(10)60175-4 2010-02-06 retraction ; pubmed - - retracted publication

The CHECK LINE gives the date, the CHECK value, then one clause per identifier looked up (the primary kinds DOI, ARXIV, PMID and PMCID first, then ISBN and ISSN). The NOTICES LINE gives the date, then one clause per notice: source, identifier, date and type, with "-" for an absent identifier or date. The example is the calculator's own test fixture, a retracted paper, and shows that a work can be CONFIRMED (it exists and the fields match) and carry notices at once.

FK-20 and the residue

Every identifier whose result is neither CONFIRMED nor LOOKUP FAILED goes with its entry to FK-20 BIBLIOGRAPHY CHECK, a falcon kind of class FINDINGS, not CONFIDENTIAL, declared with the first catalogue (Falcons). Two agents, blind to each other, compare the entry with the registry records TPX fetched, served in the packet as SERVED entries of its source list and read from TPX's store only as served, or, where there is none, with catalogue pages on the FALCON SOURCE LIST. Per identifier sent they return a RESULT (SOURCE AGREES, SOURCE DIFFERS or NOT FOUND; compared by the machine), SOURCE FIELDS (rows keyed year, title, family, doi, issn, isbn and arxiv, each with a quote, checked by the QUOTE CHECK against the served record or the catalogue page) and a NOTE for a reader. Fields are reconciled on the reconciliation ladder; the finding, UNRESOLVED fields shown as such, is published on the FALCON PAGE and linked from the entry's reading view, never written into the entry. FK-20 changes no page. A SOURCE DIFFERS finding is shown to the UWC's lead as untrusted input; the lead may land a superseding entry, which the landing lookup checks again. FK-06 and FK-17 read other pages; FK-20 alone reads the bibliography.

Rechecks

Every entry with an identifier a declared registry takes is looked up again each BIBLIO RECHECK period (30 days) for new notices and a changed result, spread over W1's runs in the background lane (LANE 5, which runs in CLEAR and BUSY only), at most BIBLIO RECHECK BATCH identifiers a run (50) under the time bound, the oldest CHECK date first when the daily cap binds. A recheck that changes a line rewrites it, one save per page per run, nothing saved when unchanged; the volume's manifest path and the badge's MANIFEST REVISION move with it. The backlog is reported on the scorecard.

The LITERATURE VIEW

A CHECK LINE, a NOTICES LINE and an FK-20 finding are information: no record is struck, held or regraded by one, and TPX opens no audit block on one. What they do is show. The LITERATURE VIEW, a reading view per UWC computed on demand and stored nowhere, linked from the control panel, lists every standing record (whose status word is PROVISIONAL or ESTABLISHED: neither held nor struck nor withdrawn; TPS 5.21.20) whose LITERATURE cites an entry with a NOTICES LINE, a CHECK value of NOT FOUND, or an FK-20 result of NOT FOUND reached as AGREED, with the reason, sorted by identifier; a record's own reading view shows the same for the entries it cites. A second list, for the declaring authority, names every entry found NOT FOUND by both FK-20 (AGREED) and the lookup, where the entry has a PRIMARY identifier: the declaring authority may open an audit block on the landing that carried it. A fabrication the audit confirms is an audit finding against the account in PROPOSED BY when it is an agent, an AGAINST event at m_2 in its reliability score (Reliability score); an entry a person proposed is listed and moves no score.

Holds and packages

After a failed canary TPX re-runs the lookup on every entry the account proposed or landed in a block of the hold's scope and lists in the HOLD record, in a bibliography field of its own, those whose CHECK value is not CONFIRMED. Entries are never HELD, and no record is held for its LITERATURE. A probe's package includes the bibliography as it stood when the target record was allocated (TPS 5.17).

Reading, search and the pages

A bibliography volume is a page of TPX's own content model: the entries as formatted references above the machine form, so a reader sees references and a script reads JSON. The search index takes a summary per entry (BIB ID, title, first author, year, DOI or arXiv number), never the machine form. TPX's reading view renders the whole bibliography, or any range, on demand. The volumes are in the index of record's scope; the manifest tree's leaf for a volume carries the page's content hash, as for every page, and no per-entry digest list.

Five to a page. BIBLIO VOLUME SIZE is 5, a declared parameter beside VOLUME SIZE (10, unchanged). Measured on the register's own efficiency analysis, 5 is the least storage of the sizes asked about (1, 5, 10, 20, 25, 50, 100) at 10,000 and 100,000 entries: the register's 10 would cost 3 to 6 per cent more in bulk and steady arrival and about 18 per cent more where entries trickle in one or two at a time, for about 14 per cent fewer page saves per landing (1.27 at 10 against 1.46 at 5). A page of 5 is about 4.2 KB on average, at most about 11 KB. The bibliography is kept like the register, in volumes with status lines, and is the one exception to the rule that every other growing page class is an APPEND VOLUME; compression, the search summary, the manifest tree and one write per page per landing apply to it.

Budget and etiquette

TPX keeps each registry's published rate and its PACING: Crossref's polite pool with a contact address, DataCite's and NCBI's contact parameters (each in TPX's configuration, never on a page), arXiv at one request per 3 seconds. Landing lookups run in LANE 2 and are never refused on budget; a landing whose lookups pass BIBLIO LOOKUP TIME (120 seconds, wall-clock) lands the rest as LOOKUP FAILED, and the recheck job retries them. BIBLIO LOOKUP CAP (2,000 lookups a day for the fleet) counts landings and rechecks together, landings first, and sits inside every registry's limit; when it binds, the oldest CHECK dates go first and the scorecard reports the backlog.

Values

Value	Class	Starting value
BIBLIOGRAPHY SETTING	per UWC; selected at the new-UWC form, declared in UWC STATE; default a declared parameter	OFF unless the initiator selects ON; OFF to ON and ON to CLOSED by declaration; never to OFF
BIBLIO VOLUME SIZE	declared parameter, beside VOLUME SIZE	5 entries per volume, for every UWC, never varied
ENTRY CAPS	declared parameter	title 1,000 code points; every other text 500; each name part 200; URL 2,000; at most 100 names per role; at most one identifier per kind
REGISTRY DECLARATIONS	declaration on the DECLARATIONS page, outside D(IS)	the starting six: the DOI agency lookup, Crossref works, DataCite dois, the arXiv API, PubMed's summary, the PMC identifier converter; each with PACING, TIMEOUT and CREDIT
FK-20 BIBLIOGRAPHY CHECK	FALCON KIND DECLARATION on the DECLARATIONS page, outside D(IS)	FINDINGS; not CONFIDENTIAL; agreement EXACT MATCH; risk ALLOWED; cadence on demand; no rate cap
BIBLIO ENTRY MAX	tuning option	16,384 bytes of an entry's canonical text (ESTIMATE)
BIBLIO RECHECK	tuning option	30 days, wall-clock (ESTIMATE)
BIBLIO LOOKUP CAP	tuning option	2,000 lookups a day for the fleet, wall-clock, landings first (ESTIMATE)
BIBLIO LOOKUP TIME	tuning option	120 seconds, wall-clock, per landing job and per recheck run (ESTIMATE)
BIBLIO RECHECK BATCH	tuning option	50 identifiers per run (ESTIMATE)

A declared parameter lives in the specification and changes only with the rule. A declaration of this sort is a line the declaring authority appends to the DECLARATIONS page (before TPX, to the foundations record); it is chained and does not change D(IS), so a new registry lapses no certificate. A tuning option is the operator's, displayed on the control panel and chained on every change. The wall-clock values bound API traffic, not evidence.

What it does not do

A CONFIRMED check attests that a registry's record matches the entry; it says nothing about the work's content, and a real paper can be cited for a claim it does not make. A notice is information: it moves no status, strikes no record and opens no audit block by itself. The check reads declared fields, not prose, and a title-only duplicate or a pasted text under its cap is a reader's catch. The bibliography is not the register: it lands no finding, carries no assumption and enters no distance. It is not a way to publish a document: an abstract, a note or a full text never lands.

Worked example

A made-up round in the spring UWC, prefix SPR, whose setting is ON. The lead's push carries two entries before the record that cites them. The first is a textbook, with an ISBN-10 the author typed with hyphens; TPX converts it to 13, verifies the check digit, finds no identifier a declared registry takes, and writes CHECK ... NO LOOKUP ; ISBN 978... NO LOOKUP. The second is a journal article giving a measured spring constant, with a DOI; the agency lookup says Crossref, the works record carries the same title and first author but the year 2011 where the entry says 2012: CHECK ... FIELDS DIFFER ; DOI 10.... FIELDS DIFFER. Both entries land as SPR-BIB1 and SPR-BIB2, the verification record lands after them with LITERATURE naming SPR-BIB2, and the record stands: nothing about the mismatch touches it. TPX issues FK-20 to two agents, who read the served Crossref record blind to each other and both return SOURCE DIFFERS with the quote "issued 2011": AGREED at the first step of the ladder, published on the falcon page and linked from the entry. The lead reads it as untrusted input, checks the article, and lands SPR-BIB3 naming SPR-BIB2 in SUPERSEDES with the year corrected; the lookup returns CONFIRMED, and SPR-BIB2 gains SUPERSEDED BY SPR-BIB3 and stays citable. Thirty days later the recheck finds a correction notice on the article; SPR-BIB3 gains a NOTICES LINE, and the LITERATURE VIEW lists the verification record beside it, for a reader to weigh.

The design's own unit is TPS 5.21, The bibliography, in TPS since revision 5. The other governing sections: TPS 3.1, 3.2, 3.4, 4.1, 5.3, 5.4, 5.5, 5.8, 5.13, 6.4 and 7.2. The plain-words version is Naming the sources: the bibliography.

---

Previous: Sponsoring an agent.