Show your work on a site

You keep the agency site and the projects it writes about in makermap already. This is how the agent that builds that site learns what to put on it - and, more importantly, what to take off.

makermap publishes nothing. It has no public pages, no anonymous access and no themes. It records what you chose to show and answers questions about it; your agent, with your token, does the rendering.

1. The site is an ordinary product

There is no separate "site" entity. The agency site has tasks, decisions and releases like anything else you build, so it is a product - and every other product is placed ON it.

2. Mark what belongs there

Open a product and use On the site in the right-hand rail. Pick the site; the product goes into its portfolio section, and stays there until you take it off.

Placing and removing are yours alone. There is no tool for either one, on purpose: deciding what the world sees is not a decision to hand to an agent that is also writing the thing being shown. That single rule is why there is no approval step anywhere in this - the mark IS the approval.

3. Write the showcase text

Create a document with the slug portfolio-card inside the product. That is what a visitor reads.

It is deliberately NOT the product's summary. That field answers "why are we building this" for your team, and on a public page it reads as marketing while saying something you never meant to publish. When the card is missing, the answer says so in missing and puts nothing in its place.

4. Let the agent read it

get_site_updates is the one to poll. It reports removals as first-class updates, because a site that only ever hears about additions keeps showing what you withdrew - and nothing about that looks wrong from either end. It also reports edits to things already placed: a rewritten product does not change its placement at all, and its card is now out of date.

Delivery is at-least-once, so dedupe by id.

What the site never sees

health, stage and status are not in the projection. They are internal judgements computed from incidents and gates, and "Critical" on an agency portfolio tells a visitor something you did not mean to say. The projection is an allow-list, so a field added to products later is absent until somebody decides to publish it.

Scopes

site:read to read all three tools. site:write exists for the placement routes, which are refused to agents regardless - so a working site agent needs site:read and the scopes for whatever it reads through its own tools (documents:read for a blog post, say).