“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.”
PropositionsT1: 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
ConstraintsNo 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
MechanismsT1: 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
BoundariesOut 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