Roadmap.

Intent of this register

The roadmap describes anticipated additions to the office's instruments and surfaces. It is not a service-level commitment; each item is anticipated in good faith, with completion governed by founder time and customer demand. Items are listed where they are presently believed to fall, and may be advanced, deferred, or withdrawn as conditions warrant.

In the present quarter (Q2 2026)

The following instruments and surfaces are registered as shipped or imminent in the current quarter.

• Standalone independent verifier (shipped — see /verify-js.html).
• Model Context Protocol server (shipped — see /mcp.html).
• Anchoring from the iOS share sheet (shipped — see /ios.html).
• HMAC-signed webhook delivery on anchor and Bitcoin-commitment events (shipped — see /docs/webhooks.html).
• Printable single-page receipt instrument (shipped).
• Vault export in JSON-LD shape for downstream verifiers (shipped).
• Account-level webhook management (shipped).

In the next quarter (Q3 2026)

The following items are anticipated within the next quarter.

• A browser extension for Chrome and Firefox, registering a file by right-click from the surrounding page.
• A watch-folder application for macOS, Windows, and Linux.
• An Editorial tier at ninety-nine dollars per month, intended for teams of up to five, with a batch endpoint and a per-account audit log.
• The independent verifier in additional languages, namely JavaScript, Go, and Rust.
• A "Gift a Pack" referral instrument presented on receipt pages.
• Comparison pages with adjacent timestamping conventions.
• Per-account anchor-count milestone notices at the tenth, fiftieth, one-hundredth, and five-hundredth anchor.

Within the year (Q4 2026 — Q1 2027)

The following items are anticipated within the present year.

• Private-calendar instances for enterprise customers.
• A premium direct-Bitcoin commitment path for time-critical use.
• A multi-signer receipt mode for editorial workflows.
• Native iOS and Android capture applications.

Long term (2027 and beyond)

The following items are anticipated on a longer horizon.

• Verifier and protocol bindings in further languages.
• Privately-operated regional calendar nodes.

What is deliberately not on the roadmap

Certain directions are excluded by design. The office does not pursue AI-content-detection claims; authorship attestation beyond date of existence; liability-bearing service-level commitments; or cryptocurrency yield or token-issuance mechanisms. These exclusions are constitutive of the instrument, not a function of present scope, and are not anticipated to enter the register.

Revision policy

This page is revised quarterly. Each revision is itself registered to the chain; the prior revision remains independently verifiable.