“DEMI Capsule is a plugin that lets a registrant form a Conceptual Core from a supplied passage (without uploading the Main File) and receive an AI Package referral, then optionally extend and cross-check that Core across AI sessions via a Parent-chain registry.”
PropositionsT1: Plugin accepts a registrant-supplied passage and generates a Conceptual Core (set of Main File ideas) with AI assistance, no Main File upload required | T2: Plugin produces an AI Package — a referral to the registrant's preferred AI system's AI Assisted Work Area (AI AWA) | T3: Registrant may optionally share the Main File with any AI to form a fuller Conceptual Core, registered as a next-stage record linked to the earlier record as Parent | T4: Parent-chain structure preserves recorded conclusions across AI sessions, overcoming AI memory loss between sessions | T5: A second AI system can cross-check recorded statements against the Main File and identify unexamined evidence, assumptions or branches | T6: At registration only the fingerprint and timestamp are stored; the Main File is never uploaded or processed by the plugin's AI | T7: All decisions to register, share, use and publish belong solely to the human registrant; no AI holds keys, pays or registers
ConstraintsProtocol: v2 | Standard reference: UPL-TECH-26-882026-EN | Registry host: demicapsule.com | Plugins are under directory review; approval is not yet granted | Main File must not be uploaded or AI-processed at registration stage | Parent-chain record requires an earlier registered record to exist | Registrant must supply the passage; AI does not source it independently | No authorship or legal-rights claims are made by or through the system | Published text is not protected from AI by this system | No AI entity may act as registrant, keyholder or payer
MechanismsT1: Verify that Core extraction runs solely on the supplied passage — confirm no file upload path exists in plugin flow | T2: Verify AI Package is generated and routes correctly to registrant's chosen AI AWA | T3: Test next-stage registration by supplying a Main File to an AI, generating a fuller Core, and confirming the new record references the correct Parent record ID | T4: Test continuity by opening a new AI session, loading only the Parent-chain record, and confirming the AI can proceed from recorded conclusions without prior context | T5: Test second-AI check by having a different AI system compare registered statements against the Main File and list unexamined branches | T6: Audit registration data to confirm only fingerprint and timestamp are stored, with no file content | T7: Confirm system interface offers no registration, payment or key-management action to any AI agent
BoundariesOut of scope: authorship attribution, legal-rights assignment, protection of published text from AI use, plugin directory approval (pending review) | Not built: full Conceptual Core from Main File at initial plugin stage (requires optional registrant action) | Not claimed: that dual AI checks establish truth of a statement | OPEN: criteria and timeline for plugin directory approval; definition of 'fingerprint' method used at registration; what constitutes sufficient evidence for a second AI's cross-check to be considered complete