Technical overview

Product model

Electronic Registry is a public registry for exact-file records, Public References, updates, and visible history. The product is task-based: users create records, add related entries when needed, and allow others to verify matching records later.

Record model

The basic browser flow identifies one exact file locally and records the resulting file hash. The file itself is not uploaded in this flow. A matching file can later be checked against the public registry record.

Updates and history

Registry records cannot be edited or removed. When something related needs to change, a new entry is added instead of changing the original record. This creates a public record history that can be verified later.

Verification flow

Verification starts from an exact file or verification code. The result can show a matching base record, when it was created, and related Public Reference, Research, Audit, or other registry entries when available.

Public and private data

Registry records are public. Files are private unless the user chooses to share them. Dashboard labels, private notes, account information, and similar user-specific organization data are off-chain/private product data and are not public registry records.

Technical details

Technical users can inspect the file hash method and chain details where available. SHA-256 may appear in technical details because it is the hash method used by the current browser flow.

Trust boundary

Electronic Registry can show that a matching public record exists, when it was created, and whether related entries were added later. It does not decide truth, ownership, authorship, originality, legality, compliance, certification, platform approval, or official approval.

Future API direction

Future API access may allow external systems to create records, add entries, and verify records programmatically. API behavior should follow the same product rules as the browser: verification should remain free, failed writes should not consume units, and public registry data must stay separate from private dashboard/account data.

The website, dashboard, and human-readable read models are product services. Public registry records and chain details should be documented separately from product-service availability.