Verifiable development changes with clear delivery boundaries.

Collection and administration no longer share a public entry point

The collection hostname continues to expose only the script and event endpoint. Administration uses a separate hostname with additional authentication and is not exposed to search engines.

Check security and observability before release

High-risk production dependency vulnerabilities, collector rate-limit logs, canonical URLs, and browser security headers are all covered by versioned checks instead of ad hoc server operations.

Information is no longer scattered across product pages

Resources are now part of the main navigation. The changelog reads continuously, documentation follows task paths, and community and help pages provide a clear next step.

The existing system architecture content remains under Resources, and the old URL redirects to the new architecture page.

Keep delivery status honest

Public installers remain governed by the status shown on the download page. Development updates are not formal releases, and development builds are not presented as downloadable versions.

Both modules work independently

Use IM alone when you only need communication, or Agent alone for tasks, tools, and results. Neither requires the other to remain running.

Linked modules exchange only explicit data

When linked, IM and Agent exchange messages, task context, progress, approvals, and results through explicit interfaces. Neither copies the other module’s internal state.

macOS first, without inventing download URLs

The platform matrix clearly identifies signing, schedule, and public availability. Until a formal build is ready, the page will not provide nonexistent dmg, pkg, or zip links.

Usage modes and procurement paths stay separate

Independent and linked Agent and IM modes belong in the client documentation, while team buyers continue to pricing and private-deployment pages instead of sharing an ambiguous download button.