Approvals, budgets, and activity

​

Legacy topic map

Use the current owner for each older topic name:

​

Definition

These records make Agent work inspectable. Approvals govern proposed actions, budgets constrain spend, activity records material product changes, and Run evidence explains execution. Dashboard, Calendar, and human attention surfaces summarize those source records without owning a second copy of their state.

​

States and records

​

Approvals

An Approval keeps the requested action, target, requester, status, discussion, decision, and application result together. An accepted request applies through the service that owns the action. Application is idempotent and remains scoped to the organization. Only pending can move to revision_requested. Approval or rejection can resolve pending and revision_requested; resubmission is available only from revision_requested. approved, rejected, and cancelled are terminal for that Approval record.

​

Budgets and cost

Runtime and result ingestion create cost events with source identity. Rudder can roll them up by organization, Agent, Project, Issue, Run, and time window where supported. Monthly periods use UTC. Soft alerts expose spend pressure; hard limits pause or block new work instead of reporting only after the fact.

​

Activity

Activity is the cross-surface audit record for material mutations. Entries keep the actor, organization, action, entity, references, and a summary. They can connect related Chat, Issue, Run, and Approval context.

​

Run intelligence

Organization Run lists default to bounded summaries with identity, status, timing, Agent and runtime, target, outcome or error, usage and cost, Skill evidence, and log availability. Open one Run for full result, context, transcript, events, or logs. Raw evidence remains available and detail reads use bounded pages where supported.

​

Dashboard, Calendar, and human attention

Dashboard derives organization health from live domain records. Calendar keeps dated events linked to their source Automation, Issue, Run, or configured calendar source. Human attention routes through Inbox, sidebar badges, and Messenger to the source object that needs a decision or response.

​

Constraints

• A Review judges output quality. An Approval authorizes a governed action. One does not substitute for the other.
• A budget hard stop prevents new hidden work when the limit is reached. Cost events retain their source Run or event identity.
• Activity records material changes, not every internal update.
• A Run summary does not replace transcripts, results, logs, events, or linked artifacts needed for diagnosis and Review.

​

Boundaries

All records stay organization-scoped. User attention and unread state must not leak across organizations. Dashboard and Calendar are derived views, so they do not redefine Issue, Run, Approval, cost, or Automation state. Use the owning detail page when a summary raises a question. Activity explains that something changed; the source Issue, Run, Approval, or Automation provides the full record and the available action.

​

Examples

• An Agent proposes a sensitive change. The Approval records the payload and discussion; after acceptance, the owning service applies it once and leaves activity evidence.
• A monthly Agent budget reaches its hard limit. New work pauses or is blocked, while cost views retain the events that produced the total.
• Dashboard shows a failed Run and Inbox asks for attention. Open the source Run for its transcript and logs, then use the linked work object for the next decision.