| Core Statement | DEMI Shared Working Protocol v2 defines unified working rules for AI assistants (Claude and ChatGPT) operating from a DEMI record, ensuring equal operation, consistent evidence handling, and verified file integrity across a single Registry and Worker. |
| Propositions | T1: One Registry and one Worker serve both Claude and ChatGPT assistants under equal rules, not identical wording | T2: AI-assisted work area is any supported Claude or ChatGPT chat receiving a UPL code or AI Package; Portal Builder GPT not required | T3: The human owner releases the main file; assistants use only owner-attached files | T4: Core may be discussed without a file (PROPOSED or OPEN); verdict, adaptation or second opinion requires the original file plus full SHA-256 match and may request a Parent file | T5: Regime 1 (simple) is default; Regime 2 adds a second AI and a shared review statement filled in by the AI | T6: Passage and Core are checked separately on scale P0–P3; P3 records two checks, not agreement | T7: Inherited disputed claims stay OPEN, never VERIFIED; wrong file, fingerprint or Parent blocks; missing evidence is NOT CHECKED; wording slip gets one note | T8: No keys, payments, AI registration or legal claims permitted | T9: Five read-only tools stay unchanged during directory reviews | T10: Twelve paired tests are defined | T11: Worker V5.9.5 fields, all OPEN items, Protocol line, own-domain address, and get_lineage are planned but not yet built |
| Constraints | SHA-256 full match required for verdict, adaptation or second opinion | Parent file may be requested for those operations | Regime 2 requires a second AI and a shared review statement | Passage and Core checked separately; P3 = two checks recorded, not consensus | Disputed inherited claims must remain OPEN | Wrong file, fingerprint mismatch or missing Parent is blocking | Missing evidence recorded as NOT CHECKED | Wording slip limited to one note | No keys, payments, registration or legal claims by AI | Five read-only tools must remain unchanged during directory reviews | Work area limited to supported Claude or ChatGPT chats with UPL code or AI Package |
| Mechanisms | T1: Verify that Registry and Worker serve both assistants and apply the same rules by running the twelve paired tests on identical cases | T2: Confirm Portal Builder GPT is not invoked during normal operation; test with UPL code delivered directly to chat | T3: Attempt assistant-side file release; confirm it is blocked and only owner-attached files are accepted | T4: Attempt Core discussion without file and confirm PROPOSED/OPEN status; then supply file with SHA-256 match and confirm verdict becomes available | T5: Default to Regime 1; switch to Regime 2 and confirm second AI and shared review statement are required and produced | T6: Run passage check and Core check independently; confirm P3 records two separate check results without forcing agreement | T7: Submit a disputed inherited claim and confirm it remains OPEN; submit wrong file and confirm block; submit case with missing evidence and confirm NOT CHECKED; introduce wording slip and confirm single note only | T8: Attempt to trigger key generation, payment or registration action; confirm all are blocked | T9: Invoke directory review and confirm all five read-only tools are unmodified before and after | T10: Execute all twelve paired tests and confirm consistent outcomes across both assistants | T11: Confirm V5.9.5 fields and get_lineage are absent from current build and flagged as planned |
| Boundaries | Portal Builder GPT is out of scope for normal operation | AI assistants may not release files, register, make payments, hold keys or assert legal claims | Directory reviews must not alter the five read-only tools | Wording-only differences between assistants are out of scope for blocking errors | Worker V5.9.5 extended fields (all OPEN items, Protocol line, own-domain address) and get_lineage are planned but not built in this version | Merging of Draft v1 and ChatGPT review into v2 is complete; further merging is out of scope here | OPEN: whether the twelve paired tests are fully specified elsewhere in the main file, or only referenced here |
| Registered file | DEMI_Shared_Working_Protocol_v2_2026-10-27.docx |
| File SHA-256 | b9dd5e0c3d684c3ce3bcc26d4d36ec52ef03493aa6f6d2fcb7f7ae06644ea86c |
| Analysed extract SHA-256 | a1b4b7085327346fee77d998ba0dcdba6e83e93342687c5fd8ab7f04992b8e55 |
| Payment | Ethereum · 0x9086c9f8bc0872c92100aff122a34612b73633498225dfc973dfd84b49ea57e2 View on Etherscan → |
| Registered at (UTC) | 2026-10-27T12:02:13.030Z |
| Registry anchor (Ethereum) | block 26283916 · 2026-10-27T12:02:23.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-666994-EN |
| Activation Reference | DEMI:1042:UPL-TECH-26-882026-EN:7 |
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_Draft_v1_ChatGPT_Review_2026-10-27.docx 18903 bytes SHA-256: 1d7e3cfa8a9132bbb0ecff29c2d9ee1f7c9f155238b0e657d4a9e6abfed8daf7 |
| 2. DEMI_Addendum_A_ChatGPT_Review_2026-10-27.docx 13537 bytes SHA-256: e2a577039d86f99423bfbdf598e6f03c202ce66ef2545e37c481bf66f5e4c879 |
| 3. DEMI_ChatGPT_Requirements_and_Tests_2026-10-27.docx 46862 bytes SHA-256: 0815a6b4d5a4b471c5f2316b5fda1430e7be28fde9ce6c1cf3e53e3c5f7872ec |
| 4. Protocol_v2_Status_2026-10-27.md 2575 bytes SHA-256: 4e5e6475d92bb1077af1643aa9437c7de3d7c48ad9e880eaf40ad2b9c530bb66 |
https://www.demicapsule.com/registry/UPL-TECH-26-882026-EN/index.html
To continue this work with an AI assistant, tell it: Read https://www.demicapsule.com/registry/UPL-TECH-26-882026-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:34.849Z · rebuilt each time it is opened; a saved copy shows the record as it stood at that moment