Jobs & Actions
Running agents is only half the story. Korras Agents separates observation (Jobs) from mutation (Actions) so writes stay under human control.
Jobs
Jobs are the history of Operator workflow and report runs for your workspace.
Use Jobs to:
- See what ran and when
- Open insight briefs produced by Operator
- Filter and page through run history
Operator briefs are grounded, insight-only summaries — health signals, data quality notes, and watch items. They are not a standalone analytics product; they exist to support handoffs and decisions.
Recipes and task packs
Before a workflow runs in production:
- A recipe defines the declarative workflow (SQL templates, scope, validation rules)
- A task pack is compiled from an active recipe
- The pack must pass static validation and a sandbox dry-run before activation
This gate keeps unsafe or over-scoped execution contracts out of your workspace’s live path.
Actions
Actions are workspace-scoped mutations with an approval path:
- Plan — propose what would change
- Preview — dry-run and surface stale-state drift
- Execute — run only after approval
Authorization can be one-time (with TTL) or always-approved for a rule. Treat approvals as part of your operating model — not a formality.
Recommended loop
- Build or refine an agent and recipe
- Run via Operator
- Review the Job / insight brief
- If a write is needed, open an Action preview
- Approve only when the preview matches intent