“DEMI_Capsule_CARD_v2_5 is a compact single-file registration interface that accepts one input file and returns one timestamped code plus two downloads, registering contract obligations, statements, and idea files without publishing abstracts or freezing extracts unless AI analysis is explicitly requested.”
PropositionsT1: One-file-in, one-code-out registration with a public timestamp attached | T2: Registers contract obligations, statements, and files of ideas | T3: Produces exactly two downloads, not six | T4: Does not publish abstracts; does not freeze an extract unless AI analysis is requested | T5: Worker anchors each registration itself; Etherscan link shown immediately or noted as in-flight on the certificate | T6: Sealing is chosen before payment; owner key shown once with a copy button, controls visibility of sealed record | T7: Manifest timestamp is taken from the Worker, not the browser clock | T8: Automatic blockchain anchoring since Worker V5.8; certificate shows 'awaiting confirmation' until mined, then shows block | T9: v2.5 sends chosen Kind to the Worker; passage hint and Copy-record AI instructions follow the Kind
ConstraintsRequires Worker V5.7 or later; CONFIG.WORKER_V57 must remain true while V5.7+ is deployed — set false only on rollback, which re-enables compatibility mode, disables sealing, requires a passage, and displays a notice | Automatic anchoring requires Worker V5.8+ | Kind-shaped Core requires Worker V5.8.2; older Workers silently ignore the Kind field | ANCHOR_HOURS and 'due within N hours' promise are removed and must not appear in EN/RU instruction blocks | Browser clock must not be used for manifest timestamps | Manual anchoring console remains a fallback
MechanismsT1: Verify single-file input produces exactly one registration code output | T2: Submit each of the three content types and confirm successful registration code is returned | T3: Confirm download count equals two per registration | T4: Confirm no abstract is published and no extract is frozen without explicit AI analysis request | T5: Check Worker response for Etherscan link; if broadcast in flight, verify certificate still carries the link | T6: Confirm seal option is presented before payment step; confirm owner key appears once with copy button and controls record visibility | T7: Compare manifest timestamp against Worker-side time log — must not match browser clock when they differ | T8: Poll certificate row for 'awaiting confirmation' state then block number after mining; verify no re-issuance needed | T9: Send a registration with a Kind value using Worker V5.8.2 and confirm Core is Kind-shaped; repeat with older Worker and confirm graceful ignore
BoundariesDoes not publish abstracts | Does not freeze extracts unless AI analysis is explicitly requested | Does not use browser clock for timestamps | ANCHOR_HOURS / hourly promise construct is fully removed and out of scope | Six-download behaviour of predecessor is removed | Passage is not required in normal (non-rollback) mode | Kind support in Core is conditional on Worker V5.8.2 and not guaranteed on older workers | OPEN: Exact format and schema of the Kind-shaped Core is not specified in the passage | OPEN: Content of the two downloads is not described | OPEN: Behaviour when blockchain broadcast fails entirely (beyond in-flight state) is not addressed