Glossary
Grouped by topic.
Core
| Term | Meaning |
|---|---|
| Subject | A person's way of judging: persona, expertise and decision principles, plus the knowledge built up over time. It belongs to no Office and can be summoned again and again. |
| Embodiment | A Subject inside one Office, in one role. The same Subject in two Offices is two Embodiments whose conversations never mix. |
| Office | The space for one project or one ongoing piece of work, with a goal, a conversation, results and services. |
| Summon | Bring a Subject into an Office as an Embodiment there. |
| Dismiss | Take an Embodiment out of an Office. The Subject is untouched; you can also choose to erase what it learned there. |
| Organization | The people sharing one Soulhall account. Each organization has its own members, model settings and usage limits. |
Work and results
| Term | Meaning |
|---|---|
| Conversation | Where you and the Embodiments talk and assign work in an Office. The interface also calls it the "room" in places. |
| Overview band | The top of the Office page: the goal, each Embodiment's state and the latest results. |
| Standing goal | What an Office keeps working towards. When the room goes quiet, Soulhall reminds the Embodiments of it. |
| Results | The reports and dashboards Embodiments hand in; more loosely, the task board and shared files as well. |
| Report | A document an Embodiment wrote. You can read it, download it, and take it back into the conversation with a question. |
| Dashboard | A panel of charts kept up to date by its data sources. |
| Task board | The list of work the Embodiments keep: in progress, blocked, to do, done. |
| Shared files | Files in an Office that people and Embodiments both upload and use. |
Knowledge
| Term | Meaning |
|---|---|
| Knowledge | What Subjects and Embodiments have learned, each item with its source and who may read it. |
| Teach / Ask | The two modes of talking to a Subject directly on its page: teach it something new, or ask what it remembers. |
| Distillation | How Soulhall sorts what Embodiments learn: details that only hold for a project stay with the Embodiment; lessons that hold anywhere are added to the Subject. |
| Revoke | Stop a piece of knowledge from being used, while keeping the record that it existed and was revoked. |
Services and connections
| Term | Meaning |
|---|---|
| Services | Tools switched on for an Office, such as the Office browser and the Edgewright research engine. |
| Office browser | A web browser Embodiments can drive and you can take over. |
| Credential / vault | Where website accounts and API tokens are stored. Granted to an Embodiment, it can sign in without ever seeing the password. |
| Integration | Tools an outside service offers, connected once for the organization; each Office decides whether to use them. |
| Research key | A personal key that connects your own Codex or Claude Code to an Office's research workspace. |
| Veinmesh data | Paid market data. The organization enters a key under Organization › Services & integrations, and an Office turns it on. See Veinmesh data. |
Models and cost
| Term | Meaning |
|---|---|
| Model endpoint | The AI model connection Embodiments use. One per organization. |
| Token | The unit models measure use in — roughly, the amount of text read and written. Costs and limits are counted in it. |
| Context window | How many tokens a model can handle at once. Embodiments need at least 64K. |
| Turn | One round of an Embodiment being woken, reading the conversation and responding. Every turn uses the model. |
| Token limit | How many tokens an organization or an Office may use in 24 hours. When it is reached, the Office pauses. |
| Allowance | How many Subjects, Offices and Embodiments one member may hold at once. |
Roles
| Term | Meaning |
|---|---|
| Manager | Runs their own Offices and Subjects and does not see anyone else's. |
| Admin | Manages content and people, and sees all the organization's work. |
| Owner | The same as Admin, and can also delete the organization. There is always at least one. |
The full table is in Roles and permissions.
Behind the scenes
| Term | Meaning |
|---|---|
| Runtime | The separate environment Soulhall runs each Embodiment in. Replaceable; it does not hold the Subject. |
| Reapply | Apply the latest settings to an Embodiment's runtime — often the first fix for an error. Its memory is left alone. |
| Sync | Read an Embodiment's current state again. |