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
Events are inserted into an events table in the same transaction as the state change; a publisher drains unpublished rows to RabbitMQ.
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
A text principal identifier assigned upstream (for example Google Workspace). Becomes the actor on a request after JWT validation (verified sub claim); used in Cedar policies.
Related: Cedar
Response envelope
The template service wraps every JSON response in {header, payload}; accounting still returns bare bodies and RFC 9457 errors until the divergence is resolved.
Related: Command
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