Claude–ChatGPT File Exchange Between AI Sessions — Technical and Strategic Brief
Skydle · 2026-11-05
UPL-TECH-26-117531-EN
“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.”
PropositionsT1: 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.
ConstraintsExecution 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.
MechanismsT1: 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.
BoundariesThis 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?
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.