Release and capability status

A visible state
for every claim.

This is a maintained product-readiness summary, not an automated uptime monitor. It describes availability boundaries without implying a service guarantee.

Product previewLast updated
Current release boundary

The bounded owner-operated core has a verified live workflow, interruption recovery, exact internal receipt and encrypted isolated database restore. External email and CRM delivery remain unconfigured. CPU inference is slow; no uptime, capacity or host-recovery guarantee is offered.

01

What is available to explore.

Available to explorePublic preview

Public product preview

The public presentation and synthetic workspace are available for exploration. Sample actions are simulated and do not contact external providers.

Explore the workspace
Bounded implementationRestricted operator access

Owner-operated core

Authenticated operations, text knowledge, three specialist roles, exact approvals and internal receipts are verified in a completed live workflow, including worker-interruption recovery. Access remains limited to the configured owner.

Read the guide
Planned capabilityConnector milestones

External delivery and synchronization

Mailbox sending, connected-drive synchronization, messaging and third-party CRM writes are not configured product capabilities.

See planned capabilities
Planned capabilityFuture service readiness

Public customer onboarding

Open registration, paid subscriptions, managed support and independent customer service guarantees are not offered by this release.

02

Progress is measured at the boundary.

Implementation evidence

Local and live workflow evidence

The local and live agency flows exercised source-backed drafting, exact approval and internal receipt creation. The live task recovered after a worker interruption; an encrypted off-host production backup passed a fresh isolated database restore.

Release evidence

Measured limits and remaining recovery work

The successful CPU workflow required about 14.5 minutes of model work. One successful run is not a reliability or capacity benchmark. Repeated evaluations, scheduled backup retention and full host recovery remain further work.

Operating boundary

No uptime or capacity promise

This page does not provide live health telemetry, incident notifications or an SLA. Model turnaround and operating capacity must be evaluated for the actual deployment.

03

How to read this page.

Does “available” mean the core is open to everyone?

No. Available describes the public preview here. The bounded operations core is restricted to its configured operator and is marked limited.

Are these real-time health checks?

No. These are maintained readiness notes. A successful page load does not prove every authenticated workflow or external dependency is healthy.

Where can I see what changed?

The changelog records product milestones and the guide explains current behavior. Neither creates an uptime, delivery or support commitment.

A considered next step

Inspect the experience, not just its status.

Read the workflow guide and explore the synthetic preview to understand the intended control and evidence trail.