Disclosure Boundary
These docs define the connect contract for Legate. They answer how do I connect and call? They do not answer how does Legate decide, score, or police internally?
Link this page from every major section. Forward it to security and legal reviewers without edits.
Purpose
Integrators and operators need stable vocabulary: transports, auth at the interface, actor boundaries, write sequence names, public errors, and maturity labels. Judgment logic, policy source, and proprietary architecture stay private.
Published
- Product identity: Legate is Stratum’s production MCP envoy; unit of record = channel-scoped shared ledger state
- Integration Surfaces maturity matrix (Live / by arrangement / contract-only)
- How to obtain a connection (wizard / deeplink / Agent Card / short-lived token) with no key export
- Transports: remote HTTPS (Streamable HTTP) and local stdio
- Auth at the interface: Bearer JWT, audience/resource binding, scopes → packs, write consent claim
- Actor boundaries: integrator, operator, external signer
- Write path as a client sequence: simulate → prepare → external sign → submit_signed
- Agent Card well-known path (high-level discovery)
/healthvs/readysemantics for callers- Public error categories and synthetic examples
- Stable public pack names partners are allowed to call
Never published
- Guard / scoring engines, trust maps, thresholds, or interrupt models
- Policy source (allow/deny rule files) beyond “scope ⊆ granted packs”
- Mandate / approval business rules that decide when prepare is allowed
- Internal architecture: component graphs, middleware order, caches, event workers, rate-limit algorithms
- Audit / SIEM internals beyond the existence of digests for actor / tool / args / status
- Deploy-plane secrets: compose internals, VPC layout, image digests, BFF minting implementation
- Exhaustive proprietary tool catalogues and unpublished admin ops
- Real client data, tokens, JWTs, or live Agent Cards
- Ledger-stack product brand names that are not part of the public Stratum / Legate vocabulary
Three-line test
Before shipping any page:
- Describes the interface an actor interacts with, not how conclusions are reached.
- Names states and signals, not admission or blocking rules.
- Explains how to connect and verify the connection contract, not production judgment processes.
Author rule: If a sentence explains how Legate decides rather than how the client connects and what interface to call, cut it.
Public vocabulary
| Prefer in public docs | Avoid in public MDX |
|---|---|
| Stratum peer / channel-scoped shared state | Competing ledger product proper names |
| Signing material / connection credentials | Wallet-export framing |
legate.read / legate.write | Internal pack aliases not issued to partners |
| Ops capabilities by arrangement | Public admin API dump |