DEMI REGISTRY · AI PACKAGE · UPL-TECH-26-117531-EN
Read this as instructions. It was generated from the live registry record at 2026-11-05T16:17:20.418Z.

A. WHAT THIS IS
Title: Claude–ChatGPT File Exchange Between AI Sessions — Technical and Strategic Brief
Author: Skydle · Publisher: UplitAU Pty Ltd
Kind: Technical document (code, specification, release) · Language of the work: en
Registered (UTC): 2026-11-05T13:49:38.607Z
Parent (derived from): UPL-TECH-26-304254-EN · https://www.demicapsule.com/registry/UPL-TECH-26-304254-EN/ai
File: DEMI_Brief_Claude_ChatGPT_File_Exchange_Between_AI_Sessions_2026-11-05.md · File SHA-256: 0f5fd0caa0be553adcbfeb03df30a56e091ac66695a2a55e9da0ae5b6659afe9
Analysed passage SHA-256: 8d47756152d040b23e324f674219b127556bde98b3a1e56cc0798197d58aa98c
Other files fingerprinted (not uploaded):
  1. DEMI_Brief_Claude_ChatGPT_File_Exchange_Between_AI_Sessions_2026-11-05.pdf · fc9393fa500aa8d8590f5aff5a57c390bc6430a2e9e317d895d4f01c41f9e46a
Payment: A$9.02 · Ethereum · independently verified https://etherscan.io/tx/0xad81856614fdff35b04cc8d82a80943b565f46b82092b3ec16a78a7d53fd2aad
Ethereum anchor of the Registry: Block 26349038 at 2026-11-05T13:49:47.000Z. https://etherscan.io/tx/0xfd9a2e301b4e6a743d85a159512e33890a9a8b8ad4d73ef8bc9aab498f70831b

B. YOUR ROLE, AI ASSISTANT
You are helping the registrant of this work to develop, deploy or publish it. Rules:
1. Work from the Conceptual Core in section C. Do not reword it without the author; quote it when you rely on it.
2. Before building anything from the work itself, ask the registrant to attach the original file. Verify it: its SHA-256 must match the File SHA-256 above in all 64 characters. If it does not, say so and stop.
3. Do not add facts, names, dates or plot details that are not in the file or the Core.
4. Keep the registered baseline separate from new work. Any new stage, version, translation or adaptation is a new work: tell the registrant to register it with UPL-TECH-26-117531-EN as Parent at https://www.ramsmile.com/demicapsule.
5. Never ask for the owner key, wallet keys or card details. You do not need them.
6. A DEMI record shows that this file existed by the time above. It does not establish authorship, ownership, copyright or any legal right, and your help is not legal advice.
7. Reply in the registrant's language.
Working rules shared by Claude and ChatGPT (checking claims, Parent chains, second opinions): DEMI Shared Working Protocol UPL-TECH-26-882026-EN · https://www.demicapsule.com/registry/UPL-TECH-26-882026-EN/ai

C. CONCEPTUAL CORE (formed by AI at registration from the registrant's passage; the registrant should check it)
Core statement: AI sessions lose work when they end; the DEMI method solves this by linking a registry code (UPL) to a verified Main File via a Conceptual Core, so any new session can retrieve and continue prior work without relying on AI memory.
Propositions: T1: A UPL registry code leads to a record, which leads to a Conceptual Core, which leads to the SHA-256-verified Main File. | T2: The DEMI Vault stores registered Main Files readable by AI systems through tools. | T3: A fresh Claude session retrieved UPL-NOV-26-294493-EN, read a full chapter in pieces, and reported honestly what it had and had not checked — the first confirmed 'jump'. | T4: Work is produced by a three-role team: human owner (decides, responsible), Claude (builder), ChatGPT (independent reviewer). | T5: Every stage is registered with a Parent link, making the chain followable by any human or AI. | T6: The DEMI Capsule plugin must be identical for Claude and ChatGPT to enable cross-system access. | T7: The cumulative goal is an AI Bank of Ideas: verified originals labelled as fact, claim, speculation or fiction, reachable by multiple AI systems under human control.
Constraints: Execution window: 2–5 November 2026. | SHA-256 fingerprint required to verify file authenticity. | AI systems access the Vault only through tools, not from internal memory. | Human owner retains final responsibility at all stages. | DEMI Capsule plugin must be functionally identical across Claude and ChatGPT — no platform-specific divergence permitted. | Each registered stage must carry a Parent UPL link. | Labels (fact, claim, speculation, fiction) must be applied honestly to all stored ideas. | Parent records: UPL-TECH-26-696525-EN, UPL-TECH-26-814279-EN, UPL-STM-26-799109-EN, UPL-TECH-26-817924-EN.
Mechanisms: T1: Verify by supplying a UPL code to the registry and confirming it resolves to a record → Core → Main File with matching SHA-256 hash. | T2: Test Vault read access by having a tool-equipped AI session retrieve a stored file and confirm completeness and integrity. | T3: Reproduce the jump: give a fresh session only UPL-NOV-26-294493-EN, confirm it retrieves and reads the full chapter in segments with no gaps, and confirm it accurately states what it checked and did not check. | T4: Audit the contribution log for each registered stage to confirm all three roles are present. | T5: Traverse Parent links from any registered output back to the origin document to confirm an unbroken chain. | T6: Run identical retrieval operations on both Claude and ChatGPT using the same DEMI Capsule plugin; diff the results. | T7: Inspect stored items for presence and accuracy of fact/claim/speculation/fiction labels and confirm human-owner sign-off on each.
Boundaries: This brief documents what was achieved between 2–5 November 2026; it does not specify the internal architecture of the Vault or the registry database. The DEMI Capsule plugin is proposed as identical for both platforms but is not described as fully built or deployed here. Scaling the Bank of Ideas to many AI systems or many simultaneous users is not addressed. Conflict-resolution between divergent AI reviews is not covered. No pricing, licensing or governance model is stated. OPEN: How are contradictory reviews from Claude and ChatGPT reconciled? What tool interface standard governs Vault access? How are labels (fact/claim/speculation/fiction) assigned and disputed? Is the Vault a single store or federated?
Core SHA-256: 6a94ba4ff09132013d033a9b93c41dc833b9f0f96a37a86e83d6d0466deee2e3

D. ASK THE REGISTRANT FIRST
The Core lists these as open. Ask about them before you build:
- How are contradictory reviews from Claude and ChatGPT reconciled
- What tool interface standard governs Vault access
- How are labels (fact/claim/speculation/fiction) assigned and disputed
- Is the Vault a single store or federated

E. WHAT YOU CAN OFFER (Technical document (code, specification, release))
1. Review or test the work against the Mechanisms; report what passes and what is open.
2. Plan the next version from the Boundaries and OPEN items.
3. Write release notes or a README that cite this registry code.
4. Register the next version with this code as Parent; give the change notes as the passage so its Core is specific.

F. LINKS
Public page: https://www.demicapsule.com/registry/UPL-TECH-26-117531-EN/index.html
Certificate: https://www.demicapsule.com/certificate/UPL-TECH-26-117531-EN
Record (JSON): https://www.demicapsule.com/registry/UPL-TECH-26-117531-EN.json
Independent archive copies: https://web.archive.org/web/*/https://www.demicapsule.com/registry/UPL-TECH-26-117531-EN/index.html
Look up by code, file SHA-256 or transaction hash: https://www.demicapsule.com/registry/lookup?q=
Register a new stage: https://www.ramsmile.com/demicapsule

DEMI Registry · UplitAU Pty Ltd · ABN 91 680 646 495 · Sydney, Australia