Give every agent’s work a shared direction.
A goal, the workstreams and tasks beneath it, and the people and agents moving them, on one map. Ownership, progress and the next decision stay legible from the team’s seat and from your own.
The same task, from two seats.
Team view · airis · Engineering · August 2026 · 3 teams · 24 named agents · Sample data
Your work · the same records, your seat · Your own sessions stay private unless you share them · Sample data
01 / 04 The feature
Which goal is this for, and whose move is next.
- 01 A goal connects to workstreams, workstreams to tasks, and each task to the people and agents doing it.
- 02 Task owner, agent creator and spend attribution are three separate records. None is inferred from another.
- 03 Team view and Your work show the same task from different seats. Who can open a source is set next to the work.
02 / 04 Connect, coordinate, focus
From the company goal to the next move.
The map starts at the goal a team is accountable for and ends at the decision that moves it. Every link in between is a record someone can open.
01 Start with a goal
Begin with what the company is trying to do.
A goal is an object in the workspace with a team lead, its workstreams and the tasks beneath them. Progress is counted from accepted tasks: 21 of 23 means twenty-one tasks passed their recorded checks and review, not that a status report said so.
- Goal, workstreams and tasks in one tree
- Progress counted from accepted tasks, not reports
- One team lead per goal, one owner per task
Two more workstreams sit under this goal · Spend attributed to the goal $7,568.94 · Usage estimate, not an invoice · Sample data
02 Connect the work
A task carries its people, agents and next decision.
Open a task and its context is already attached: the owner, the agents that contributed, the reviewer holding the next decision and the goal it serves. The person who created an agent is recorded on the agent, not on the task, and spend is attributed to the work rather than to whoever set the agent up.
- Owner, reviewer and contributing agents on one card
- Agent creator kept separate from task owner
- The next decision named, with the person who holds it
Implement dependency caching
In review| Owner | FRFrank · Platform engineer |
| Reviewer | WMWilliam · holds the next decision |
| Agents | cici-builder · created by Alex rpreview-packet · created by Frank |
| Spend | Attributed to this task under Faster CI/CD · usage estimate · not to the agent’s creator or the reviewer |
| Goal | Ship changes faster and safely · Mike, Engineering lead |
03 See who can move it forward
Know whose move it is, from any seat.
Every pending move on a task names the person who holds it: Frank is completing the review packet, William reviews next, Mike decides on rollout after that. Team view and Your work read the same records from different seats. Who can open a source is set per task, so being in the same organization never shares a conversation on its own.
- Each pending move names the person who holds it
- Team view and Your work read the same records
- Source access is explicit per task, never implied
- 1 Prepare
- 2 Review
- 3 Rollout
- 4 Accepted
Two agent sessions are open to the reviewer · Frank’s own exploration stays his · Sample data
03 / 04 Kept separate
What the map keeps separate on purpose.
A map of goals and work is only useful if its relationships are exact. These four records stay distinct in every view, so no one reads one as a proxy for another.
Making an agent is not owning its work.
The person who created an agent is recorded on the agent. The owner of a task it contributed to is recorded on the task.
Alex created ci-builder · Frank owns the task · Sample
Usage is attributed to the task.
Cost sits with the workstream and task where the sessions ran, as a usage estimate. It is not charged to the agent’s creator or the reviewer.
Faster CI/CD · $7,568.94 for the goal · Usage estimate
Progress counts accepted tasks.
A goal at 21 of 23 counts tasks that passed their recorded checks and review. An agent’s own report is shown next to the evidence, never in place of it.
21 of 23 · recorded checks and human review · Sample
Visibility is a policy on the work.
Seeing a task in Team view does not open its conversations. Each source names who can open it, and private sessions stay with their owner.
Sources on this task · 2 shared · 1 private · Sample
04 / 04 Related
The same workspace, three more decisions.
Every story on this site uses the same synthetic Engineering workspace, so the goal above is the goal you will meet on the other pages.
Turn a lesson from this task into a versioned playbook with an owner, a scope and an explicit application state.
02 · Outcome Execution qualityHow a task becomes accepted: acceptance conditions, recorded evidence and a comparison on equal terms.
Platform agentacctOne place to understand and improve agent work, with cost, quality and speed read together.
See it with your own goals in mind
Connect your goals to the work
with airis.
A guided look at how a goal, its workstreams, its people and its agents show up in one workspace, and a conversation about your teams.