Roadmap

In beta now

The public beta focuses on File Record and Public Reference. Research and Audit are available as advanced beta workflows for structured public history.

• File Record: create a public record for one exact file.
• Public Reference: connect an already-recorded file to a public URL, DOI, article, report page, source page, or other public reference.
• Research: advanced beta timeline for ongoing research projects.
• Audit: advanced beta history for audit or review items.

In development

These registry layers show the direction of the platform but are not active public beta create or verify paths yet.

• Content Creator
• Content Origin
• AI Signals
• Promos & Giveaways
• Product Passport
• Contracts

Planned platform direction

Electronic Registry is designed to support multiple registry layers over time. New layers should only become public when they add clear value, have safe terminology, and preserve the same trust boundary: the registry records what was registered and when, but it does not decide truth, ownership, authorship, legality, compliance, certification, or official approval.

API direction

A future API may allow organizations and developers to create records, add registry entries, and verify records from their own systems. API access should preserve the same rules as the browser product: no charge for verification, no charge for failed writes, public records for registry data, and private dashboard/user data kept separate.

What will not change

• Records cannot be edited or removed.
• Updates are added as new entries.
• The file stays private unless the user chooses to share it.
• Verification does not decide truth, ownership, authorship, originality, legality, compliance, certification, platform approval, or official approval.
• In-development layers will not be treated as active beta paths until explicitly enabled.