“DEMI Capsule Plugin v1.0.4 solves the problem of non-transferable AI-assisted work sessions by providing a shared ChatGPT/Claude plugin that creates dated, registry-backed stage records retrievable by any compatible assistant via a UPL code.”
PropositionsT1: Portal Builder skill prepares a work stage and drafts its passage for registry submission | T2: Continue skill resumes a prior work session from a UPL registry code or its AI package | T3: Verify skill compares a file's SHA-256 hash against its registry record | T4: Both ChatGPT and Claude releases are fingerprinted under integration spec UPL-TECH-26-310441-EN | T5: v1.0.4 succeeds v1.0.3 (UPL-TECH-26-506840-EN) with identical skill sets across both assistant targets | T6: User registration is handled externally at ramsmile.com/demicapsule for A$9 by card
ConstraintsPlugin must never pay, register or hold keys on behalf of the user. Registration requires a card payment of A$9 at ramsmile.com/demicapsule performed entirely by the person. Claude version must conform to Claude directory submission requirements (submitted 8 October 2026). ChatGPT version must conform to OpenAI business verification requirements (submitted 10 October 2026). Both plugin packages must expose identical skills. SHA-256 is the required hash algorithm for Verify. All operations reference UPL codes as the retrieval and continuity identifier.
MechanismsT1: Portal Builder — verify output is a correctly structured stage passage ready for registry submission; test by staging a sample work unit and confirming dated record is produced | T2: Continue — supply a known UPL code or AI package and confirm the session resumes with correct prior-stage context | T3: Verify — hash a test file with SHA-256 externally and confirm plugin Verify returns a match or mismatch against the registry record | T4: Cross-check fingerprint record links both ChatGPT and Claude v1.0.4 packages to UPL-TECH-26-310441-EN | T5: Diff skill definitions across both packages to confirm identical capability surface | T6: Attempt any payment or key-storage action within the plugin and confirm it is refused
BoundariesOut of scope: payment processing, user registration, and key management inside the plugin. Not yet built: (1) ETH micro-payment flow allowing an assistant to initiate registration and pay approximately 12 cents per anchor from the user's own wallet with per-transaction explicit consent — blocked pending legal determination on the ETH rail (R1), an approved consent UX design, and a technical mechanism to pay a third party from within an AI session; (2) a read-only MCP connection enabling assistants to retrieve registry records reliably by UPL code. OPEN: R1 — legal status of the ETH payment rail for this use case; consent design specification for per-anchor ETH payments; technical method for third-party payment from an AI session; architecture and availability of the read-only MCP retrieval connection.
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.