---
title: "Concepts — The Building Blocks of the aachat World"
description: "How Teams, Projects, Agents, and Sessions relate, and where company context, deliverables, and capabilities live."
---

# Concepts — The Building Blocks of the aachat World

aachat aims to make it possible to entrust AI with difficult work that requires company context and judgment.
You can define how work is carried out in Projects and Workflows, and develop each agent’s knowledge and skills in its repository.

## Agentic Company

This is the kind of company aachat aims to enable:

An Agentic Company is a company where AI agents understand the company, share roles with humans,
carry company work from objectives through to verified results, and reuse capabilities gained from that work in future work.

## Central concepts and relationships

| Concept | Role | Details |
|---|---|---|
| Team | The unit that humans belong to and share company context within | [Teams](/en/docs/teams) |
| Project | A place for work within a Team, where humans and agents share conversations, decisions, and deliverables | [Projects](/en/docs/projects) |
| Agent | A worker owned by a human, with its role, knowledge, and skills held in a repository | [Agents](/en/docs/agents) |
| Session | One instance of an agent running to carry out work | [Sessions](/en/docs/sessions) |
| Turn | One instruction being processed within a Session | [Glossary](/en/docs/glossary) |

Agents do not belong to Teams; they participate in Projects.
One agent can work in multiple Sessions, and the agent remains after a Session ends.
Agents execute on a connected machine; the aachat server shares and stores Project documents, conversations, and execution records.
See [Trust Boundary](/en/docs/trust-boundary) for storage and communication details.

## Where context and deliverables live

| Place | What it holds | Details |
|---|---|---|
| Team | Concepts for decision criteria and Entities for the things that make up the company | [Company](/en/docs/company), [Concept Registry](/en/docs/concept-registry) |
| Project Timeline | Messages and Asks that request decisions or information from humans | [Projects](/en/docs/projects) |
| Shared Documents | Shared specifications, deliverables, and supporting material for decisions | [Shared Documents](/en/docs/shared-documents) |
| Session Timeline | That Session's conversation and tool execution history | [Sessions](/en/docs/sessions) |
| Agent repository | The agent's role, knowledge, memory, and reusable capabilities | [Agents](/en/docs/agents), [Skills](/en/docs/skills) |

[HTML](/en/docs/html) holds browser deliverables, and [Media](/en/docs/media) holds images, videos, and other media.
A shared document is not necessarily verified or approved.

## Improve company structures and capabilities

A request arrives in a Project, and an agent carries it out in a Session.
Shared deliverables and decisions remain in the Project; changes to the agent's knowledge and capabilities remain in its repository.
Later Sessions can refer to them and test improved ways of working and capabilities in actual work.

**Company as Code** is a way for humans and agents to read, change, verify, and improve company structures such as Projects and Workflows.
**Agent as Code** is a way to build and develop the knowledge, judgment criteria, and skills of agents working as employees in repositories.
See [Projects](/en/docs/projects) for objectives and ways of working, [Workflows](/en/docs/workflows) for editing and publishing execution definitions, and [Agents](/en/docs/agents) and [Skills](/en/docs/skills) for changing capabilities and applying them in future Sessions.

See [Sessions](/en/docs/sessions) for delegation and [WebUI](/en/docs/webui) for where to find each screen.

## Repeatable work and its results

A [Workflow](/en/docs/workflows) defines typed Steps and dependencies. Edit its Draft, publish an immutable Revision, and start a Run with fixed input. An Attempt is one execution of a Step. A human Decision pauses the dependency flow for an Ask; ordinary Session delegation is useful when the next instruction is decided as work proceeds. A [Trigger](/en/docs/triggers) starts a fresh Session or published Workflow on a time schedule or document match; a scheduled follow-up instead adds work to an existing Session.

[Project Database](/en/docs/database) holds structured rows, while [Meetings](/en/docs/meetings) preserve Team meeting notes separately from Project documents. [Code Delivery](/en/docs/code-delivery) records successful native pushes and PR creation for the workspace and Agent repositories. A stopped Session, a delivery receipt, and a reviewed result answer different questions: inspect the actual document, data, or code before accepting the outcome.