STUDIO / FANSPINE / LIVE BACKEND
Agent governance
Software agents now move sponsor budgets and issue offers. This page shows the leash: the cap each agent works inside, the point where a person must approve, and the record of every decision. Synthetic data, labelled as such.
Each row is one decision: what an agent or job tried, the limit it faced, and what happened.
Loading the governance record…
Try it
Make the media agent ask for a large move, then approve it as the commercial director.
Each click writes real rows to the log above. Keep asking and the agent will eventually hit its cap.
How this is measured
What a cap is for. A cap is the most an agent may spend in a day or a week. It turns “trust the software” into a number you chose, and an approval threshold sends the larger moves to a person before they happen.
What the log proves at renewal. A sponsor can ask what the agent did with its money. Every action, including the ones that were refused, is one row with the cap and the spend at that moment. Rows are never edited or removed, so the record is the same one you saw at the time.
Why the site's own jobs are in the same log. A record that covers only the agents hides the people and scripts that act beside them. Scheduled jobs write here too, so one page shows everything that touched the operation.
How the numbers are counted. Spend in the period adds up allowed and approved amounts since the start of the day or week (UTC). Checkout rate is the share of sessions with a purchase, split by whether the session came from an agent. The AI-made share is assets marked as generated, and how many of those are disclosed. All figures are read from the backend tables when the page loads.
Keep going
What this shows a club: an agent can spend your sponsor's money only inside a cap you set, and every decision it makes is on a page you can hand to the board.