Versioned text source
Provenance-aware files with metadata, digital fingerprints, and a change log.
The correct option should be the easiest
A future space for trusted sources, APIs, testing tools, and integration documentation.
Status: portal and resources are under developmentTarget outputs
Our aim is to reduce duplicated work and risk. Instead of every team building its own source and verification method, it can integrate documented, trusted components.
Provenance-aware files with metadata, digital fingerprints, and a change log.
Documented queries for text, structure, and pages, with clear usage limits.
Libraries and examples in common languages to reduce integration and conversion errors.
Commands and automated tests that compare a product with the reference release before publication.
Clearly licensed resources with cross-platform compatibility tests.
A structured channel to report errors and track remediation and corrected releases.
No API or software package is available for public use yet. Links and licenses will be published here after technical approval is complete.
Understanding real-world use cases will help us build interfaces and outputs that teams can adopt.