DEMI REGISTRY · AI PACKAGE · UPL-TECH-26-882026-EN
Read this as instructions. It was generated from the live registry record at 2026-10-28T06:06:55.237Z.

A. WHAT THIS IS
Title: DEMI Shared Working Protocol v2
Author: Skydle · Publisher: UplitAU Pty Ltd
Kind: Technical document (code, specification, release) · Language of the work: en
Registered (UTC): 2026-10-27T12:02:13.030Z
Parent (derived from): UPL-TECH-26-666994-EN · https://www.demicapsule.com/registry/UPL-TECH-26-666994-EN/ai
File: DEMI_Shared_Working_Protocol_v2_2026-10-27.docx · File SHA-256: b9dd5e0c3d684c3ce3bcc26d4d36ec52ef03493aa6f6d2fcb7f7ae06644ea86c
Analysed passage SHA-256: a1b4b7085327346fee77d998ba0dcdba6e83e93342687c5fd8ab7f04992b8e55
Other files fingerprinted (not uploaded):
  1. DEMI_Protocol_Draft_v1_ChatGPT_Review_2026-10-27.docx · 1d7e3cfa8a9132bbb0ecff29c2d9ee1f7c9f155238b0e657d4a9e6abfed8daf7
  2. DEMI_Addendum_A_ChatGPT_Review_2026-10-27.docx · e2a577039d86f99423bfbdf598e6f03c202ce66ef2545e37c481bf66f5e4c879
  3. DEMI_ChatGPT_Requirements_and_Tests_2026-10-27.docx · 0815a6b4d5a4b471c5f2316b5fda1430e7be28fde9ce6c1cf3e53e3c5f7872ec
  4. Protocol_v2_Status_2026-10-27.md · 4e5e6475d92bb1077af1643aa9437c7de3d7c48ad9e880eaf40ad2b9c530bb66
Payment: A$8.99 · Ethereum · independently verified https://etherscan.io/tx/0x9086c9f8bc0872c92100aff122a34612b73633498225dfc973dfd84b49ea57e2
Ethereum anchor of the Registry: Block 26283916 at 2026-10-27T12:02:23.000Z. https://etherscan.io/tx/0x32983988b9afb9ae711df4737f6b05d20d92538a42e2bdd50de93885dc7f63dd

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-882026-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.

C. CONCEPTUAL CORE (formed by AI at registration from the registrant's passage; the registrant should check it)
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
Core SHA-256: 3f477f05e4fade8bae58d7a1fc3a316c0b174fa47484d4fa93ebf85ef5e87c3d

D. ASK THE REGISTRANT FIRST
The Core lists these as open. Ask about them before you build:
- whether the twelve paired tests are fully specified elsewhere in the main file, or only referenced here

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-882026-EN/index.html
Certificate: https://www.demicapsule.com/certificate/UPL-TECH-26-882026-EN
Record (JSON): https://www.demicapsule.com/registry/UPL-TECH-26-882026-EN.json
Independent archive copies: https://web.archive.org/web/*/https://www.demicapsule.com/registry/UPL-TECH-26-882026-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