What shipped, and what it proves.

A question asked in a customer's chat tool is resolved to exactly one installation, sent to an endpoint the vendor runs, and the reply is relayed into the same thread. Streaming and single replies both work: a streamed answer is posted on the first chunk and the same message is edited as it grows, rather than posting fragments or waiting in silence. An answer that fails partway keeps what arrived and appends the reason, and the vendor's own error text goes to their event log rather than into their customer's channel.

Every question carries that customer's own MCP endpoint and token, so the vendor's assistant can act inside the workspace with the customer's credentials, bounded by the package frozen at their install and by what they are entitled to. Conversation history is neither sent nor stored: a stable thread reference goes instead, and the assistant keeps its own memory against it.

An assistant Meetext runs, given the same per-customer endpoint as its tools, so it answers from capabilities the vendor approved and the customer bought rather than from general knowledge. The name on the bot is still the vendor's.

A control on the product page sends a question down the real path and returns the reply here instead of posting it into a channel, reporting the latency, whether the answer actually streamed, and which customer's capabilities it was given. Two scripts stand in for a vendor's product and a vendor's assistant, so the whole chain runs locally before any OAuth application exists.

Every page and every main component carries an icon that says, in plain words, what the thing is and what to do with it. Written for somebody who has not yet met the words entitlement, canary rotation or confounded incident, which is most people on their first day.

Salesforce, ServiceNow, Atlassian Cloud and HubSpot, each with its own fake provider and lifecycle tests. Every one is held to the same contract as Slack and Microsoft, and each forced out a platform truth worth encoding: Salesforce hides fields by omitting them, ServiceNow has no revocation endpoint, an Atlassian site scope is not project access, and a HubSpot scope change makes every existing customer reinstall.

Four facts that used to collapse into one word now stay apart: whether an adapter exists, whether it passes against a simulator, whether real credentials have gone through it, and which parts of the lifecycle were exercised for real. Nothing may be called available without dated real-provider evidence, which is why all seven destinations read preview.

Running discovery against a real FastAPI document, the public Swagger Petstore and a real repository found what the suite could not: a $ref resolver that counted structural depth and refused 100 of 108 operations, a repository scanner offering authorization as a capability input, and refusal messages carrying raw validation-library output into a developer-facing report.

The privacy policy states what is deliberately not stored, including capability argument values and raw provider messages. The terms say plainly that there is no service level agreement yet rather than publishing a number with no operating history behind it.

A document whose uniqueness mattered gets an id derived from the fields that made it unique, so a second write with the same identity updates one document instead of creating a duplicate.

Ids are time ordered and monotonic within a millisecond, so two facts recorded in the same instant read back in the order they happened rather than reshuffling between reads.

Sign in, create an organization, and reset a password in one page. Organization names are validated rather than silently slugified into a counter.

Observed by Meetext, derived by Meetext, asserted by the vendor, or observed by the customer. Every renderer preserves the distinction, so an inference can never be read as an observation.

A sign-off covers the exact posture the reviewer saw. When the posture moves, the review goes back into renewal instead of quietly covering whatever shipped next.

Share links are hashed, expiring, and revocable. Revoking one kills the page without touching the snapshot it pointed at.

Who owns the next move is a different question from what is blocking progress, and collapsing them made a waiting customer look like a broken deployment.

Time nobody can account for is reported as unattributed rather than distributed across the parties. A coverage figure says how much of the total is explained.

A pattern is only reported as verified once it has been checked at least five times and held at least eighty percent of them.

A client's own connector check verifies that it can reach the endpoint and list tools. That is the protocol layer and nothing more. It used to be reported as health.

An outage at Slack degrades the deployment and says so, rather than reporting the vendor's own product as broken.

A deployment is healthy when a real read capability ran against the vendor's system, not when a token exists.