DEMI Shared Working Protocol — Draft v1 (for review by ChatGPT)
Skydle · 2026-10-27
UPL-TECH-26-666994-EN
“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.”
PropositionsT1: 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
ConstraintsVerified 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
MechanismsT1: 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
BoundariesProtocol 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
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.