| Core Statement | The DEMI Central Registry is production-ready for integration design, distinguished not by blockchain timestamping alone but by combining low-friction registration, local file hashing, minimal content custody, a stable machine-readable reference, an AI-readable semantic layer, and lineage continuity across outputs. |
| Propositions | Two payment rails—a conventional Card rail and an ETH-payment rail—have both been successfully exercised against the same DEMI Central Registry architecture, each producing a UPL Registry Code, Activation Reference, SHA-256 evidence, five-part Conceptual Core, machine-readable Registry record, and an Ethereum Registry anchor. |
| Constraints | The overall assessment is 8.8/10, with unresolved variables including external demand, independent security assurance, distribution, support burden, platform review, and the cost of production-grade integration. |
| Mechanisms | Registration operates through local file hashing and minimal custody of source content, yielding a stable machine-readable reference and an AI-readable semantic layer that supports continuation of work with traceable lineage to later outputs. |
| Boundaries | A publishing company evaluating DEMI need not adopt blockchain payments or store manuscripts in DEMI; an initial evaluation can be read-only and limited to provenance and reference retrieval. |
| Registered file | DEMI_Capsule_Plugin_MCP_Integration_Specification_v1.0_2026-09-30.docx |
| File SHA-256 | 9f285343c9364b1ae39971798a51ab628fbee50469b6906e592aa12c025f45a5 |
| Analysed extract SHA-256 | fe87a8c482856470b5a5498d985d56a909c4204b84796ad9a42479ab9c346fe5 |
| Payment | Ethereum · 0x11e24e458d5c6841ba65df89219c48c6563bd568fec52491dedcb73189765b6f View on Etherscan → |
| Registered at (UTC) | 2026-09-30T23:36:23.601Z |
| Registry anchor (Ethereum) | block 26093620 · 2026-09-30T23:36:35.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-925132-EN |
| Activation Reference | DEMI:1042:UPL-TECH-26-310441-EN:Z |
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. photo_of_Skydle_Sep7_2026.jpg 350738 bytes SHA-256: 9b1371d666775ddc9a7d508c0a81fa8e13efa255eb68981b5f4a649ae31d4887 |
| 2. video_Two-Directions_of_Waves.mp4 1281022 bytes SHA-256: 877cf479b18ac676a7de4dd8fd034e78da00078990b1188669aac17cec7768f2 |
| 3. DEMI_Capsule_Reassessment_OpenAI_Plugin_Prospects_2026-09-30.docx 43311 bytes SHA-256: b890d586594fc1ec2e41e2ceab79e5571d706d757584c3a15c102e0c6b818dc5 |
https://demi-proxy.flat-bonus-ffc5.workers.dev/registry/UPL-TECH-26-310441-EN/index.html
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-01T07:35:52.870Z · rebuilt each time it is opened; a saved copy shows the record as it stood at that moment