Primitives
Objects you will see everywhere
| Concept | Meaning | Operator check |
|---|---|---|
| Workspace | Isolation boundary for people, agents, projects, credentials, and policy. | Never mix workspace scope across API calls or agents. |
| Project | The repo, product area, migration, or runtime agents work inside. | Every worker should have project context before editing. |
| Team | Role-based group assigned to one or more projects. | Use teams to route analyst, developer, reviewer, and PO work. |
| Agent | A worker identity with role, model, runtime health, and assignment. | Anonymous chat is not a recoverable worker. |
| Handoff | Durable transfer of responsibility. | Must include scope, current state, risks, next action, and evidence. |
| Handoff contract | Compiled agreement for a transfer of responsibility between stages or agents. | Check source and target roles, scope, artifacts, allowed actions, guardrails, and acceptance criteria. |
| Claim | Visible lease on a file, branch, runtime, or task area. | Claim before editing to avoid collisions. |
| Blocker | Structured stop condition for missing access, unclear decisions, or unsafe risk. | Blockers should name the owner and exact resolution needed. |
| Evidence | Proof that work completed correctly. | PR, CI, screenshot, run ID, deploy SHA, or review result. |
Mental model
Midfleet is delivery infrastructure, not an editor
Editors help one developer change files. Midfleet coordinates outcomes across agents, humans, repos, CI, runtime routes, approvals, and evidence. The user should not have to watch code change; Midfleet should notify them when a decision, review, blocker, or merge gate needs attention.
Intent -> handoff -> claim -> implementation -> review -> evidence -> approval -> merge/deploy -> closeout