Org inbox

Overview

Org inbox is where you watch the fleet. Every scheduled run across your organisation appears here with its outcome, how long it took, and what it produced in counts. Alongside it sits anything the system will not decide on its own, and a lookup that answers "why does the agent believe this about this account".

You see that a colleague ran something, not what it said

This is the part worth understanding before you use the page, because it is deliberate and it is enforced by the database rather than by the screen.

Your organisation's activity is shared: every seat can see which role ran which skill, when, whether it succeeded, and what it cost. Your organisation's content is not. A run belonging to a colleague shows a "metadata only" marker, and the artifact behind it does not load, because your session is not entitled to read it.

The exception is anything shared on purpose. A finding promoted to team or organisation visibility is readable by everyone it was promoted to, which is the whole point of promoting it. Your own drafts stay yours unless you promote them.

This is the same boundary the leadership rollups have always had: a manager sees that a rep's agent worked, never the words it wrote. The inbox does not widen it.

Waiting on you

Two kinds of decision reach a person, and both change what happens on the next run.

• A lesson. Your agents extract durable craft from what actually happened, for example that naming a compliance deadline in the first line earns replies on manufacturing renewals. A lesson the system is confident about and can tie to a real buyer event accepts itself. A lesson it is unsure about waits here. Approving one changes what every seat in its scope is grounded in from the next run onward, so each card shows the claim, how confident the system is, and the observed signal it rests on.
• A candidate prompt. A proposed change to how a skill is written can run in shadow against a slice of your real traffic first. Its output is scored and never delivered to anyone. The card shows how the candidate did against the live version on the same runs, because a candidate's own pass rate means nothing without knowing what live did on that week's work.

Rejecting either needs a reason. A refusal nobody can review later is not a decision, and both of these are kept as a record rather than deleted.

Why does the agent believe this?

Give the lookup an object type and a subject key (a company and its domain, for instance) and it lists every live fact your organisation holds about it: the claim, how far it is shared, who established it, and which agent recorded it.

Two things are worth reading closely:

• "Needs recheck" means something the fact was derived from has since been retracted. The fact is still believed and is flagged for revalidation; it has not silently disappeared, and it has not silently stayed true either.
• An empty result means no facts you are entitled to see, which is not the same as none existing. The page says so rather than implying the account is unknown.

What it costs

Nothing. The inbox reads what has already been recorded and runs no model of its own. The one figure it shows that is about spend is the shadow cost on a candidate card, which is what the shadow runs have cost so far, so the price of an experiment is visible before you decide whether to keep it going.