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

A. WHAT THIS IS
Title: DEMI_Capsule_Unified_Obligations_Register_v1.0_2026-10-02
Author: Skydle · Publisher: UplitAU Pty Ltd
Kind: Agreement or contract · Language of the work: en
Registered (UTC): 2026-10-02T05:34:58.599Z
Parent (derived from): UPL-TECH-26-310441-EN · https://registry.demicapsule.com/registry/UPL-TECH-26-310441-EN/ai
File: DEMI_Capsule_Unified_Obligations_Register_v1.0_2026-10-02.docx · File SHA-256: f9e4fef7326ab4c8d5229d04b7485bfa3033434970ce3b0b22569b37276f6ee0
Analysed passage SHA-256: f55421472dd9e67b41007190cfc7ac4fc0bbcc572fbe639159c22964f2e48371
Payment: A$9.00 · Ethereum · independently verified https://etherscan.io/tx/0x212e7e5d2f26aae9202f6ab189e57bae26e3ade249f029509029789fcdc4944d
Ethereum anchor of the Registry: Block 26102584 at 2026-10-02T05:35:11.000Z. https://etherscan.io/tx/0x0ae5251851762cf64c530a61c348b3d52d7979d048130bf5fbd9d3bdca7160fb

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-AGR-26-120413-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: UplitAU Pty Ltd (ABN 91 680 646 495), directed by Dr Dmitri Tcherkas, operates DEMI Capsule and the DEMI Central Registry under obligations to service providers and users, grouped across security, continuity, payments, regulation, and user duties. The registered signed agreement prevails.
Propositions: O1 · UplitAU · store all API and service keys only as encrypted Worker secrets · ongoing · evidence: configuration audit or registered secrets inventory | O2 · UplitAU · maintain offline backup of all keys · ongoing · evidence: registered backup record | O3 · UplitAU · never share the owner key with any third party · ongoing · evidence: PARTY confirmation | O4 · UplitAU · maintain Worker code integrity for continuity · ongoing · evidence: registered code snapshot | O5 · UplitAU · perform KV store exports for continuity · ongoing · evidence: registered export logs | O6 · UplitAU · migrate from workers.dev links to own domain · date not stated · evidence: WEB — public URL inspection | O7 · UplitAU · process card payments via Lemon Squeezy rail · ongoing · evidence: WEB — Lemon Squeezy transaction records | O8 · UplitAU · operate private ETH payment rail · ongoing · evidence: ON-CHAIN if blockchain address stated; address not stated in passage | O9 · UplitAU · record AUD valuation of crypto receipts on the day for tax · ongoing · evidence: registered valuation records | O10 · UplitAU · resolve AML/CTF question R1 · date not stated · evidence: registered compliance determination | O11 · UplitAU · comply with privacy obligations · ongoing · evidence: PARTY or registered privacy policy | O12 · UplitAU · comply with scams framework · ongoing · evidence: WEB — published framework adherence | O13 · UplitAU · comply with ASIC regime · from 9 April 2027 · evidence: WEB — ASIC registrati
Constraints: Providers' published terms (Anthropic, OpenAI, Cloudflare, Lemon Squeezy, Etherscan, CoinSpot, MetaMask, Commonwealth Bank) prevail over this register where they conflict. O13 (ASIC regime) activates 9 April 2027; no earlier compliance date stated. O8 uses a private ETH rail but no blockchain address is specified in the passage, preventing ON-CHAIN verification. O10 (R1 AML/CTF) is explicitly unresolved with no resolution date stated. Squarespace and Internet Archive terms are not yet reviewed, creating unresolved dependency for any obligations touching those services. AUD valuation (O9) must be captured on the transaction day for tax purposes. No fee amounts or currency amounts are stated in the passage.
Mechanisms: O1: REGISTERED | O2: REGISTERED | O3: PARTY | O4: REGISTERED | O5: REGISTERED | O6: WEB | O7: WEB | O8: PARTY (no blockchain address stated in passage; ON-CHAIN not available until address registered) | O9: REGISTERED | O10: REGISTERED | O11: REGISTERED | O12: WEB | O13: WEB | O14: REGISTERED | O15: PARTY | O16: REGISTERED
Boundaries: The signed and registered DEMI Capsule Unified Obligations Register v1.0 dated 2 October 2026 governs all obligations listed herein. An AI assistant using this record may only flag obligation status as on track, due soon, overdue, evidence missing, or mismatch; all decisions, remedial actions and determinations remain with the parties. This record is not legal advice. GAPS: O6 has no due date for domain migration; O8 lacks a blockchain address preventing ON-CHAIN verification; O10 (R1 AML/CTF) is unresolved with no resolution date or responsible party detail beyond UplitAU; O11 privacy obligations are not individually specified; no fee amounts or currency amounts are stated for any payment obligation; Squarespace and Internet Archive terms are unreviewed, leaving obligations touching those services undefined; O3 and O15 lack documentary evidence pathways beyond PARTY confirmation.
Core SHA-256: 86c67898a9973060742579d496b1b9ec1ca3746e2ed4bb381e6f15accbedf4fb

D. ASK THE REGISTRANT FIRST
- What do you want to do with this work now?

E. WHAT YOU CAN OFFER (Agreement or contract)
1. Verify the file against the File SHA-256 before anything else.
2. List each obligation in the Core with its method of proof: REGISTERED (a later document registered with this code as Parent), WEB (public information), ON-CHAIN (a blockchain event), PARTY (only the parties can confirm).
3. Report each obligation as on track, due soon, overdue, evidence missing or mismatch. Flag only; the parties decide. This is not legal advice.
4. Register the report, if the registrant wishes, with this code as Parent.

F. LINKS
Public page: https://registry.demicapsule.com/registry/UPL-AGR-26-120413-EN/index.html
Certificate: https://registry.demicapsule.com/certificate/UPL-AGR-26-120413-EN
Record (JSON): https://registry.demicapsule.com/registry/UPL-AGR-26-120413-EN.json
Independent archive copies: https://web.archive.org/web/*/https://registry.demicapsule.com/registry/UPL-AGR-26-120413-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