DEMI CAPSULE · REGISTRY CERTIFICATE · UplitAU Pty Ltd

DEMI Capsule Plugin v1.0.5: Read-only Registry Connection, Submitted to OpenAI

Skydle · 2026 · STARTER tier · REGISTERED
UPL REGISTRY CODE
UPL-TECH-26-144456-EN

DEMI Conceptual Core

Core StatementDEMI Capsule Plugin v1.0.5 solves the problem of AI assistants lacking access to registered creative works by connecting Claude and ChatGPT to the DEMI Registry via a read-only MCP server, enabling retrieval, preparation and verification without registration, payment or key handling.
PropositionsT1: get_ai_package retrieves a packaged work record for AI consumption | T2: get_record fetches a full registry record | T3: lookup_record resolves a UPL code to its record | T4: list_children enumerates sub-records of a parent entry | T5: verify_fingerprint checks a file against its SHA-256 hash without the file leaving the user's device | T6: Three skills (prepare a stage, continue a work, verify a file) are byte-identical across Claude and ChatGPT packages | T7: ChatGPT package submitted to OpenAI on 14 October 2026 with domain verified, skill checks passed and dedicated privacy notice
ConstraintsRead-only access only — no writes permitted | Backed by Worker V5.8.9 MCP server | SHA-256 verification is client-side; file does not leave user device | Registration requires card payment on the DEMI Capsule page, outside plugin scope | Plugin does not handle API keys or payments | Must maintain byte-identical skill logic across both assistant packages | Privacy notice required for OpenAI submission | Domain verification required
MechanismsT1–T4: Call each tool with a known UPL code or record ID and assert the returned data matches the registry entry | T5: Supply a file and its expected SHA-256; confirm plugin returns match/mismatch without transmitting the file | T6: Diff the skill definitions across Claude and ChatGPT packages byte-for-byte to confirm identity | T7: Check OpenAI submission status, domain verification record and privacy notice URL for presence and validity | End-to-end: Use a UPL code to continue a registered work through lookup_record then get_ai_package and confirm Conceptual Core and later stages are returned correctly
BoundariesPlugin does not register works, process payments or manage keys — these are out of scope | Plugin makes no legal claims: a record confirms a file existed at a time but does not establish authorship, ownership or legal rights | Packaging differences between Claude and ChatGPT builds are intentional and not subject to identity requirements | Review outcome of OpenAI submission is not yet known | OPEN: Whether future versions will add write or registration capabilities; whether Worker V5.8.9 version dependency is fixed or floating; how conflicts between cross-assistant result cross-checks are resolved

Chain of Evidence

Registered filedemi-capsule-v1.0.5c-chatgpt.zip
File SHA-25620bf9df3fe719269316556212e77c02f6d1b254fdcd0e1649cfb95d3ccebbcc6
Analysed extract SHA-2567997511410e173ed1a4702d0b6e61d3167fbf8e64f01ecde3ea8a81a0d8debfa
PaymentEthereum · 0x30a3aa97b123cb78345452d5b01cee1b146997d663125b2d3e023728fb003279 View on Etherscan →
Registered at (UTC)2026-10-14T23:04:29.115Z
Registry anchor (Ethereum)block 26193911 · 2026-10-14T23:04: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 fromUPL-TECH-26-817924-EN
Activation ReferenceDEMI:1042:UPL-TECH-26-144456-EN:D

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.

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.

1. Worker_demi_proxy_V5_8_9_MCP.js
245647 bytes
SHA-256: 62234b0c8c67ca3c757d510180a9372a007012a311a213b764f6727c7e413e89
2. DEMI_Technical_Brief_for_ChatGPT_2026-10-14.md
14884 bytes
SHA-256: add3ff41edf5a0a3985fae8ef15e4f1ac294df0edf0efa26b43b5e88b151ec62
3. demi-capsule-v1.0.5-claude.zip
61279 bytes
SHA-256: 592b71ceadf6182dd6aa0b5c3bf3037f70771d4f0c4088dd219b5dcd46203c22
4. DEMI_Skills_Identity_Check_v1.0.5.md
4128 bytes
SHA-256: 6b73c395354b042ab09ced15ee14c783398d4ebf53232838d7f2da21e420c5e2

Canonical Landing Page

https://www.demicapsule.com/registry/UPL-TECH-26-144456-EN/index.html

AI Package

To continue this work with an AI assistant, tell it: Read https://www.demicapsule.com/registry/UPL-TECH-26-144456-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:26.898Z · rebuilt each time it is opened; a saved copy shows the record as it stood at that moment