Catalog: Agents

Jobs to be done (optional)

The user journey story will eventually be stuff like:

• do any agents handle payments?
• Are any agents duplicating efforts?
• Are any agents ineffective?
• Are my agents healthy?

But we're not quite there yet. These will be the use cases Catalog solves and the add it provides on AIGW (AIGW is for the builders, Catalog is for the platform eng whose job it is to answer those questions above). semantic questions

With this first milestone: think centralized view for a platform owner.

Definition of done

• Need to note what is autopulled from well known (so if you change that, it will change things on the Catalog end, like changing the name)
• AIGW is the recommended path
• strong focus on automation (how would they get their agents in here in an automated fashion?)
• Limitation??? one version, but will be included in the future

Information

PRD: https://docs.google.com/document/d/18pq1PTRQl0VFZQtQl3eAY-Ki5LJjWzOzjBbiRvqFfqs/edit?tab=t.0#heading=h.sdya2o3myu00

Due date (optional)

Size

Start by reviewing the linked PRD and the issue's Catalog and AIGW descriptions. Identify the documentation scope for the first centralized platform-owner view, including what is autopulled from well known, the recommended AIGW path, automation, and the one-version limitation. Done means those boundaries and the resulting Catalog guidance are documented.