Govern a multi-agent topology lifecycle

Why it matters

A multi-agent release is a set of agent versions with shared costs; without a recorded mapping and metering, no one can say which release or tenant spent what.

What to practise

Inventory prompt agents and their immutable versions through AIProjectClient, then promote a scanner, reviewer, and orchestrator as one release after a promotion gate. Record the mapping from logical topology version to Foundry versions. In a Cosmos DB usage registry, enforce a 60-request per minute limit and a 1,000,000-token monthly quota in one ETag-conditional update, meter usage, and allocate estimated USD charges to a tenant and cost center. Finally, retire the disposable scanner version, after confirming that each failed gate, such as a remaining consumer or a short notice period, denies the deletion.

How it fits

Quotas, metering, and chargeback evidence that differs from an invoice are 3.3.7. For 4.3, the release mapping and gated retirement are 4.3.5’s promotion-through-retirement lifecycle.