Define capability, territory, delivery authority, certification evidence, support responsibility, data access and exit obligations before customer work begins.
No organisation is listed as an approved partner without evidence.
Register versioned OpenAPI or AsyncAPI contracts, scopes, tenant bounds, correlation, idempotency, rate, cost, monitoring, replay and suspension authority.
Write-back remains disabled by default.
Approve tools by exact purpose, data class, input/output schema, human gate, cost, audit and kill switch before any registered agent may use them.
A tool cannot expand the agent's underlying authority.
Separate route
Submissions remain in this synthetic prototype only. A production process would require due diligence, agreement, access boundaries, delivery RACI and evidence review.
Form LOS-PARTNER-V1.0
Purpose: respond to this partner-governance enquiry. A required service response is separate from optional marketing.