How work fits together
Understand the records that connect a goal to its execution and results.
A workspace groups the code, people, configuration, and work for a project. A session is where an agent does a piece of that work. Tasks and specifications add tracking and agreement when the goal needs them.
Read the visual explanation
A workspace contains project context. A specification defines the outcome, a task tracks delivery, and a session produces changes and outputs.
The main records
| Record | What it represents | Example |
|---|---|---|
| Organization | The shared ownership and funding boundary | Your company and its wallet |
| Workspace | A shared project context | The customer dashboard team |
| Repository | A source checkout available to work | The dashboard web app |
| Agent | A role with a particular kind of work | Product writes a specification |
| Specification | An agreed description of behavior and acceptance | How search filters should reset |
| Task | A tracked delivery item | Fix empty-query search results |
| Session | The goal, environment, conversations, and results of work | Investigate and implement the fix |
| Conversation | A message history within the work | A thread between you and Engineering |
| Turn | One execution in response to accepted input | Apply the fix and run checks |
| Output | A published result | A pull request, image, video, or document |
Follow the relationship
Organization
Workspace: repositories + members + settings
Specification: desired behavior and acceptance
Task: delivery and ownership
Session: conversations + environment
Turn: agent execution
Outputs: changes, reports, files, pull requestsThis is a common path, not a requirement to create every record. A standalone session can fix a small bug without a task or specification. A task can have several sessions, and delegated work can have child sessions with their own conversations.
Choose the right place for a follow-up
Keep a correction to the same implementation in its session so the agent retains the decisions. Put a new independent goal in a separate session. Use a task for ownership and delivery status; use a specification for decisions about what should be built.
Changing a task's status does not prove a code change shipped. A completed turn does not prove a pull request merged. Follow the linked result and its checks to verify the outcome.
Continue with sessions, Tasks (Alpha), or specifications.