| Core Statement | 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. |
| Propositions | T1: 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 |
| Constraints | Registration 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 |
| Mechanisms | T1: 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 |
| Boundaries | Operator 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 |
| Registered file | Worker_demi_proxy_V5_9_1(1).js |
| File SHA-256 | 558e51a987899e4ddebf5a6d0abc52d3bcb1478710828735a9da0f797530d8af |
| Analysed extract SHA-256 | b8af4fd5dbbe73f34602bfa7dd918816cf349f03ba0921e96f90b8019da8eff5 |
| Payment | Ethereum · 0xfb40eee8d73c1426e98ec98fb4645d7b86403bcae2bdddf29f9621dfa7975f04 View on Etherscan → |
| Registered at (UTC) | 2026-10-16T23:08:19.167Z |
| Registry anchor (Ethereum) | block 26208290 · 2026-10-16T23:08:35.000Z · View on Etherscan → The Registry state containing this record was committed to the Ethereum blockchain -- an independent public timestamp, regardless of how the registration was paid. |
| Derived from | UPL-TECH-26-395542-EN |
| Activation Reference | DEMI:1042:UPL-TECH-26-243670-EN:4 |
How to verify: compute the SHA-256 of the original file with any standard tool — if it matches the File SHA-256 above, the file is byte-for-byte identical to the one registered. For Ethereum payments, the block timestamp of the transaction is an independent public timestamp of 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.
| 1. Worker_demi_proxy_V5_9_0(1).js 268314 bytes SHA-256: 3f69270fc340ffe89afb8139dda2efece756601a7d83c55dfa0fed0426f19368 |
https://www.demicapsule.com/registry/UPL-TECH-26-243670-EN/index.html
To continue this work with an AI assistant, tell it: Read https://www.demicapsule.com/registry/UPL-TECH-26-243670-EN/ai and help me with this work.
DEMI Publishing Registry · UplitAU Pty Ltd · ABN 91 680 646 495 · Sydney, Australia
AU2018100999 · AU2019101249 · © 2026 UplitAU Pty Ltd / Skydle
AI-Fetchable: ✓ · Machine-readable record embedded below · ramsmile.com
Certificate generated 2026-10-28T06:05:22.501Z · rebuilt each time it is opened; a saved copy shows the record as it stood at that moment