See verified release history and prospective work on one clear, accessible public page.
Added: Publish a server-rendered Product Updates page with stable release links and reviewed user-facing notes.
Improved: Make current and earlier releases discoverable through the site footer, canonical metadata, and public sitemap.
Accessibility: Distinguish shipped and planned work with headings, labels, structure, and text rather than color alone across supported layouts and themes.
Privacy: Keep release and roadmap content free of accounts, personal data, analytics, remote requests, and new client-side dependencies.
Documentation: Group prospective work as Next, Later, and Exploring with a visible notice that priorities, scope, order, and availability may change.
Planning notice: Plans describe current priorities, not promises. Scope, order, and availability may change as testing, security, accessibility, and student needs evolve.
Next
The project's current priority after this page launches.
Phase 6: Visual finding map
In development
Explore returning a safe rendered view of a submitted document with markers showing where detected hidden text, metadata, or related findings were located.
Considerations: Markers must distinguish exact coordinates, approximate page or region locations, and structural locations such as document metadata without inventing visual precision.
Later
Valuable work that is not yet scheduled.
Evidence-aware version comparison
Planned
Improve before-and-after review so findings can be described as added, removed, moved, or changed with honest uncertainty.
Considerations: Comparison language must not imply certainty when file formats or extraction methods limit the evidence.
Educational sample lab
Planned
Provide synthetic files that demonstrate hidden-content patterns and common benign explanations.
Considerations: Samples must be synthetic, clearly labeled, and safe to download and inspect.
Exploring
Ideas being researched or tested before a commitment is made.
Local review timeline
Under consideration
Consider a browser-local sequence of review actions that can be included in an evidence packet.
Considerations: The concept must not introduce accounts, server persistence, or claims about when a file was received.