“Worker V5.9.1 of the DEMI Registry fixes a failure mode where a Conceptual Core could be missing or misreported on a certificate, by adding AI-call reliability measures and a verified '/core-again' re-formation endpoint.”
PropositionsT1: AI Core call has a 50-second timeout, 4000-token limit, one retry on network error/429/5xx/529/invalid JSON, and pre-return validation | T2: '/core-again' endpoint accepts owner-pasted passage only if SHA-256 matches record's extract fingerprint, fills missing Core only, enforces 3 attempts/record/day, logs to core_changes, adds fingerprint to index and next Ethereum anchor, and gates publication on operator token for ETH-wallet payments | T3: Display layer shows 'Not formed yet' with re-formation link for failed Cores, labels operator as UplitAU and record originator as Publisher, flags early records as EARLY REGISTRATION, returns matched file hash from verify_fingerprint, and sets nosniff and referrer headers with optional rate limiting | T4: V5.9.1 fix corrects a broken page script in V5.9.0 that prevented '/core-again' from running in a browser; validated live on record UPL-TECH-26-667079-EN on 16 October 2026
ConstraintsRegistration flow, payment handling, Ethereum anchoring, index format and five MCP tools are unchanged from prior versions | 44 local tests must pass and output must be at parity with V5.8.8 | '/core-again' requires passage SHA-256 to equal the stored extract fingerprint | Existing Cores must never be overwritten | Attempt cap is 3 per record per day | ETH-wallet payment records require operator token before Core is published | V5.9.1 subsumes V5.9.0 changes
MechanismsT1: Inject a network error, a 429 and a 5xx response in turn and confirm single retry each; inject a non-JSON AI response and confirm retry; confirm rejection after two consecutive failures; measure response under 50-second cut-off with a 4000-token reply | T2: Submit correct and incorrect SHA-256 passages and confirm accept/reject; attempt Core re-formation on a record with an existing Core and confirm no change; submit 4 attempts in one day and confirm the fourth is blocked; check core_changes log after a successful fill; confirm fingerprint appears in index and Ethereum anchor queue; submit as ETH-wallet owner without operator token and confirm Core is withheld | T3: Load a record with missing Core and confirm 'Not formed yet' text and link render; inspect certificate of an early record for EARLY REGISTRATION label; call verify_fingerprint and confirm returned value is the matched file's hash; inspect HTTP headers for nosniff and referrer-policy values | T4: Load '/core-again' page in a real browser under V5.9.1 and confirm script executes; verify UPL-TECH-26-667079-EN now carries a published Core dated 16 October 2026
BoundariesOperator token scope is limited to UplitAU's own records (expansion out of scope) | Index storage in a database is not yet implemented | Deployment on a dedicated domain is not yet done | Owner-key verification for the Vault is not yet built | Certificate wording corrections beyond display-layer changes are not described | OPEN: when operator token scope will be extended; database index migration path; domain acquisition timeline; design of owner-key check for the Vault
Files fingerprinted by this registration
These files were fingerprinted by the registrant and were never uploaded. The registration time above applies to each fingerprint below: a fingerprint cannot be produced without the file it describes. This record does not establish authorship or ownership of the files named.