Glossary of embedded infrastructure terms

White label: the full surface runs under the partner brand and domain, and the underlying provider is not shown to the end user unless the partner chooses to name it.

Embedded components: prepared surfaces, such as a screening result, an evidence pack or an investor portal, rendered inside the partner's own interface and inheriting the partner's identity session.

API deployment: the partner builds its own experience and calls the layer for assessment, evidence, workflow state and reporting.

Data exchange: the partner's own data is an input to the layer and is attributed as a source wherever it supports a finding.

MCP for partner agents: a tool interface through which a partner's own assistants and agents read and act on scoped tenant records under explicit permissions.

Mandate: a written statement of what a tenant invests in, at what stage, in which jurisdictions and under what constraints. It is the basis of assessment, which is why two tenants can receive different reasoning on the same opportunity.

Mandate-aware screening: assessment against the tenant's own mandate rather than a shared taxonomy or a platform-wide filter.

Reasoning retention: keeping the inputs and the logic that produced an assessment, so it can be reviewed later rather than reconstructed from memory.

Rubric: the structured criteria applied to a given asset class or sub-asset class. Coverage across the platform is 68 native asset classes and 314 sub-asset class overlays across 56 of them.

Finding: a structured claim extracted from source material, as distinct from a narrative summary.

Attribution tier: how a source behind a claim was established. Self-reported means it came from the subject. Verified means it was checked against an independent source. Triangulated means several independent sources agree.

Evidence pack: the set of findings, sources and attribution tiers assembled for a decision, retrievable later.

Provenance: the chain linking an output back to the records and actions that produced it, including actions taken by agents.

Tenant: the isolation boundary. Mandate, documents, records and decision history belong to the tenant that created them, and nothing is pooled across tenants to build a shared model of a partner's flow.

Client-level isolation: separation between a partner's own clients inside the partner tenant, where the partner requires it.

Residency: the hosting jurisdiction selected for a tenant where residency obligations apply.

Retention configuration: the per-tenant rules for how long records are kept and how they are deleted.

Export: the ability to take records and decision history out of a tenant, agreed at the start of an arrangement rather than at the end.

System of record: the system treated as authoritative for a given record. In an embedded deployment this is often the partner's, with the layer reading and writing back.

Coordination rather than performance: where a settlement, custody, registry or administration step belongs to the partner or a licensed third party, the layer records and coordinates it rather than performing it.

Software boundary: Reuben AI does not hold client money, settle transactions, distribute securities, or act as a licensed administrator, trustee, custodian, registry, adviser, auditor or tax agent, and holds no certification it has not obtained.