Bounded Contexts

The Corporation’s domain model is divided into six bounded contexts. Each context owns specific data, enforces specific rules, and communicates with other contexts through defined interfaces.

The domain types live in corp-core. Storage paths are defined via StoredEntity implementations in corp-storage. Route handlers live in corp-server. Nothing in corp-core does I/O.

The six contexts

1. Formation

Owns entity lifecycle — creation, conversion, dissolution, legal identity, state registration, and initial tax milestones.

Owns	Does not own
Entity metadata (name, type, jurisdiction, status)	Equity grants (→ Equity)
Formation documents (articles, operating agreement, bylaws)	Bank accounts (→ Treasury)
State filings (certificate of incorporation / formation)	Ongoing compliance (→ Compliance)
Tax profile (IRS classification, EIN)

corp-core modules: formation::Entity, formation::Document, formation::Filing, formation::TaxProfile

Storage paths: formation/entity/, formation/documents/, formation/filings/, formation/tax/

Owned by: Legal / Corporate Secretary + Backend Governance Kernel

2. Equity

Owns the cap table — instruments, grants, SAFEs, issuance identifiers, vesting schedules, and ownership calculations.

Owns	Does not own
Instruments and grant records	Entity legal identity (→ Formation)
SAFE notes and conversion terms	Cash movement for purchases (→ Treasury)
Vesting schedules and holder records	Compliance reporting (→ Compliance)
Funding rounds, valuations, and transfers

corp-core modules: equity::CapTable, equity::Instrument, equity::EquityGrant, equity::SafeNote, equity::Valuation, equity::FundingRound, equity::Holder, equity::ShareTransfer

Storage paths: equity/cap_tables/, equity/instruments/, equity/grants/, equity/safes/, equity/valuations/, equity/rounds/, equity/holders/, equity/transfers/

Owned by: Board + Officers + Backend Governance Kernel

3. Governance

Owns board composition, meetings, agenda items, votes, and resolutions.

Owns	Does not own
Governance bodies (board, committees)	Entity legal identity (→ Formation)
Governance seats and member appointments	Cap table changes (→ Equity)
Meetings, agendas, and votes
Resolutions and board actions

corp-core modules: governance::GovernanceBody, governance::GovernanceSeat, governance::Meeting, governance::AgendaItem, governance::Vote, governance::Resolution

Storage paths: governance/bodies/, governance/seats/, governance/meetings/, governance/agenda_items/, governance/votes/, governance/resolutions/

Owned by: Board + Officers + Backend Governance Kernel

4. Treasury

Owns bank accounts, payment instructions, cash movement, and spending-limit enforcement.

Owns	Does not own
Bank account records	Invoice generation (→ cross-context)
Payment instructions (ACH, wire, check)	Payroll calculation (→ Workforce)
Journal entries and reconciliation	Tax filings (→ Compliance)
Spending limits and approval thresholds

corp-core modules: treasury::Account, treasury::BankAccount, treasury::JournalEntry, treasury::Invoice, treasury::Payment, treasury::PayrollRun, treasury::Reconciliation

Storage paths: treasury/accounts/, treasury/bank_accounts/, treasury/journal_entries/, treasury/invoices/, treasury/payments/, treasury/payroll_runs/, treasury/reconciliations/

Owned by: Finance / Treasury + Backend Governance Kernel

5. Compliance

Owns the compliance calendar — deadlines, filing obligations, evidence requirements, and jurisdiction-specific rules.

Owns	Does not own
Compliance calendar and deadlines	Entity formation steps (→ Formation)
Filing obligations (annual reports, tax returns)	Financial transactions (→ Treasury)
Evidence requirements and tracking	Equity issuance (→ Equity)
Jurisdiction-specific rule sets

Owned by: Legal / Compliance + Backend Governance Kernel

6. Agent Identity

Owns agent runtime identity, capability scope, and delegation state.

Owns	Does not own
Agent identity and credentials	Corporate data (→ all other contexts)
Capability scopes (which tools an agent can use)	Policy rules (→ Governance Kernel)
Authority mode (normal, principal_unavailable, incident_lockdown)	Human obligations (→ Compliance)
Delegation chain

corp-core modules: agents::Agent

Storage paths: agents/

Owned by: Principal / Board + Backend Governance Kernel

Cross-context rules

1. Every external or irreversible action is requested as an Intent, evaluated by policy, and executed via execute_intent. No context bypasses this.

2. Authority tiering applies across all contexts:

   • Tier 1: Agent-autonomous (read operations, reports)
   • Tier 2: Agent proposes, human approves (equity issuance, payroll)
   • Tier 3: Board-only (dissolution, jurisdiction change)

3. Natural-person reserved acts produce Obligation artifacts — signing formation documents, filing with the state, tax attestations.

4. Scopes enforce context boundaries at the API layer. Each context has dedicated read/write scopes (e.g., formation-read, equity-write, treasury-approve). A total of 34 scopes are defined in corp-core::auth::Scope, checked via ScopeSet on every authenticated request.

Context interactions

Formation ──→ Compliance   (jurisdiction triggers compliance calendar)
Formation ──→ Treasury     (entity + tax IDs enable bank accounts)
Governance ──→ Equity      (board resolution required for Tier 3 equity events)
Equity    ──→ Compliance   (issuance events trigger reporting obligations)
Treasury  ──→ Compliance   (transaction evidence supports filing requirements)
Agent Identity ──→ All     (agent scopes constrain what operations are allowed)

Each arrow represents a defined interface — not direct data access. Context A publishes events or data; context B consumes them through the governance kernel.