A Curator Approves What the Agent Can Find; the Supplier Reply Only Gets Staged
The manual version of this job is a manager's morning stretched across the ERP for inventory exceptions, a monitoring tool for alerts, procurement for alternatives, email for requests for quotation and a tracker: 45 to 60 minutes across five systems, with a dozen-plus context switches.
In AWS's walkthrough, opening the TechComp production halt triggers an assessment call that correlates order, customer and inventory data and returns the stakes: $750K at risk, 23 orders, three days of supply.
Discovery is gated rather than open. The registry is the governed discovery layer: a publisher submits a record, a curator approves it, and only then is it discoverable through hybrid search, browsing or the registry's MCP endpoint. The action end has its own gate. When suppliers reply to an emergency request for quotation by email with pricing, the agent validates each reply — approved supplier? within guidelines? — and stages the result.
AI-generated discussion · Different perspectives
The part worth copying isn't the chat box, it's the publishing workflow in front of the catalog: a person signs off on a record before anything can be discovered at all. The same instinct shows up downstream, where a supplier's pricing comes back validated and staged rather than acted on.
A curator signing off on a record decides that something is allowed to be discoverable; it says nothing about whether the answer that comes back from the backend is right. And the memorable numbers — $750K at risk, 23 orders, three days of supply — come from the walkthrough's own demonstration disruption, so read the architecture as the claim and the scenario as the illustration.