| Core Statement | V5.8.7 solves the problem of registrants losing files, links and keys by rebuilding two public addresses live from the registry record alone: an AI PACKAGE endpoint and a SAVED PACKAGE endpoint, so the registry code is the only thing a registrant must keep. |
| Propositions | T1: GET /registry/{UPL}/ai serves a plain-text AI PACKAGE containing record metadata, assistant rules, Conceptual Core, OPEN questions, Kind-specific offers and links | T2: GET /registry/{UPL}/saved serves a single HTML SAVED PACKAGE containing the record, Core, public page, Internet Archive links, certificate, AI package, blockchain evidence, next-stage instructions and lost-key guidance | T3: The SAVED PACKAGE optionally inserts the owner key client-side at <!--DEMI-OWNER-KEY--> in the browser; the Worker never sees or serves a key on this route | T4: GET /capsule/blue-screen.js is one shared result screen for ETH Capsule, Card Capsule and DEMI for Authors, showing code, anchor status, registry link, and four items: owner key copy, certificate download, Saved package download, AI package copy | T5: Sealed and unlisted records return the same minimum as their other public views unless the owner key is supplied as ?k=, which is never cached | T6: GET /llms.txt describes the Registry to AI crawlers; CAPSULE_URL variable names the registration page, defaulting to https://www.ramsmile.com | T7: Registration, payment, Core, anchoring and listing logic are unchanged from V5.8.6 |
| Constraints | No email and no key appear in either the AI PACKAGE or the SAVED PACKAGE | The owner key via ?k= must never be cached | The Worker must never see or serve a key on the /saved route | The AI assistant's rules (embedded in the AI PACKAGE) prohibit adding facts, require SHA-256 verification before building, require new stages to use the current code as Parent, prohibit requesting keys, prohibit legal advice, and require replies in the registrant's language | Sealed and unlisted records receive only their standard minimum public view without ?k= | Changing blue-screen.js propagates to all three capsule pages simultaneously | CAPSULE_URL defaults to https://www.ramsmile.com if not set | All logic outside the two new endpoints and the shared screen is as in V5.8.6 |
| Mechanisms | T1: Verify the /ai endpoint returns plain text structured in sections A–F; check that no email or key appears in the output; test with a sealed record without ?k= to confirm minimum view | T2: Verify the /saved endpoint returns a single valid HTML file containing all listed sections; confirm <!--DEMI-OWNER-KEY--> is absent from the served file and only injected client-side when the registrant ticks the box | T3: Confirm via network inspection that the Worker response body for /saved never contains the owner key; confirm client-side injection occurs only on checkbox tick | T4: Load blue-screen.js from /capsule/blue-screen.js and confirm all four items render correctly in English and Russian on all three capsule pages; edit the file once and verify propagation | T5: Request a sealed record with and without ?k= and compare responses; confirm ?k= responses carry no-cache headers | T6: Fetch /llms.txt and confirm it describes the Registry; set and unset CAPSULE_URL and confirm fallback | T7: Run V5.8.6 regression tests against registration, payment, Core, anchoring and listing routes to confirm no change |
| Boundaries | Out of scope for V5.8.7: any change to registration, payment, Core extraction, anchoring or listing logic | The GPT Store designated space is replaced, not extended | The landing page and certificate linking to the AI package are noted as done but not separately specified here | OPEN: The passage does not state how the AI PACKAGE handles a Kind not in the listed set (NOV, TECH, AGR, STM, SCI) beyond 'general' | OPEN: No detail is given on the format or content of the blockchain evidence section inside the SAVED PACKAGE | OPEN: The passage does not specify rate-limiting or authentication requirements for the two new public endpoints |
| Registered file | Worker_demi_proxy_V5_8_7_AI_PACKAGE.js |
| File SHA-256 | 02ae67d75f96e4fef04149cf55ee8de5f159e4d573e19d6db97b2370f7ccf5c7 |
| Analysed extract SHA-256 | f944a3cd3e54054a4d553f1684d774db8ba056c3e83043710d9d3292b8199665 |
| Payment | Ethereum · 0x83bfbae47160f1ffb7f9a1e220c62fc33c8ee6990b7482eeb2e3a1ef5fe81f84 View on Etherscan → |
| Registered at (UTC) | 2026-10-06T23:54:00.065Z |
| Registry anchor (Ethereum) | block 26136754 · 2026-10-06T23:54:11.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-500520-EN |
| Activation Reference | DEMI:1042:UPL-TECH-26-294654-EN:O |
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.
https://www.demicapsule.com/registry/UPL-TECH-26-294654-EN/index.html
To continue this work with an AI assistant, tell it: Read https://www.demicapsule.com/registry/UPL-TECH-26-294654-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:04:59.622Z · rebuilt each time it is opened; a saved copy shows the record as it stood at that moment