Carlos Florênciostatus, system, specification_version, migration, owners
| status | system | specification_version | migration | owners | |
|---|---|---|---|---|---|
| draft | office | 1 | complete |
|
Office system
Purpose
The Office system owns autonomous agent workspaces, coordination, scheduling, automation runs, dashboards, inboxes, and Office-specific live state.
Ownership
This system owns Office agents and roles, autonomous task assignment, scheduler and wakeup policy, Office routing, automation runs, inbox activity, dashboard projections, and Office testing contracts.
Exclusions
- Durable task and workflow primitives belong to the task system.
- Shared agent profiles and permissions belong to the agent system.
- External provider connections belong to the integration system.
Specification map
Requirements
- Office: Agents
- Office: Personal Assistant Agent, Channels & Agent Memory
- Automation runs — status-scoped delete all
- Automation Runs
- Automations — "Pull request merged" trigger
- Automations in Settings
- Automations YAML Export
- Office: Cost Tracking & Budget Management
- Office Dashboard
- Office: Inbox, Approvals & Activity Log
- Office Live Updates
- Office per-agent and per-role tier selection
- Office: Overview
- Office Provider Routing
- Office Agent Runtime — Error Handling Contract
- Office Scheduler
- Office Tasks
- Office: E2E Mock Harness for Task Sessions and Messages
- Office: Slack-Style Unread Divider
System design
- Office: Agents System Design Part 1
- Office: Agents System Design Part 2
- Office: Agents System Design Part 3
- Office: Personal Assistant Agent, Channels & Agent Memory
- Automation Runs
- Automations — "Pull request merged" trigger System Design Part 1
- Automations — "Pull request merged" trigger System Design Part 2
- Automations — "Pull request merged" trigger System Design Part 3
- Automations — "Pull request merged" trigger System Design Part 4
- Automations — "Pull request merged" trigger System Design Part 5
- Automations — "Pull request merged" trigger System Design Part 6
- Automations — "Pull request merged" trigger System Design Part 7
- Automations — "Pull request merged" trigger System Design Part 8
- Automations in Settings System Design Part 1
- Automations in Settings System Design Part 2
- Automations YAML Export System Design Part 1
- Automations YAML Export System Design Part 2
- Automations YAML Export System Design Part 3
- Automations YAML Export System Design Part 4
- Automations YAML Export System Design Part 5
- Automations YAML Export System Design Part 6
- Office: Cost Tracking & Budget Management System Design Part 1
- Office: Cost Tracking & Budget Management System Design Part 2
- Office Live Updates System Design Part 1
- Office Live Updates System Design Part 2
- Office per-agent and per-role tier selection System Design Part 1
- Office per-agent and per-role tier selection System Design Part 2
- Office per-agent and per-role tier selection System Design Part 3
- Office: Overview System Design Part 1
- Office: Overview System Design Part 2
- Office Provider Routing System Design Part 1
- Office Provider Routing System Design Part 2
- Office Agent Runtime — Error Handling Contract System Design Part 1
- Office Agent Runtime — Error Handling Contract System Design Part 2
- Office Scheduler System Design Part 1
- Office Scheduler System Design Part 2
- Office Tasks System Design Part 1
- Office Tasks System Design Part 2
Migration record
All legacy sources assigned to this system are now represented by the canonical requirement and system-design documents above. Source detail is retained in those documents or in their linked design parts.
Related systems
- Tasks: supplies durable work and workflow primitives.
- Agents: supplies agent profiles and permission policy.
- Integrations: supplies provider connections.