Meetings and documents

Some of the most decision-dense material in an organization has no integration to connect: the recording of Tuesday's call, the signed contract, the email chain where the commitment was actually made.

These arrive through admin-authenticated relays rather than a toolkit.

Meetings

A recording bot joins the call, and the transcript comes back as a source event with a resolvable link to the recording.

Meeting bots are metered, because each one spends third-party recording minutes and that cost is real rather than notional. Your allowance for the period, and how much of it is left, is on Settings → Billing.

Documents

For contracts, policies, specifications and email. Storage is on disk by default, or in an object store when you configure one.

Two settings, both under Settings → Documents, and both set once: the public origin evidence links are served from, and optionally the object store uploads are kept in.

The public origin matters: a document with no reachable link is a document Memnox rejects, exactly like an unevidenced meeting.

Both are always tainted

The consequence in practice: a decision extracted from a contract still needs a human to approve it, and an agent whose session read one needs a human before any privileged action. Both of those are the correct outcome.

Derivatives ending in _enriched inherit the classification, so summarizing a document does not clean it.

Evidence is still mandatory

Unevidenced meetings and documents are rejected at the normalizer. There is no relay that stores content with a blank sourceRef, because one unevidenced record makes the whole graph a set of assertions rather than citations.

Authentication

Both relays require an admin bearer token, not a workspace credential. They accept arbitrary content and attribute it to your organization, so the bar is deliberately high.

Never put an admin token in a client-side integration. Relay from a server you control.