Glossary

Identity and access

Identity
Your user account (the person who signs in). One identity can access multiple workspaces and use multiple sign-in methods (e.g. passkeys).

Workspace (tenant)
Your organization’s isolated Axiomatic environment: team members, entities, ledger data, and credit balance. Billing and usage apply per workspace.

Entity
An accounting boundary inside a workspace: a business, fund, trust, or personal books with its own chart of accounts and reports. You switch entity context in the app; APIs are usually scoped to one entity. See Entities.

Credential
A sign-in method (e.g. passkey) linked to your identity.

---

Data protection

DEK (data encryption key)
Per-entity symmetric key used to encrypt sensitive columns at rest (AES-256-GCM). The DEK is available only inside authorized server handlers after tenant resolution.

Encryption at rest
Sensitive fields are stored as ciphertext; plaintext is never written to tenant tables for protected columns. See Encryption.

Blind index
Optional HMAC of a searchable value so you can match without storing decryptable duplicates in plaintext.

---

Accounting engine

Event
A typed business fact (invoice, payment, payroll line, etc.) that enters the system and can drive posting.

Rule / DSL
Declarative posting logic compiled to a deterministic engine (WASM). Rules map events to journal lines according to your rule packs.

Rule pack
A bundle of rules and configuration for a book or scenario (e.g. GAAP vs. management).

Book
A logical ledger within an entity (e.g. GAAP, tax, management) with its own rule packs and posted balances.

Journal entry
Balanced debit/credit lines posted to accounts; traceable back to events and rules.

Triple-entry
Posting model where events, journal lines, and attestations/proofs can align; the docs use this to describe the integrated engine beyond classical double-entry alone.

---

Product and billing

Module / app
A major surface in the unified app (Ledger, CRM, Cortex, etc.) — same deployment, entity-scoped APIs unless documented otherwise.

Cortex
In-app AI with tools grounded in your tenant. See Cortex AI.

Credits (cloud)
Prepaid USD balance (1 credit ≈ $1) consumed when you use billable features — ledger posts, API writes, AI, proofs, storage, and similar — not a flat monthly ERP subscription like QuickBooks/Xero and not per-seat like Salesforce. Each workspace has its own balance. When balance is zero, writes pause until you add credits. See Billing and credits.

---

Integration and automation

Connector
An integration to an external system (bank, Stripe, Gmail, etc.) with a documented auth model (API key, OAuth, webhook).

API key (ak_…)
Entity-scoped secret for Authorization: Bearer ak_... on the REST API (/api/...), with optional module scopes set when the key is created. Created under Settings → API keys.

---

Related

• Platform overview — how modules fit together
• Architecture — how the system is structured
• ZK proofs — proofs of financial statements