| Core Statement | The DEMI Shared Working Protocol (Draft v1) defines a shared baseline so that Claude and ChatGPT plugins interact with one Registry identically, using a passage-verification system and Parent-chain lineage to prevent error accumulation across AI-assisted registration stages. |
| Propositions | T1: One Registry and one Worker serve both assistants with identical plugin behaviour | T2: Passage verification statuses P0–P3 record who checked a passage against which file at what time | T3: Regime 1 allows a new stage without a Parent; Regime 2 requires cross-AI checking and a Parent link | T4: Ten rules govern every assistant's conduct during reading, labelling and registration | T5: The Protocol resides in AI Packages, a registered Protocol record, both plugins and ramsmile.com, independent of the retiring Portal Builder GPT | T6: Proposed Worker items (regime, authoring AI, passage status, review record type, Protocol version, new Package sections, Capsule page choices, get_lineage tool) are pending review | T7: This draft is submitted to ChatGPT for section-by-section review; the owner merges decisions into Protocol v2 with this record as Parent |
| Constraints | Verified means traceably checked by a named party against a named file fingerprint at a recorded time — not merely true | P3 requires two independently developed AI systems | Unverified Cores must be treated as hypotheses | New stages may only build on a Parent's verified conclusions | No assumed continuity without a Parent | Claims must be labelled VERIFIED, PROPOSED or OPEN | Owner must approve every next passage | Only proof errors block registration | AI assistants may not hold keys, make payments, perform registration or make legal claims | DEMI Portal Builder GPT retires 11 December 2026 and must not be a lineage dependency |
| Mechanisms | T1: Test both plugins against the same Registry record and compare outputs field by field | T2: Verify a passage by checking it against its main file hash at a recorded time with a named party; confirm status label matches the number of independent checkers | T3: Attempt Regime 1 without a Parent and confirm acceptance; attempt Regime 2 without a prior verified Parent and confirm rejection | T4: Run each of the ten rules as a checklist against a sample assistant session log | T5: Confirm Protocol text is retrievable from each named location independently of the Portal Builder GPT | T6: After reviews, confirm each proposed Worker item is present or explicitly deferred in the merged v2 record | T7: ChatGPT review produces a structured statement marking agreed, to-change and to-add points; owner decision log becomes part of the v2 Parent reference |
| Boundaries | Protocol v2 is not yet built — this draft is the input to its creation | The get_lineage tool is proposed, not implemented | Addendum A and the two technical briefs of 25 Oct are referenced but not reproduced here | This document is not an agreement between OpenAI and Anthropic and implies no corporate endorsement | The Protocol does not define how file fingerprints are generated or stored | No payment, key-management or legal-claim mechanisms are in scope | OPEN: How will conflicts between the two AI review statements be resolved before owner merging? | OPEN: Exact fingerprinting and timestamping method for passage verification is not specified | OPEN: Scope and API design of the read-only get_lineage tool are not defined |
| Registered file | DEMI_Shared_Working_Protocol_Draft_v1_2026-10-26(1).docx |
| File SHA-256 | 03b8a1cad0bd47173d284a2be2185d6dd8d5a7320ddef6a22a1bc78d7090b3aa |
| Analysed extract SHA-256 | da9fdc8219672a9a8a96f6171f34fc2903030a99008833b94eb73c39f83088ad |
| Payment | Ethereum · 0x9f90c95e7b8275bfd381b67df8bfb7eee17ae95dd63653be203422c24c2335c4 View on Etherscan → |
| Registered at (UTC) | 2026-10-27T00:34:44.069Z |
| Registry anchor (Ethereum) | block 26280487 · 2026-10-27T00:34:59.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 from | UPL-TECH-26-397277-EN |
| Activation Reference | DEMI:1042:UPL-TECH-26-666994-EN:G |
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.
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. DEMI_Protocol_Addendum_A_Two_Regimes_2026-10-27.docx 13768 bytes SHA-256: 88c90f0695da8f03251258453d0aa6549df3708bd17e299dcd07a01067435057 |
| 2. DEMI_Capsule_Technical_Brief_2026-10-25_Claude.docx 15939 bytes SHA-256: 132af891ca275a9e1f0ceb9ae7cef2df99b2208950036a80d06cf340c193cdcd |
| 3. DEMI_Capsule_Technical_Brief_2026-10-25_ChatGPT.docx 41559 bytes SHA-256: 0efcd698728750de9210d24cbfde79dfc1e4292a693c82ab066302457c6edc59 |
https://www.demicapsule.com/registry/UPL-TECH-26-666994-EN/index.html
To continue this work with an AI assistant, tell it: Read https://www.demicapsule.com/registry/UPL-TECH-26-666994-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:12.498Z · rebuilt each time it is opened; a saved copy shows the record as it stood at that moment