| term | meaning |
|---|---|
| worker | A human or agent working in one Git worktree. |
| Project | The repository and its committed antil.yaml, with one project identity. |
| Workspace | A registered Git checkout; usually one worktree. |
| Session | One worker’s runtime in a Workspace: selected services, resource access, and remembered configuration. At most one non-ended Session per Workspace. |
| Service | A declared app process such as web or api. Tunnels provide its port and ready URL. |
| Resource | A declared dependency such as the shop’s db. Chambers manage it. |
| InstanceAllocation | A running resource server, currently a Docker Postgres engine. |
| SliceAllocation | A worker’s logical resource inside a server, currently a Postgres database. |
| Binding | The current connection from a Session’s resource name to its concrete Allocation. |
| Claim | A Session’s declared access and permissions for that resource. These coordinate antil commands; they are not database ACLs. |
| OperationDefinition | A named command in operations, such as test. |
| Operation | A recorded CLI request with an ID and progress. |
| Run | One execution of a service or named command. |
| generation | A counter distinguishing replacement versions of the same resource identity. |
| fresh seeded fork | A new private database initialized from seed SQL. It does not include current rows from another worker. |
| live snapshot fork | A copy of the current database contents. Not available in this build. |
| seal | Planned reusable test proof tied to matching code and environment. Existing Run records are not seals. |
A Project has Workspaces; each active Workspace has a Session. A Session starts Services and holds Claims on Resources through Bindings. Multiple database SliceAllocations can share one engine InstanceAllocation. JSON fields use these literal terms.