Public Roadmap

Anchor commitments

Regulation

CMS-0057-F full-compliance deadline: January 1, 2027. Tessara's product roadmap is sequenced to land core capability ahead of enforcement.

Drift Index cadence

Quarterly public benchmark. Anonymized cohort scoring. Methodology published. Independently re-runnable from public FHIR endpoints.

Verification artifact cadence

Every audit-customer pilot receives one signed compliance verdict per check cycle (configurable; default weekly during enforcement).

Update cadence

This page is reviewed and updated quarterly. Material shipped against commitments is appended to the resolved-decisions ledger in tessara-facts.yml (canonical, public-repo).

Drift Index — 4-quarter commitment

The Drift Index is Tessara's quarterly public benchmark of US payer FHIR API conformance under CMS-0057-F and its predecessor CMS-9115-F. We commit to the next four quarterly releases.

Product — what we're shipping

Live today

• Tessara CLI — baseline / probe / check / evidence commands. Patent-pending 4-level Merkle hash tree over Structural Contract Models. Ed25519 signed verdicts. SQLite evidence chain with mandatory write verification.
• Dashboard authentication hardening — Stage 2.2.13g shipped (audit hash chain, Origin-header CSRF defense-in-depth, global rate-limit lockout, JTI revocation). See public commit history under github.com/Tessara-us.
• Zero-PHI architecture — metadata-only probes against CapabilityStatement endpoints. No payload retention.
• FHIR IG ingestion — real ImplementationGuide package support (.tgz). RFC 8785 JCS canonicalization.

Targeted next 90 days

• Status page at status.tessara.us — independent uptime monitoring (instatus.com or equivalent).
• Drift Index Q3 2026 full release — first publicly published quarterly benchmark.
• BAA execution path — counsel-reviewed BAA template ready for first pilot signing. Draft published today. BAA template →
• SOC 2 Type I engagement — begins with first pilot revenue. Honest milestone, not pre-revenue burn. SOC 2 posture →

Targeted Q4 2026 - Q1 2027

• OSS drift-bench harness — independent verifier tool letting anyone re-run Tessara's measurements against any public FHIR endpoint. Gated on patent FTO clearance.
• Provider Directory support — CMS-9115-F's Provider Directory API coverage (the fifth API in the CMS-0057-F + CMS-9115-F regulatory bundle).
• CMS-0057-F enforcement-window coverage — full four-API drift detection (Patient Access expanded, Provider Access, Payer-to-Payer, Prior Authorization) ahead of enforcement (2027-01-01).

What we won't do (scope honesty)

Procurement officers see vendor scope creep as a risk signal. The inverse — explicit scope limits — is a credibility signal. Here's what Tessara is not.

• Not a SIEM, log aggregator, or compliance certification service. Tessara produces signed evidence of FHIR API conformance drift. We don't replace ONC-certified conformance testing (Inferno, Touchstone), and we don't issue compliance certifications.
• Not a payload data processor. Tessara stores structural metadata only. No PHI traverses Tessara infrastructure. BAA template available because integration context may still be HIPAA-regulated even when our specific data flow is not.
• Not a scan-without-consent service. We do not scan payer endpoints without explicit customer authorization. Public Drift Index measurements are taken from documented public endpoints (CMS SMA Directory + payer-published metadata URLs).
• Not a legal-advice provider. Tessara verdicts identify drift for further investigation. They are not substitutes for legal or regulatory advice.

How to read this roadmap

Dated commitments use directional language ("targeted for Q3 2026", "begins with first pilot revenue") because Tessara is pre-revenue and runway is finite. Definite-date claims are reserved for regulatory anchors (CMS-0057-F enforcement 2027-01-01) and shipped artifacts (commit dates, audit reports, published Index entries).

Every commitment listed here is backed by an entry in tessara-facts.yml (canonical, machine-readable, in the public github.com/Tessara-us/Tessara repository) or by a publicly-pushed commit. If a commitment slips, the slip will be recorded — not erased — in the resolved-decisions ledger.

Sales/marketing collateral that conflicts with this page is wrong. This page wins.