Skip to main content
Business Transaction answers: what was submitted for evaluation? A BusinessTransaction is the aggregate root of a single execution lifecycle. It bundles Authority, Authorization, Intent, and a Policy Reference together with runtime signals, and becomes the anchor that every downstream artifact — Decision, Execution, Verification, Receipt, Execution Trust Record — refers back to.

​
Model

interface BusinessTransactionMetadata {
  businessTransactionId: string;
  correlationId: string;
  tenantId: string | null;
  sourceSystem: string;
  submittedBy: string;
  submittedAt: Date;
}

interface BusinessTransaction {
  businessTransactionId: string;
  metadata: BusinessTransactionMetadata;
  authority: Authority;
  authorization: Authorization;
  intent: Intent;
  policy: PolicyReference;
  signals: Record<string, unknown>;
  status: string;
  createdAt: Date;
}
signals carries the runtime data a policy actually evaluates — for example a requested amount, a risk score, or a model recommendation. Signal values must be deterministic; see Guides → Basic Execution for constraints on signal types.

​
Lifecycle

A Business Transaction is created once, atomically. If validation of any required field fails, no Business Transaction — and no downstream Execution Trust Record — is created. There is no partial-creation state. See REST API → Error Model.

​
Relationships

Decision

Produced by evaluating this transaction’s Intent against its Policy Reference.

Execution

Occurs only after a successful Decision.

Execution Trust Record

Aggregates this transaction with all its executions, verifications, receipts, and overrides.

REST API

Retrieve and list Business Transactions over HTTP.