TARE wordmark
Back to home

Design partner access

Release notes and known limits

TARE is available to design partners with an explicit support surface and limitations. This page separates current release evidence from roadmap work so security, scientific, and procurement reviewers can plan validation honestly.

Design partner release posture

Supported means a covered design partner path with release gates, not a blanket commitment that every lab workflow, instrument, validation packet, or outage procedure is finished.

Current

Design partner support surface

Supported design partner paths cover identity, RBAC, inventory, ELN records, SOP publication, custody, evidence attachments, billing controls, and admin operations health.
Current

Release gates

Supported features are backed by documented release gates, access-control review, public-claim checks, and production-build validation.
Current

Design and recovery evidence

Desktop and mobile review evidence covers public and authenticated routes, including recovery states and dashboard empty states.
Current

Operational automation

Cron health, stale-state reconciliation, email/upload failure counters, and admin operations views are present for the supported maintenance path.

Known limits

What still needs validation or hardening

These limits are intentionally visible. They should be treated as validation planning inputs for design partners, not hidden implementation details.

Customer-specific validation is still required before regulated workflow reliance.
VECTOR, INTERLOCK, realtime relay, and hardware-control workflows remain experimental unless separately reviewed.
OpenAI Realtime voice sessions are optional experimental behavior, not part of the design partner support commitment.
Write-capable automation and hardware-control workflows require separately approved private scopes.
Suggested drafts summarize and route context, but human review remains authoritative.
Advanced instrument ingestion, retention drills, outage continuity, and deeper calibration packages remain active hardening areas.
Design evidence includes desktop and mobile review coverage across supported public and authenticated routes.

Not included in this release posture

  • Open public self-serve onboarding
  • Enterprise contract automation
  • Autonomous hardware actuation
  • Universal instrument compatibility
  • Formal customer validation packets

Review evidence

Engineering evidence is maintained in the full-platform audit register and validation reports. Customer-facing commitments should stay aligned to this page and the product maturity matrix.