| Core Statement | Registered works lose their physical file locations across chats, projects and AI systems; Worker V5.9.4 solves this by adding a personal keyed table that stores per-record file-location notes and DEMI Locate search steps, so an AI or person can find the file later. |
| Propositions | T1: Operator token publishes a re-formed Conceptual Core on an ETH-paid record only if payment wallet is in OPERATOR_WALLETS, verified on-chain; otherwise Core is returned unpublished; scope narrowed to UplitAU's own records. | T2: POST /registry/owner-check answers yes/no for a record's owner key, only to callers holding OWNER_CHECK_SECRET, rejects operator token, rate-limited to 20 wrong keys per record per hour; prepares DEMI Vault Gate. | T3: GET /registry/table retrieves records by code or Parent family in JSON, CSV, Markdown or HTML with title, file name, registration time, fingerprint start…end, Parent and certificate; private records expose only code, time and fingerprint. | T4: One personal key stored as hash only lists a person's records with a private per-record note for file location and related chat; a read-only link renders the table in browser, Excel, Claude or ChatGPT; JSON carries DEMI Locate steps to search project files then chats, returning a one-line location answer. | T5: Corrections fix V5.9.3 bugs: author-name-only matching for add-all, remove-from-list action, bulk location paste, inline error display, table shown under button, Parent displayed as 6 digits matching Director's Excel index. |
| Constraints | Five read-only MCP tools (get_ai_package, get_record, lookup_record, verify_fingerprint, list_children) are unchanged. Registration, payments, anchoring and certificates are unchanged. No email, owner key or file location appears in public output. AI must never pay, register or hold keys. Owner-check rate limit: 20 wrong keys per record per hour. OWNER_CHECK_SECRET required for owner-check endpoint. Personal key stored only as a hash. Personal list and notes stored in UplitAU Cloudflare storage. Builds on V5.9.1 (UPL-TECH-26-243670-EN). Live date: 18 October 2026. |
| Mechanisms | T1: On-chain wallet check verified against OPERATOR_WALLETS; test by submitting re-form request from unlisted wallet and confirming Core is returned not published. | T2: Call POST /registry/owner-check with correct and incorrect keys; confirm rate-limit triggers at 21st wrong key per hour; confirm operator token is rejected. | T3: Request table in each format (JSON, CSV, Markdown, HTML) for public and private records; confirm private records show only code, time and fingerprint. | T4: Add records via personal key, save location notes, open read-only link in browser and in Claude/ChatGPT; verify DEMI Locate steps execute and return one-line answer. | T5: Attempt add-all with a record paid by UplitAU for another author; confirm it is excluded; paste multiple locations at once; confirm errors display inline and table refreshes under button. Local checks: 44, 26, 19, 31, 5, 10 automated checks passed; Chromium page-click 17 checks, no script errors; MCP output identical to V5.9.3 on 12 of 12 checks; live: 5 review checks passed, version reported V5.9.4, 62 records loaded with 19 locations, foreign-author record removed. |
| Boundaries | Registry cannot access Claude or ChatGPT accounts or search their chats; file finding is performed by the AI or person guided by the table. Author names are free text with no validation. Personal list and notes must be downloaded as CSV regularly as a backup. Out of scope: DEMI Vault Gate v0.2 (needs OWNER_CHECK_SECRET deployed to both Workers); sixth MCP tool make_table and demi-locate skill in plugin v1.0.6 pending directory approval; optional My records key field on Capsule page. OPEN: DEMI Vault Gate v0.2 deployment; make_table tool and demi-locate plugin skill after directory approval; My records key field on Capsule page. |
| Registered file | Worker_demi_proxy_V5_9_4.js |
| File SHA-256 | afb7261ec83b4f44eb1b563e92003d1aca39dacd077e746ee9dbf5cdfb7e2485 |
| Analysed extract SHA-256 | 3bae3b42726ab83b1097e224496e86a806b5c98d63fd8f3ce9b7eb0654f8f453 |
| Payment | Ethereum · 0xfb285ac56135e3cc4723bd406590d9d3aedc4fff008d7e65c9e886e29699a298 View on Etherscan → |
| Registered at (UTC) | 2026-10-18T04:12:40.552Z |
| Registry anchor (Ethereum) | block 26216980 · 2026-10-18T04:12:47.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-243670-EN |
| Activation Reference | DEMI:1042:UPL-TECH-26-741263-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.
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_2.js 283447 bytes SHA-256: 5b8243647d38fcde0c33e4f11af5ff0708fc263d8e0075c74b8f5608ecc1b276 |
| 2. Worker_demi_proxy_V5_9_3.js 304219 bytes SHA-256: c75389142ca0f46151a4d730a7ba8bbfd6a25f1e872a80f810708a5915cfd7cf |
| 3. How_to_find_the_file_of_a_DEMI_record_v1.md 3674 bytes SHA-256: 20e89415f71dee9b346cdb313ba8e752d06c2a0a192dbf4ec7b5a3495fca318a |
| 4. Your_DEMI_table_how_to_use_v1.md 4863 bytes SHA-256: 1c6f512662a8e504fda099326e627e041b268103a727bc2f2372a02822e1295a |
https://www.demicapsule.com/registry/UPL-TECH-26-741263-EN/index.html
To continue this work with an AI assistant, tell it: Read https://www.demicapsule.com/registry/UPL-TECH-26-741263-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:20.506Z · rebuilt each time it is opened; a saved copy shows the record as it stood at that moment