# The agents do the work. Your team decides what ships.
*Platform*
> CommerceClarity Agent OS is the platform the company’s catalog agents run on, and it has four surfaces: Context, what an agent knows before it starts; Agents, the plan it builds from a target; Governance, the customer’s own rules turned into the standard every output is scored against; and Grid View, the catalog itself with every value the agents touched. Anything the checks cannot settle is held for a person to approve before it reaches a channel.
Four surfaces: what they know, what they do, what they pass, and where your team picks it up.
## Surfaces
### The agents start from what your company knows
context
*Context*
The agent reads all of it before it writes a word: your rules, your systems, and the market outside.
- Yours · Rules, glossary, attribute model, and the systems you already run.
- And what you do not control · Search demand, what the engines answer, and what a category must state.
### You give it the target. It builds the plan.
agents
*Agents*
Bring the number you are measured on and the date you need it by. The agent works out the steps.
- Fitted to one catalog · Same shape for everyone, your model inside.
- Human in the loop · What the checks cannot settle is held for a person to decide.
### Your rules become the standard every agent is held to
governance
*Governance*
Encoded once, scored on every output, and a person decides what the score cannot settle.
- Measured, not asserted · Every agent carries a quality target, and every output is scored on it before it moves.
- Explainable one value at a time · The rule it failed, and the sentence it would have written.
### The screen your team works in
gridview
*Grid View*
Your team goes straight to the values the agent could not settle, marked in the cell.
- The view is the export · Build it once, save it, and export it in the column order you set.
- A thousand rows in one gesture · Filter, select, and run an agent on the selection.
## Open it on your own catalog
Bring one category and the attributes you never got to fill. Half an hour in the platform beats a deck.
## Questions
### What is CommerceClarity Agent OS?
The platform our catalog agents run on. It has four surfaces: the context an agent reads, the plan it builds, the rules it is scored on, and the grid where your team reviews the output.
### Do we operate the platform ourselves?
No. We run it alongside your team, and a Retail Engineer brings agents live category by category.
### Does it replace our PIM, ERP or DAM?
No. The agents read those systems and write the finished record back. You do not migrate anything, and you keep one catalog.
### What stops an agent publishing something wrong?
Every value it writes is scored against your rules first. What clears the bar you set goes to the channel; anything the checks cannot settle is held with the reason, and a person decides. Every published value carries the rule it passed.
### How long before the first workflow is live?
Weeks. The first workflow goes live on one category, and the next starts from the records it built.
## Entities
## Sources
---
Canonical: https://commerceclarity.com/platform
Every page of this site is available as markdown: append `.md` to its path. Index: /llms.txt
](https://cdn.sanity.io/images/xd4hrbt2/production/d28affc652f461d768e312804e68de5ce65dead5-2880x1920.webp?auto=format){kind=link}
](https://cdn.sanity.io/images/xd4hrbt2/production/42732d07f4ed5cc491b58213f6b67668e37e6dd0-1254x970.webp?auto=format){kind=link}