Modern C++ core for embedding and verification.
The engine roadmap centers on invisible watermark embedding, robust decode behavior, and verification that is designed to survive more than perfect source-file conditions.
Roadscript and Cyphra are designed to make invisible authenticity usable.
Roadscript focuses on embedding invisible authenticity signals directly into media content. Cyphra is the user-facing verification experience designed to help people check whether media still carries a valid Roadscript signal and interpret what that result means in practice.
Roadscript + Cyphra
A content-layer system with a user-facing verification layer.
The current public site is a preview of a larger engineering and product direction. The core idea is not only to embed a signal, but to make that signal verifiable through workflows that feel understandable to real users and developers.
User-facing verification that translates technical results into a clearer product experience.
Cyphra is designed to present authenticity status, payload extraction, and verification feedback through a simpler interface, with a roadmap toward broader cross-platform access.
Workflow preview
Embed, share, verify, interpret.
The intended experience is straightforward: apply an authenticity signal, let the media move through the world, then verify and interpret the result through a product surface that is easier to understand than raw engine output alone.
Embed
Roadscript is designed to place an invisible authenticity signal into the content layer instead of relying only on external metadata.
Share
The media then moves through normal workflows such as exports, reposts, screenshots, and downstream distribution.
Verify
Cyphra checks whether the media still carries a valid Roadscript authenticity signal and whether the verification result is intact.
Interpret
The product layer is designed to present authenticity status and relevant details without expecting every user to think like an engine developer.
Engineering direction
Built around local-first verification goals and a developer-ready roadmap.
The current direction includes a modern C++ core, a local-first processing bias, a robust decode pipeline, and a CLI and SDK-ready architecture. Some product claims remain targets rather than final benchmarks, which is why this page stays explicit about roadmap language.
Local-first processing
Verification is intended to avoid unnecessary uploads wherever possible.
Sub-second verification target
Responsiveness is a product goal while benchmarks and packaging continue to mature.
CLI and SDK roadmap
The broader Roadscript ecosystem is intended to support both user-facing and developer-facing workflows.