DEMI REGISTRY · AI PACKAGE · UPL-TECH-26-814279-EN
Read this as instructions. It was generated from the live registry record at 2026-10-28T07:25:48.979Z.

A. WHAT THIS IS
Title: DEMI Capsule and Vault — Technical Summary v1.0
Author: Skydle · Publisher: UplitAU Pty Ltd
Kind: Technical document (code, specification, release) · Language of the work: en
Registered (UTC): 2026-10-16T10:42:29.450Z
Parent (derived from): UPL-TECH-26-667079-EN · https://registry.demicapsule.com/registry/UPL-TECH-26-667079-EN/ai
File: DEMI_Capsule_and_Vault_Technical_Summary_v1_0.md · File SHA-256: 42aded0fe0dc79507e98e5e6f205d17e8c2d9fee572492877306f60c6ffea9cc
Analysed passage SHA-256: feb91230dfa06b9e094fdb0492c00df6f286211c2368d56a01f78ad287105e77
Payment: A$9.02 · Ethereum · independently verified https://etherscan.io/tx/0xd8f3470913d10876f6fd7af32b7c070aacb866adc3ebbe3387c71b9a317369d0
Ethereum anchor of the Registry: Block 26204568 at 2026-10-16T10:42:35.000Z. https://etherscan.io/tx/0xe9012ec86185decb7c525d48751ca577eee7b3f9728052f2c472dc93c6dcc0d7

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-814279-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.
Working rules shared by Claude and ChatGPT (checking claims, Parent chains, second opinions): DEMI Shared Working Protocol UPL-TECH-26-882026-EN · https://registry.demicapsule.com/registry/UPL-TECH-26-882026-EN/ai

C. CONCEPTUAL CORE (formed by AI at registration from the registrant's passage; the registrant should check it)
Core statement: UPL-TECH-26-667079-EN proposes DEMI Capsule and DEMI Vault: a browser-side SHA-256 fingerprinting and Ethereum-anchored registry system with an AI plugin and a gated file vault, so AI assistants can verify but never register or hold keys.
Propositions: T1: Registry assigns UPL code, SHA-256 (browser-computed, file not uploaded), Parent code, Conceptual Core, and Ethereum anchor per work stage | T2: DEMI Capsule plugin (Claude/ChatGPT) exposes three skills (Portal Builder, Continue, Verify) and five read-only MCP tools (get_ai_package, get_record, lookup_record, list_children, verify_fingerprint), live at Worker V5.8.8 | T3: DEMI Vault Gate v0.1 (Cloudflare Worker, R2+KV, pilot) stores registered main file only if deposited SHA-256 matches record SHA-256; owner sets access as closed/request/open; get_file_link tool reports availability; export package transfers file and evidence to institution vault | T4: Registration costs A$9 per card at ramsmile.com/demicapsule and is performed by the human owner only
Constraints: AI assistants are read-only: they verify; they do not register, pay or hold keys | SHA-256 computed client-side; file never uploaded during registration | Vault deposit rejected if SHA-256 mismatches record | Request permits use expiring revocable links; only token hash stored, not the link itself | User-agent filter is a barrier, not a security guarantee | Consistency check confirms passage matches file; does not certify content truth | DEMI Vault not yet deployed (37 local tests passed, pilot only) | Cloudflare Worker and R2/KV infrastructure dependency | Worker V5.8.8 required for live plugin
Mechanisms: T1: Verify UPL code chain via lookup_record and list_children; confirm SHA-256 matches local file hash computed in browser; check Ethereum anchor exists in Registry state | T2: Test each MCP tool independently with known UPL codes; invoke Verify skill against a record and confirm fingerprint match/mismatch response; test Portal Builder and Continue skills for correct record linkage | T3: Attempt vault deposit with correct and incorrect SHA-256 to confirm accept/reject logic; test each permit mode (closed/request/open) via get_file_link responses; validate export package integrity by comparing file hash and evidence post-export; reference 37 passed local tests | T4: Confirm registration card flow at ramsmile.com/demicapsule produces a valid UPL code and Ethereum anchor
Boundaries: DEMI Vault Gate v0.1 is pilot only — not deployed in production | Out of scope: client-side encryption | Out of scope: owner-key verification by the Registry | Out of scope: request relay by email | Out of scope: payment as a permit mechanism | Out of scope: file indexing in a database | Out of scope: Cloudflare paid plan features | Out of scope: legal review for third-party files | OPEN: Core formation timed out on UPL 667079 (~20 s limit) — resolution not stated; client-side encryption design; owner-key check by Registry; email-based request relay; payment-as-permit logic; database index; Cloudflare paid plan migration path; legal framework for third-party file deposits
Core SHA-256: 5606c2c81a81eade78be6948a00acdff86e147b4335f1a500f2ad332bd0c0c0c

D. ASK THE REGISTRANT FIRST
The Core lists these as open. Ask about them before you build:
- Core formation timed out on UPL 667079 (~20 s limit) — resolution not stated
- client-side encryption design
- owner-key check by Registry
- email-based request relay
- payment-as-permit logic
- database index
- Cloudflare paid plan migration path
- legal framework for third-party file deposits

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://registry.demicapsule.com/registry/UPL-TECH-26-814279-EN/index.html
Certificate: https://registry.demicapsule.com/certificate/UPL-TECH-26-814279-EN
Record (JSON): https://registry.demicapsule.com/registry/UPL-TECH-26-814279-EN.json
Independent archive copies: https://web.archive.org/web/*/https://registry.demicapsule.com/registry/UPL-TECH-26-814279-EN/index.html
Look up by code, file SHA-256 or transaction hash: https://registry.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