Glossary
Canonical definitions for platform and accounting terms used across the portal.
Platform
Core concepts every service on this platform shares.
Postgres
Each service owns one Postgres database as the source of truth for its bounded context; services never read each other's databases.
Related: Transactional outbox
Transactional outbox
Each domain inserts events into its own <domain>_events table in the same transaction as the state change; a publisher drains unpublished rows to Azure Service Bus.
Command
An HTTP POST that changes state, recorded with an Idempotency-Key so retries do not double-apply; not CQRS or a command bus.
Related: Idempotency-Key, Transactional outbox
Idempotency-Key
A caller-supplied header, stable across retries, that lets command.Execute claim the operation once and replay the same response on duplicate requests.
Related: Command
Cedar
The authorization engine; each service embeds a Cedar policy and evaluates every mutating request against the actor's principal record.
Related: FID
FID
The id of a principal. For a person it is their Kratos identity id, a lowercase UUID; for a service it is its OAuth2 client_id. It arrives as the verified sub claim of a Hydra access token and becomes the actor on the request.
Principal
A person or a service that the identity service knows about, identified by its FID, with a kind (person or system) and a status (active or disabled). Having a principal grants nothing on its own; access comes from grants.
Grant
A role held by a principal at a scope: global, one building, or one unit. Grants live in the identity service and are the only input to authorization besides the endpoint_access data that says which roles an action allows.
OAuth2 client
An app or service registered with Hydra so it can get access tokens. Web and mobile apps are public clients that use authorization code with PKCE; services use client_credentials. Each has exactly one audience.
Related: FID
Response envelope
The template service wraps every JSON response in {header, payload}. A success payload is {data} (a record or a list) plus optional meta.pagination; accounting still returns bare bodies and RFC 9457 errors until the divergence is resolved.
Related: Command
Foundry
The service that owns agents: each one's definition, the tools it is granted, and whether it is running. People and agents build new agents through the same Foundry tools.
Accounting
Chart of accounts and ledger vocabulary.
Chart of accounts
The hierarchical set of accounts in one jurisdiction; codes are unique per chart, classifications are a closed enum, and parent links form a tree.
Related: Account classification
Account classification
One of asset, liability, equity, revenue, or expense; required on every account and used to derive normal balance and financial statement placement.
Related: Chart of accounts
Documents
Document storage, references, and blob access.
SAS URL
A Shared Access Signature: a blob URL carrying a signed, time-limited grant of specific permissions. The documents service signs one per request with the storage account key and never stores it, so an expired URL cannot be replayed from a command response.
Related: Storage account catalog
Storage account catalog
The named Azure Storage accounts the documents service can write to, each with a visibility, one container, and a SAS lifetime. Configuration rather than a database table; callers name an account and never a container.
Related: SAS URL
Workspace
Projects, conversations, and the collaboration surface agents read.
Context pack
What an agent is given before it answers: one project's own state plus the company knowledge that bears on it, served by workspace from a single endpoint. It degrades to the project sections alone when intelligence is unreachable, and says so, so an empty knowledge section is never mistaken for nothing being known.
Related: Insight, Derivation surface
Break-glass
Time-boxed membership a platform admin opens on a project. They can already read every project without being a member; this row is for appearing as a member, expires, and is implemented as membership rather than a check the authorization code skips.
Company fact
A statement about the business that a platform admin has decided is settled — a legal entity name, what a product is, which market the company sells into. It is a record in workspace's fact domain, written as markdown or uploaded as a file, readable by anyone and writable only by a platform admin. Intelligence derives claims from it the ordinary way and then confirms them instead of queueing them for review, and those claims go into every project's context pack. Distinct from an insight whose kind happens to be `fact`, which is any claim the pipeline extracted from a conversation and which still goes to a reviewer.
Related: Context pack, Insight, Epistemic state, Company model
Derivation surface
The internal routes intelligence reads conversation text through, authenticated by a service token and a named principal. Evidence stays in workspace and is fetched per request rather than copied, so a redaction takes effect everywhere at once.
Related: Context pack, Citation
Task
One thing a project needs to do, decide, answer, or remember. It has a type, a status, and a title, and everything else is optional. The API and the database call it an item.
Related: Task type, Task status, Goal
Task type
What kind of task it is: task, bug, chore, feature, question, or note. The type decides which extra fields the form asks for and which part of the task can become company knowledge.
Related: Task
Task status
Where a task stands, such as Todo or In review. Each status belongs to a status category and carries a one-line description the app shows beside its name.
Related: Status category, Task
Status category
One of six fixed stages every task status belongs to: backlog, unstarted, started, review, completed, or canceled. Completed and canceled are closed. Rules read the category rather than the status's name, so they keep working when a project adds statuses of its own.
Related: Task status
Goal
An outcome a project is working toward, with one lead, an optional target date, and a status. A project has at most five active goals, and closing one needs a note saying how it ended.
Related: Task
Intelligence
How the company knowledge layer decides what is known and how sure it is.
Insight
One claim the knowledge layer holds: a fact, decision, open question, or journal entry, derived from conversations and answerable across projects. It is never a source of truth — every insight points back at the evidence it came from.
Related: Citation, Epistemic state, Practice
Citation
A span of source text an insight rests on, verified twice: the quote must still exist where it claims to, and it must actually support the claim. A quote that exists but does not support becomes context; a claim with no supporting citation is withdrawn.
Related: Insight, Derivation surface
Epistemic state
How much credit a claim has earned — asserted, corroborated, human confirmed, authoritative, disputed, or stale — tracked separately from where it sits in the review workflow. Independence is counted by source, so ten quotes from one conversation is one source.
Practice
The area of expertise a claim belongs to: marketing, engineering, design, construction. Knowledge is company-scoped, so practice rather than project is what partitions the corpus.
Related: Insight
Candidate
A proposed insight waiting on a decision. Most are resolved without a person: well-grounded corroborated claims promote automatically, poorly grounded ones auto-reject, and anything unreviewed past its deadline expires rather than accumulating.
Related: Insight, Epistemic state
Enrichment queue
The Postgres table intelligence's derivation work runs through: leased claims, deduplication on job and target, exponential backoff, and a dead letter. It is a table rather than a broker queue because a burst of turns in one conversation has to collapse into one extraction, which is a row update.
Company model
The structured three-layer model of Flow that the knowledge layer compiles into: identity (human-owned), strategy (proposed then confirmed), and operating facts (automatic, each with an as-of date). Nothing is deleted; a change is superseded. Distinct from a company fact, which is the admin-written source text a claim can be derived from.
Related: Company fact
Unit role
Whether a property is owned, a joint venture, managed for a third-party owner, sold, or unresolved. Only managed units count toward the third-party management bet. Owned and JV growth must not be scored as that scale.
Related: Company model, Named metric
Named metric
A closed set of operating numbers the insight harness may ask for by slug: occupancy, leased percent, units, Bet 1 managed units, vacant units, vacant rent, asking rent, marketing spend, and the audience and hospitality counts. The agent never writes SQL. Adding a metric is a migration.
Related: Company model, Unit role, Portfolio finding
Portfolio finding
A harness-produced claim about the company model. It must name a metric, join at least two sources, state a deviation from a baseline, and name a decision it would change. Shadow findings are for review and are not published as insights. The harness clusters them into portfolio briefs.
Related: Company model, Named metric, Portfolio brief
Portfolio brief
A company-altitude story clustered from building-level findings: a thesis, a material number, a recommendation, and where the story could be wrong. Shadow only; not published as an insight.
Related: Portfolio finding, Company model
Construction
Real-estate development vocabulary: stages, gates, document revisions, and how progress is measured.
Development project
One building or site being developed, from the first idea to handing it over. It has one of four kinds: master plan, ground up, conversion, or capital improvement. Not a workspace project: a workspace project is where people talk about work, a development project is the work itself.
Related: Stage, Stage gate
Stage
One of the seven steps every development project passes through in order: initiation, execution plan, final product approval, tender, award, construction, closeout. The first five make up the pre-construction phase and the last two the construction phase. A project is in exactly one stage at a time and cannot skip one.
Related: Development project, Stage gate, Package
Stage gate
An approval that has to be granted before a project can leave initiation, final product approval, tender, or award. Without an approved gate the advance is refused, which stops a project drifting into the next stage before the previous one is signed off.
Package
A named body of work inside a project, such as signage, facade, or amenities. It is measured either by the progress of its tasks or by a percentage somebody reports. A project's progress is the weighted average of its packages and is never stored.
Related: Stage
Controlled document
A document whose changes are tracked formally, such as a drawing, a specification, or the project schedule. It keeps one permanent code for its whole life; a change adds a revision rather than a new document.
Revision
One version of a controlled document. Internal revisions (A, B, C, or R0-A after the first release) are working copies that are prepared, reviewed and approved. A published revision (R0, R1, and so on) is the official one people work from. Only one revision is published at a time, and publishing a new one supersedes the old.
Related: Controlled document
Variation
A change to the cost or schedule agreed at award, for example extra work a new drawing revision needs. It is approved through an approval, and incorporating it writes a new baseline.
Baseline
A saved record of what was agreed at a point in time: the budget, the construction start and finish, and the published document revisions. The first is written when the project passes the award gate; each incorporated variation adds another. Earlier baselines are kept.
Related: Variation, Stage gate
Vendor
An outside firm working on a development: an architect, an engineer, a consultant, a contractor, or a supplier. Its contacts use the vendor portal, which shows them only the tasks assigned to their firm and the documents those tasks use.
Related: Development project, Controlled document