DEMI CAPSULE · REGISTRY CERTIFICATE · UplitAU Pty Ltd

What DEMI Capsule became — a shared memory for AI work, checked by more than one AI

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

DEMI Conceptual Core

Core StatementBefore these sessions DEMI Capsule proved file existence and formed a Conceptual Core; these sessions added cross-session shared memory via Parent-linked stage records and dual-AI cross-checking so any new Claude or ChatGPT conversation can continue verified work without relying on chat history.
PropositionsT1: Staged work records are linked by Parent codes so a new AI session continues from earlier Conceptual Cores without chat memory | T2: A second AI from a different company checks each Core's statements as true or false against the owner-released main file | T3: The true/false check may be registered as its own record with the earlier record as Parent | T4: Claude and ChatGPT plugins are identical so check preparation and recording is uniform whichever AI performs it | T5: Three overclaiming Cores (696525, 666994, 882026) were caught and fixed openly, demonstrating the method works | T6: The owner decides at every step whether to release the file, accept the check, and publish the record
ConstraintsChecking requires the main file to be released by the owner | Two AIs reduce shared mistakes but do not eliminate them | Two checks do not make a statement true | Owner authority is final at every decision point | Plugin identity must remain identical across Claude and ChatGPT implementations | Method operates independently of pending plugin reviews | Protocol v2 applies | Standard: UPL-TECH-26-882026-EN | Registry: demicapsule.com
MechanismsT1: Verify a new session reads only Conceptual Cores from Parent-linked records and continues work correctly — confirmed when Claude's memory was compressed and work resumed correctly | T2: Supply the checking AI with the Core and the main file; confirm each flagged statement maps to file content or is absent from it | T3: Confirm the check record carries the Parent code of the record it checked and is readable by either AI | T4: Run identical check preparation steps on Claude and on ChatGPT; compare outputs for procedural equivalence | T5: Retrieve records 696525, 666994, 882026; confirm their Cores previously contained statements beyond file content and that corrected versions are now registered | T6: Audit log must show owner release action precedes each check and owner approval precedes each publication
BoundariesChecking without the main file is out of scope | Automatic or AI-initiated publishing without owner decision is out of scope | Removal of all shared mistakes is not claimed | Pending plugin review outcomes are not addressed here | No claims about future AI systems beyond current Claude and ChatGPT plugins | OPEN: Whether registering every check record is mandatory or optional; whether the identical-plugin requirement is formally specified anywhere in the protocol

Chain of Evidence

Registered fileDEMI_Capsule_Plain_Words_Brief_2026-10-29.docx
File SHA-2564250c1727162e6d5dea9f65bd8c1433299e195312a99ba8406df879b2cfc0e6f
Analysed extract SHA-2565aeb5b95ccc2f0df08c23f43b30d745a5573dcdd1dc7c3c72c6420a32713a1f8
PaymentEthereum · 0xbb0705c75ab60325969d10d77757f49c7b2baa41eb93ad60e15e852c6b7d44d1 View on Etherscan →
Registered at (UTC)2026-10-28T21:37:26.101Z
Registry anchor (Ethereum)block 26293969 · 2026-10-28T21:37: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-882026-EN
Activation ReferenceDEMI:1042:UPL-TECH-26-285645-EN:Q

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. Handover_Brief_Session_2026-10-21_to_29.md
7405 bytes
SHA-256: 478e172f6a002b7ea0137163c0d1dbfa09d843cce605a45ffde02684a27493c1

Canonical Landing Page

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

AI Package

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