“AI assistants and users lose context across sessions and tools; DEMI solves this by assigning each work stage a unique registry code and adding a Vault that stores the exact registered file with fingerprint verification and configurable access control.”
PropositionsT1: DEMI assigns each work stage a unique code (e.g. UPL-TECH-26-310441-EN) that acts as a persistent, cross-platform address for the record. | T2: The DEMI Capsule plugin allows both Claude and ChatGPT to retrieve the same record using the same code. | T3: The DEMI Vault stores the exact registered file, verifies it by fingerprint, and rejects any differing version. | T4: Three access tiers are defined — Open (anyone retrieves and works from full text in-chat), On Request (owner-approved link, optionally after card payment, with no email disclosure), Closed (record only). | T5: The AI summary and registry record are always readable by anyone, at no cost.
ConstraintsVault pilot is tested but not live; launch depends on the Capsule plugin being publicly released. Email-request and payment flows are not yet built. A registry record proves a file existed at a given time but does NOT prove ownership or content truth. Access tiers are owner-selected. Expiring links are used for On Request access. Related security dependencies documented at UPL-STM-26-799109-EN.
MechanismsT1: Verify code format and that retrieving the code returns correct metadata (stage, registration date, parent stage). | T2: Issue the same code in a Claude session and a ChatGPT session; confirm identical record is returned by both. | T3: Upload registered file — confirm acceptance; upload altered file — confirm rejection. | T4: Set each access tier and test: Open — retrieve full text in-chat without auth; On Request — confirm owner notification fires without exposing email, link expires after use; Closed — confirm only record is shown. | T5: Attempt record and AI summary retrieval without authentication — confirm free access in all three tier states.
BoundariesOut of scope: proving file ownership; proving content truth or accuracy; email-request workflow (planned, not built); payment processing (planned, not built). Vault pilot exists but is not yet running. Plugin public release is a prerequisite for Vault launch. OPEN: What fingerprint algorithm is used? What is the link expiry duration? What payment providers or amounts apply? What SLA or uptime applies to the Vault? How are owner notifications delivered if email is not disclosed?
Files fingerprinted by 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.