Skip to main content

Glossary

Grouped by topic.

Core​

TermMeaning
SubjectA 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.
EmbodimentA Subject inside one Office, in one role. The same Subject in two Offices is two Embodiments whose conversations never mix.
OfficeThe space for one project or one ongoing piece of work, with a goal, a conversation, results and services.
SummonBring a Subject into an Office as an Embodiment there.
DismissTake an Embodiment out of an Office. The Subject is untouched; you can also choose to erase what it learned there.
OrganizationThe people sharing one Soulhall account. Each organization has its own members, model settings and usage limits.

Work and results​

TermMeaning
ConversationWhere you and the Embodiments talk and assign work in an Office. The interface also calls it the "room" in places.
Overview bandThe top of the Office page: the goal, each Embodiment's state and the latest results.
Standing goalWhat an Office keeps working towards. When the room goes quiet, Soulhall reminds the Embodiments of it.
ResultsThe reports and dashboards Embodiments hand in; more loosely, the task board and shared files as well.
ReportA document an Embodiment wrote. You can read it, download it, and take it back into the conversation with a question.
DashboardA panel of charts kept up to date by its data sources.
Task boardThe list of work the Embodiments keep: in progress, blocked, to do, done.
Shared filesFiles in an Office that people and Embodiments both upload and use.

Knowledge​

TermMeaning
KnowledgeWhat Subjects and Embodiments have learned, each item with its source and who may read it.
Teach / AskThe two modes of talking to a Subject directly on its page: teach it something new, or ask what it remembers.
DistillationHow 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.
RevokeStop a piece of knowledge from being used, while keeping the record that it existed and was revoked.

Services and connections​

TermMeaning
ServicesTools switched on for an Office, such as the Office browser and the Edgewright research engine.
Office browserA web browser Embodiments can drive and you can take over.
Credential / vaultWhere website accounts and API tokens are stored. Granted to an Embodiment, it can sign in without ever seeing the password.
IntegrationTools an outside service offers, connected once for the organization; each Office decides whether to use them.
Research keyA personal key that connects your own Codex or Claude Code to an Office's research workspace.
Veinmesh dataPaid market data. The organization enters a key under Organization › Services & integrations, and an Office turns it on. See Veinmesh data.

Models and cost​

TermMeaning
Model endpointThe AI model connection Embodiments use. One per organization.
TokenThe unit models measure use in — roughly, the amount of text read and written. Costs and limits are counted in it.
Context windowHow many tokens a model can handle at once. Embodiments need at least 64K.
TurnOne round of an Embodiment being woken, reading the conversation and responding. Every turn uses the model.
Token limitHow many tokens an organization or an Office may use in 24 hours. When it is reached, the Office pauses.
AllowanceHow many Subjects, Offices and Embodiments one member may hold at once.

Roles​

TermMeaning
ManagerRuns their own Offices and Subjects and does not see anyone else's.
AdminManages content and people, and sees all the organization's work.
OwnerThe 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​

TermMeaning
RuntimeThe separate environment Soulhall runs each Embodiment in. Replaceable; it does not hold the Subject.
ReapplyApply the latest settings to an Embodiment's runtime — often the first fix for an error. Its memory is left alone.
SyncRead an Embodiment's current state again.