S&DP Architecture Explorer

Keputusan Arsitektur

Primary Database

Source of truth untuk write, versioning, relationship, idempotency, policy, dan ledger.

Strong consistency

JSON Document

Profil, role, capability, requirement, dan konfigurasi sparse yang dapat berkembang tanpa DDL rutin.

Flexible schema

Manticore Search

Projection terdenormalisasi untuk pencarian, filter, CMS, dan dashboard. Disposable dan dapat di-reindex.

Eventually consistent

External Services

Masterdata, AWB, dan Billing tetap menjadi pemilik data masing-masing. S&DP menyimpan external ID.

No authoritative duplication

OOP ke Data Model

Encapsulation

Ownership per service dan akses melalui API/event.

Inheritance

Role taxonomy dan default capability, bukan table-per-subclass.

Polymorphism

Behavior dipilih berdasarkan capability, workflow, dan policy.

Composition

Satu party dapat menerima banyak role dan capability tanpa menggandakan identity.

ERD v4.0.0 (Counter-Design Aurora MySQL 8.0)

v4.0.0 Reviewed Draft

v4.0.0 — JSON Attribute Naming Normalization: the aggregate-owned JSON columns on account, account_relationship, and ledger_entry use the same physical name, attributes. Distinct JSON roles keep semantic names: facts for immutable observations, definition for policy rules, and payload for integration messages. Signed BIGINT Snowflake IDs remain unchanged.

erDiagram ACCOUNT_TYPE_LOOKUP ||--o{ ACCOUNT : classifies ACCOUNT_STATUS_LOOKUP ||--o{ ACCOUNT : status RELATIONSHIP_TYPE_LOOKUP ||--o{ ACCOUNT_RELATIONSHIP : categorizes ACTIVITY_TYPE_LOOKUP ||--o{ ACTIVITY_EVENT : types ACTIVITY_TYPE_LOOKUP ||--o{ OPERATIONAL_TRANSACTION : types POLICY_STATUS_LOOKUP ||--o{ POLICY_DOCUMENT : status LEDGER_STATUS_LOOKUP ||--o{ LEDGER_ENTRY : status LEDGER_ENTRY_TYPE_LOOKUP ||--o{ LEDGER_ENTRY : entry_type ACCOUNT ||--o{ ACCOUNT : created_by ACCOUNT ||--o{ ACCOUNT_RELATIONSHIP : source ACCOUNT ||--o{ ACCOUNT_RELATIONSHIP : target ACCOUNT ||--o{ ACTIVITY_EVENT : validates_actor ACCOUNT ||--o{ OPERATIONAL_TRANSACTION : validates_actor ACCOUNT ||--o{ LEDGER_ENTRY : validates_beneficiary ACTIVITY_EVENT ||--o{ LEDGER_ENTRY : validates_activity POLICY_DOCUMENT ||--o{ LEDGER_ENTRY : validates_policy OUTBOX_EVENT ||--o{ PROJECTION_RECEIPT : projects ACCOUNT { bigint account_id PK string account_type FK string external_account_id string subledger_code string cost_center_code bigint created_by_account_id FK integer schema_version json attributes string status FK boolean is_active bigint version datetime deleted_at datetime created_at datetime updated_at } ACCOUNT_RELATIONSHIP { bigint relationship_id PK bigint source_account_id FK bigint target_account_id FK string relationship_type FK datetime valid_from datetime valid_to string status FK boolean is_active json attributes datetime deleted_at datetime created_at datetime updated_at } OPERATIONAL_TRANSACTION { bigint transaction_id PK bigint partition_key PK boolean is_active PK datetime partition_created_time bigint actor_account_id string external_transaction_id string transaction_type FK string branch_code integer financial_period numeric amount string currency string status FK json facts datetime occurred_at datetime settled_at datetime deleted_at datetime created_at datetime updated_at } ACTIVITY_EVENT { bigint activity_id PK bigint partition_key PK boolean is_active PK datetime partition_created_time bigint actor_account_id string activity_type string external_transaction_id string idempotency_key UK json facts datetime occurred_at datetime recorded_at datetime deleted_at datetime created_at datetime updated_at } POLICY_DOCUMENT { bigint policy_id PK string policy_code integer policy_version json definition datetime valid_from datetime valid_to string status FK datetime created_at datetime updated_at } LEDGER_ENTRY { bigint ledger_entry_id PK bigint partition_key PK boolean is_active PK datetime partition_created_time bigint activity_id bigint policy_id FK binary32 accrual_dedup_key UK bigint beneficiary_account_id FK string subledger_code string debit_account_code string credit_account_code integer financial_period string ap_voucher_number bigint journal_batch_id numeric amount string currency string entry_type FK string status FK string billing_external_id UK json attributes datetime settled_at datetime deleted_at datetime created_at datetime updated_at } OUTBOX_EVENT { bigint event_id PK bigint partition_key PK boolean is_active PK datetime partition_created_time string aggregate_type bigint aggregate_id binary32 outbox_dedup_key UK bigint aggregate_version string event_type json payload datetime created_at datetime updated_at datetime available_at datetime published_at integer attempt_count string last_error_code string last_error_ref } PROJECTION_RECEIPT { string projection_name PK bigint event_id bigint aggregate_id bigint aggregate_version datetime processed_at } ACCOUNT_TYPE_LOOKUP { string code PK string description } ACCOUNT_STATUS_LOOKUP { string code PK string description } RELATIONSHIP_TYPE_LOOKUP { string code PK string description } ACTIVITY_TYPE_LOOKUP { string code PK string description } POLICY_STATUS_LOOKUP { string code PK string description } LEDGER_STATUS_LOOKUP { string code PK string description } LEDGER_ENTRY_TYPE_LOOKUP { string code PK string description }

Design Summary

Identity

Signed 64-bit Snowflake IDs; typed account relationships; external business IDs remain strings.

Integrity

Foreign keys on non-partitioned tables; application validation documented where Aurora partitioning forbids FKs.

Operations

Idempotency, optimistic versions, transactional outbox, CDC timestamps, and keyset/batch bounds.

Retention

deleted_at is the only soft-delete truth; is_active is lifecycle/partition state only.

Data Dictionary

How to read: one row describes one physical column in schemas.sql. PK = primary key, FK = database-enforced foreign key, App-ref = application-validated reference on a partitioned table, and UK = member of a unique key. IDs are signed 64-bit Snowflakes and JSON APIs expose them as decimal strings.

`account_type_lookup`

Allowed party/account classifications such as agent, partner, and CMS user.

Reference4 columns

`account_status_lookup`

Allowed account lifecycle states; deletion is represented only by deleted_at.

Reference4 columns

`relationship_type_lookup`

Allowed semantic edges between accounts, such as referral and management.

Reference4 columns

`activity_type_lookup`

Allowed immutable business activity classifications.

Reference4 columns

`policy_status_lookup`

Allowed lifecycle states for versioned commission policies.

Reference4 columns

`ledger_status_lookup`

Allowed lifecycle states for commission ledger entries.

Reference4 columns

`ledger_entry_type_lookup`

Allowed accounting entry classifications, including accrual and reversal.

Reference4 columns

`account`

Canonical S&DP party identity for agents, managing partners, and internal CMS users.

Identity / Party14 columns

`account_relationship`

Typed, time-bounded relationship edge between two accounts.

Identity / Party12 columns

`operational_transaction`

Mutable logistics transaction snapshot used for operational state and settlement.

Logistics19 columns

`activity_event`

Immutable, idempotent business activity used as evidence for commission decisions.

Logistics / Audit14 columns

`policy_document`

Versioned and effective-dated commission calculation policy.

Commission11 columns

`ledger_entry`

Typed commission accrual, reversal, and settlement record with ERP reference snapshots.

Commission / Finance24 columns

`outbox_event`

Transactional outbox envelope for reliable asynchronous projection and integration.

Integration18 columns

`projection_receipt`

Idempotent acknowledgement that a named projection processed an event/version.

Integration8 columns

Table	Column	Type	Key	Nullability / default	Business meaning & rule	Example	Owner
`account_type_lookup` Allowed party/account classifications such as agent, partner, and CMS user.	`code`	`varchar(64)`	PK	Required Default: `—`	Stable machine-readable lookup value.	`ACTIVE`	S&DP Reference Data
`account_type_lookup`	`description`	`varchar(255)`	—	Required Default: `—`	Human-readable explanation of the lookup value.	`—`	S&DP Reference Data
`account_type_lookup`	`created_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC timestamp when the row was created; microsecond precision.	`—`	S&DP Reference Data
`account_type_lookup`	`updated_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC CDC timestamp of the latest row change; microsecond precision and ETL indexed.	`—`	S&DP Reference Data
`account_status_lookup` Allowed account lifecycle states; deletion is represented only by deleted_at.	`code`	`varchar(64)`	PK	Required Default: `—`	Stable machine-readable lookup value.	`ACTIVE`	S&DP Reference Data
`account_status_lookup`	`description`	`varchar(255)`	—	Required Default: `—`	Human-readable explanation of the lookup value.	`—`	S&DP Reference Data
`account_status_lookup`	`created_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC timestamp when the row was created; microsecond precision.	`—`	S&DP Reference Data
`account_status_lookup`	`updated_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC CDC timestamp of the latest row change; microsecond precision and ETL indexed.	`—`	S&DP Reference Data
`relationship_type_lookup` Allowed semantic edges between accounts, such as referral and management.	`code`	`varchar(64)`	PK	Required Default: `—`	Stable machine-readable lookup value.	`ACTIVE`	S&DP Reference Data
`relationship_type_lookup`	`description`	`varchar(255)`	—	Required Default: `—`	Human-readable explanation of the lookup value.	`—`	S&DP Reference Data
`relationship_type_lookup`	`created_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC timestamp when the row was created; microsecond precision.	`—`	S&DP Reference Data
`relationship_type_lookup`	`updated_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC CDC timestamp of the latest row change; microsecond precision and ETL indexed.	`—`	S&DP Reference Data
`activity_type_lookup` Allowed immutable business activity classifications.	`code`	`varchar(64)`	PK	Required Default: `—`	Stable machine-readable lookup value.	`ACTIVE`	S&DP Reference Data
`activity_type_lookup`	`description`	`varchar(255)`	—	Required Default: `—`	Human-readable explanation of the lookup value.	`—`	S&DP Reference Data
`activity_type_lookup`	`created_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC timestamp when the row was created; microsecond precision.	`—`	S&DP Reference Data
`activity_type_lookup`	`updated_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC CDC timestamp of the latest row change; microsecond precision and ETL indexed.	`—`	S&DP Reference Data
`policy_status_lookup` Allowed lifecycle states for versioned commission policies.	`code`	`varchar(64)`	PK	Required Default: `—`	Stable machine-readable lookup value.	`ACTIVE`	S&DP Reference Data
`policy_status_lookup`	`description`	`varchar(255)`	—	Required Default: `—`	Human-readable explanation of the lookup value.	`—`	S&DP Reference Data
`policy_status_lookup`	`created_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC timestamp when the row was created; microsecond precision.	`—`	S&DP Reference Data
`policy_status_lookup`	`updated_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC CDC timestamp of the latest row change; microsecond precision and ETL indexed.	`—`	S&DP Reference Data
`ledger_status_lookup` Allowed lifecycle states for commission ledger entries.	`code`	`varchar(64)`	PK	Required Default: `—`	Stable machine-readable lookup value.	`ACTIVE`	S&DP Reference Data
`ledger_status_lookup`	`description`	`varchar(255)`	—	Required Default: `—`	Human-readable explanation of the lookup value.	`—`	S&DP Reference Data
`ledger_status_lookup`	`created_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC timestamp when the row was created; microsecond precision.	`—`	S&DP Reference Data
`ledger_status_lookup`	`updated_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC CDC timestamp of the latest row change; microsecond precision and ETL indexed.	`—`	S&DP Reference Data
`ledger_entry_type_lookup` Allowed accounting entry classifications, including accrual and reversal.	`code`	`varchar(64)`	PK	Required Default: `—`	Stable machine-readable lookup value.	`ACTIVE`	S&DP Reference Data
`ledger_entry_type_lookup`	`description`	`varchar(255)`	—	Required Default: `—`	Human-readable explanation of the lookup value.	`—`	S&DP Reference Data
`ledger_entry_type_lookup`	`created_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC timestamp when the row was created; microsecond precision.	`—`	S&DP Reference Data
`ledger_entry_type_lookup`	`updated_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC CDC timestamp of the latest row change; microsecond precision and ETL indexed.	`—`	S&DP Reference Data
`account` Canonical S&DP party identity for agents, managing partners, and internal CMS users.	`account_id`	`bigint`	PK	Required Default: `—`	Application-generated signed 64-bit Snowflake identifier for the account.	`215574410218721283`	S&DP Account Domain
`account`	`account_type`	`varchar(64)`	FK · UK	Required Default: `—`	Account classification validated by account_type_lookup.	`AGENT`	S&DP Account Domain
`account`	`external_account_id`	`varchar(128)`	UK	Required Default: `—`	Authoritative identity/reference from Masterdata or IAM.	`MD-AGENT-001`	S&DP Account Domain
`account`	`subledger_code`	`varchar(64)`	—	Optional Default: `—`	Validated ERP AP vendor/subledger reference snapshot.	`VEND-AG-9001`	S&DP Account Domain
`account`	`cost_center_code`	`varchar(64)`	—	Optional Default: `—`	Validated ERP cost-center reference snapshot.	`CC-CGK-01`	S&DP Account Domain
`account`	`created_by_account_id`	`bigint`	FK	Optional Default: `—`	Account that created this account; commonly the CMS operator.	`—`	S&DP Account Domain
`account`	`schema_version`	`int`	—	Required Default: `1`	Version of the bounded JSON document contract.	`1`	S&DP Account Domain
`account`	`attributes`	`json`	—	Required Default: `—`	Aggregate-owned extensible profile attributes: sparse identity references, roles, capabilities, properties, and external document references.	`—`	S&DP Account Domain
`account`	`status`	`varchar(64)`	FK	Required Default: `'PENDING'`	Current business lifecycle status validated by the corresponding lookup where a physical FK is available.	`ACTIVE`	S&DP Account Domain
`account`	`is_active`	`tinyint(1)`	—	Required Default: `1`	Lifecycle/partition state: 1 ongoing, 0 final or settled; never means deleted.	`1 = ongoing`	S&DP Account Domain
`account`	`version`	`bigint`	—	Required Default: `1`	Monotonic aggregate version used for optimistic updates and event ordering.	`2`	S&DP Account Domain
`account`	`deleted_at`	`datetime(6)`	—	Optional Default: `—`	Sole soft-delete marker. NULL means live; a timestamp means deleted.	`NULL = live`	S&DP Account Domain
`account`	`created_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC timestamp when the row was created; microsecond precision.	`—`	S&DP Account Domain
`account`	`updated_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC CDC timestamp of the latest row change; microsecond precision and ETL indexed.	`—`	S&DP Account Domain
`account_relationship` Typed, time-bounded relationship edge between two accounts.	`relationship_id`	`bigint`	PK	Required Default: `—`	Application-generated signed 64-bit Snowflake identifier for the relationship.	`—`	S&DP Account Domain
`account_relationship`	`source_account_id`	`bigint`	FK	Required Default: `—`	Account from which the relationship edge originates.	`—`	S&DP Account Domain
`account_relationship`	`target_account_id`	`bigint`	FK	Required Default: `—`	Account to which the relationship edge points.	`—`	S&DP Account Domain
`account_relationship`	`relationship_type`	`varchar(64)`	FK	Required Default: `—`	Meaning of the relationship edge, validated by relationship_type_lookup.	`REFERRED_BY`	S&DP Account Domain
`account_relationship`	`valid_from`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	Inclusive UTC start of the relationship or policy validity.	`—`	S&DP Account Domain
`account_relationship`	`valid_to`	`datetime(6)`	—	Optional Default: `—`	Exclusive UTC end of validity; NULL means open-ended.	`NULL = open-ended`	S&DP Account Domain
`account_relationship`	`status`	`varchar(64)`	FK	Required Default: `'ACTIVE'`	Current business lifecycle status validated by the corresponding lookup where a physical FK is available.	`ACTIVE`	S&DP Account Domain
`account_relationship`	`is_active`	`tinyint(1)`	—	Required Default: `1`	Lifecycle/partition state: 1 ongoing, 0 final or settled; never means deleted.	`1 = ongoing`	S&DP Account Domain
`account_relationship`	`attributes`	`json`	—	Required Default: `—`	Aggregate-owned extensible attributes of this relationship edge; stable relationship invariants remain typed columns.	`—`	S&DP Account Domain
`account_relationship`	`deleted_at`	`datetime(6)`	—	Optional Default: `—`	Sole soft-delete marker. NULL means live; a timestamp means deleted.	`NULL = live`	S&DP Account Domain
`account_relationship`	`created_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC timestamp when the row was created; microsecond precision.	`—`	S&DP Account Domain
`account_relationship`	`updated_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC CDC timestamp of the latest row change; microsecond precision and ETL indexed.	`—`	S&DP Account Domain
`operational_transaction` Mutable logistics transaction snapshot used for operational state and settlement.	`transaction_id`	`bigint`	PK	Required Default: `—`	Application-generated Snowflake identifier for the logistics transaction.	`—`	S&DP Operations
`operational_transaction`	`partition_key`	`bigint`	PK · UK	Required Default: `—`	Application-maintained UTC year-month (YYYYMM) derived from updated_at.	`202608`	S&DP Operations
`operational_transaction`	`is_active`	`tinyint`	PK · UK	Required Default: `1`	Lifecycle/partition state: 1 ongoing, 0 final or settled; never means deleted.	`1 = ongoing`	S&DP Operations
`operational_transaction`	`partition_created_time`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	Timestamp recorded when the row first entered its partition lifecycle.	`—`	S&DP Operations
`operational_transaction`	`actor_account_id`	`bigint`	App-ref	Required Default: `—`	Account that performed or owns the operational activity.	`—`	S&DP Operations
`operational_transaction`	`transaction_type`	`varchar(64)`	—	Required Default: `—`	Business transaction classification, such as AWB_CREATED.	`AWB_CREATED`	S&DP Operations
`operational_transaction`	`branch_code`	`varchar(64)`	—	Optional Default: `—`	Validated ERP branch/hub or cost-dimension reference snapshot.	`HUB-CGK-01`	S&DP Operations
`operational_transaction`	`financial_period`	`int`	—	Required Default: `—`	ERP accounting period encoded as YYYYMM.	`202608`	S&DP Operations
`operational_transaction`	`external_transaction_id`	`varchar(128)`	App-ref	Required Default: `—`	Authoritative external business ID, normally an AWB or order ID.	`AWB-2026-001`	S&DP Operations
`operational_transaction`	`idempotency_key`	`varchar(128)`	UK	Required Default: `—`	Stable business retry key; duplicate processing must resolve to the original operation.	`awb:AWB-2026-001:create`	S&DP Operations
`operational_transaction`	`amount`	`decimal(19,4)`	—	Required Default: `0.0000`	Monetary amount stored exactly as DECIMAL(19,4).	`7500.0000`	S&DP Operations
`operational_transaction`	`currency`	`char(3)`	—	Required Default: `'IDR'`	ISO 4217 three-letter currency code.	`IDR`	S&DP Operations
`operational_transaction`	`status`	`varchar(64)`	—	Required Default: `'PENDING'`	Current business lifecycle status validated by the corresponding lookup where a physical FK is available.	`ACTIVE`	S&DP Operations
`operational_transaction`	`facts`	`json`	—	Required Default: `—`	Immutable or bounded JSON business facts not suitable as stable relational invariants.	`—`	S&DP Operations
`operational_transaction`	`occurred_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC time when the business action happened.	`—`	S&DP Operations
`operational_transaction`	`settled_at`	`datetime(6)`	—	Optional Default: `—`	UTC time when the transaction or ledger entry reached final settlement.	`—`	S&DP Operations
`operational_transaction`	`deleted_at`	`datetime(6)`	—	Optional Default: `—`	Sole soft-delete marker. NULL means live; a timestamp means deleted.	`NULL = live`	S&DP Operations
`operational_transaction`	`created_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC timestamp when the row was created; microsecond precision.	`—`	S&DP Operations
`operational_transaction`	`updated_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC CDC timestamp of the latest row change; microsecond precision and ETL indexed.	`—`	S&DP Operations
`activity_event` Immutable, idempotent business activity used as evidence for commission decisions.	`activity_id`	`bigint`	PK	Required Default: `—`	Application-generated Snowflake identifier for immutable activity evidence.	`—`	S&DP Operations
`activity_event`	`partition_key`	`bigint`	PK · UK	Required Default: `—`	Application-maintained UTC year-month (YYYYMM) derived from updated_at.	`202608`	S&DP Operations
`activity_event`	`is_active`	`tinyint`	PK · UK	Required Default: `1`	Lifecycle/partition state: 1 ongoing, 0 final or settled; never means deleted.	`1 = ongoing`	S&DP Operations
`activity_event`	`partition_created_time`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	Timestamp recorded when the row first entered its partition lifecycle.	`—`	S&DP Operations
`activity_event`	`actor_account_id`	`bigint`	App-ref	Required Default: `—`	Account that performed or owns the operational activity.	`—`	S&DP Operations
`activity_event`	`activity_type`	`varchar(64)`	UK	Required Default: `—`	Activity classification; service validates the lookup for partitioned tables.	`AWB_HANDED_OVER`	S&DP Operations
`activity_event`	`external_transaction_id`	`varchar(128)`	UK	Required Default: `—`	Authoritative external business ID, normally an AWB or order ID.	`AWB-2026-001`	S&DP Operations
`activity_event`	`idempotency_key`	`varchar(128)`	UK	Required Default: `—`	Stable business retry key; duplicate processing must resolve to the original operation.	`awb:AWB-2026-001:create`	S&DP Operations
`activity_event`	`facts`	`json`	—	Required Default: `—`	Immutable or bounded JSON business facts not suitable as stable relational invariants.	`—`	S&DP Operations
`activity_event`	`occurred_at`	`datetime(6)`	—	Required Default: `—`	UTC time when the business action happened.	`—`	S&DP Operations
`activity_event`	`recorded_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC time when S&DP persisted the externally occurring activity.	`—`	S&DP Operations
`activity_event`	`deleted_at`	`datetime(6)`	—	Optional Default: `—`	Sole soft-delete marker. NULL means live; a timestamp means deleted.	`NULL = live`	S&DP Operations
`activity_event`	`created_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC timestamp when the row was created; microsecond precision.	`—`	S&DP Operations
`activity_event`	`updated_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC CDC timestamp of the latest row change; microsecond precision and ETL indexed.	`—`	S&DP Operations
`policy_document` Versioned and effective-dated commission calculation policy.	`policy_id`	`bigint`	PK	Required Default: `—`	Application-generated Snowflake identifier of the exact policy version used.	`—`	S&DP Commission
`policy_document`	`policy_code`	`varchar(128)`	UK	Required Default: `—`	Stable business code shared by all versions of a policy.	`AWB_HANDOVER_COMMISSION`	S&DP Commission
`policy_document`	`policy_version`	`int`	UK	Required Default: `—`	Monotonic version number within a policy code.	`1`	S&DP Commission
`policy_document`	`definition`	`json`	—	Required Default: `—`	Versioned, schema-validated commission rule definition in bounded JSON.	`—`	S&DP Commission
`policy_document`	`valid_from`	`datetime(6)`	—	Required Default: `—`	Inclusive UTC start of the relationship or policy validity.	`—`	S&DP Commission
`policy_document`	`valid_to`	`datetime(6)`	—	Optional Default: `—`	Exclusive UTC end of validity; NULL means open-ended.	`NULL = open-ended`	S&DP Commission
`policy_document`	`status`	`varchar(64)`	FK	Required Default: `'DRAFT'`	Current business lifecycle status validated by the corresponding lookup where a physical FK is available.	`ACTIVE`	S&DP Commission
`policy_document`	`is_active`	`tinyint(1)`	—	Required Default: `1`	Lifecycle/partition state: 1 ongoing, 0 final or settled; never means deleted.	`1 = ongoing`	S&DP Commission
`policy_document`	`deleted_at`	`datetime(6)`	—	Optional Default: `—`	Sole soft-delete marker. NULL means live; a timestamp means deleted.	`NULL = live`	S&DP Commission
`policy_document`	`created_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC timestamp when the row was created; microsecond precision.	`—`	S&DP Commission
`policy_document`	`updated_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC CDC timestamp of the latest row change; microsecond precision and ETL indexed.	`—`	S&DP Commission
`ledger_entry` Typed commission accrual, reversal, and settlement record with ERP reference snapshots.	`ledger_entry_id`	`bigint`	PK	Required Default: `—`	Application-generated Snowflake identifier for a ledger entry.	`—`	S&DP Commission; ERP/Finance owns referenced codes
`ledger_entry`	`partition_key`	`bigint`	PK · UK	Required Default: `—`	Application-maintained UTC year-month (YYYYMM) derived from updated_at.	`202608`	S&DP Commission; ERP/Finance owns referenced codes
`ledger_entry`	`is_active`	`tinyint`	PK · UK	Required Default: `1`	Lifecycle/partition state: 1 ongoing, 0 final or settled; never means deleted.	`1 = ongoing`	S&DP Commission; ERP/Finance owns referenced codes
`ledger_entry`	`partition_created_time`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	Timestamp recorded when the row first entered its partition lifecycle.	`—`	S&DP Commission; ERP/Finance owns referenced codes
`ledger_entry`	`activity_id`	`bigint`	—	Required Default: `—`	Application-generated Snowflake identifier for immutable activity evidence.	`—`	S&DP Commission; ERP/Finance owns referenced codes
`ledger_entry`	`policy_id`	`bigint`	App-ref	Required Default: `—`	Application-generated Snowflake identifier of the exact policy version used.	`—`	S&DP Commission; ERP/Finance owns referenced codes
`ledger_entry`	`accrual_dedup_key`	`binary(32)`	UK	Required Default: `—`	Application-computed SHA-256 business identity preventing duplicate accruals.	`—`	S&DP Commission; ERP/Finance owns referenced codes
`ledger_entry`	`beneficiary_account_id`	`bigint`	App-ref	Required Default: `—`	Account entitled to the commission or affected by the ledger entry.	`—`	S&DP Commission; ERP/Finance owns referenced codes
`ledger_entry`	`subledger_code`	`varchar(64)`	—	Required Default: `—`	Validated ERP AP vendor/subledger reference snapshot.	`VEND-AG-9001`	S&DP Commission; ERP/Finance owns referenced codes
`ledger_entry`	`debit_account_code`	`varchar(64)`	—	Required Default: `—`	Validated ERP GL debit-account snapshot used to explain posting.	`6100-COMMISSION-EXPENSE`	S&DP Commission; ERP/Finance owns referenced codes
`ledger_entry`	`credit_account_code`	`varchar(64)`	—	Required Default: `—`	Validated ERP GL credit-account snapshot used to explain posting.	`2100-PARTNER-PAYABLE`	S&DP Commission; ERP/Finance owns referenced codes
`ledger_entry`	`financial_period`	`int`	—	Required Default: `—`	ERP accounting period encoded as YYYYMM.	`202608`	S&DP Commission; ERP/Finance owns referenced codes
`ledger_entry`	`ap_voucher_number`	`varchar(128)`	—	Optional Default: `—`	ERP Accounts Payable voucher reference returned during settlement.	`APV-2026-08-00788`	S&DP Commission; ERP/Finance owns referenced codes
`ledger_entry`	`journal_batch_id`	`bigint`	App-ref	Optional Default: `—`	Internal normalized Snowflake reference for the ERP journal batch.	`—`	S&DP Commission; ERP/Finance owns referenced codes
`ledger_entry`	`amount`	`decimal(19,4)`	—	Required Default: `—`	Monetary amount stored exactly as DECIMAL(19,4).	`7500.0000`	S&DP Commission; ERP/Finance owns referenced codes
`ledger_entry`	`currency`	`char(3)`	—	Required Default: `—`	ISO 4217 three-letter currency code.	`IDR`	S&DP Commission; ERP/Finance owns referenced codes
`ledger_entry`	`entry_type`	`varchar(64)`	—	Required Default: `—`	Accounting intent, such as commission accrual, reversal, or settlement.	`—`	S&DP Commission; ERP/Finance owns referenced codes
`ledger_entry`	`status`	`varchar(64)`	—	Required Default: `'PENDING'`	Current business lifecycle status validated by the corresponding lookup where a physical FK is available.	`ACTIVE`	S&DP Commission; ERP/Finance owns referenced codes
`ledger_entry`	`billing_external_id`	`varchar(128)`	UK	Optional Default: `—`	Idempotent settlement/callback reference owned by Billing.	`BILL-SETTLE-7788`	S&DP Commission; ERP/Finance owns referenced codes
`ledger_entry`	`attributes`	`json`	—	Required Default: `—`	Aggregate-owned calculation and audit attributes for this ledger entry; accounting invariants remain typed columns.	`—`	S&DP Commission; ERP/Finance owns referenced codes
`ledger_entry`	`settled_at`	`datetime(6)`	—	Optional Default: `—`	UTC time when the transaction or ledger entry reached final settlement.	`—`	S&DP Commission; ERP/Finance owns referenced codes
`ledger_entry`	`deleted_at`	`datetime(6)`	—	Optional Default: `—`	Sole soft-delete marker. NULL means live; a timestamp means deleted.	`NULL = live`	S&DP Commission; ERP/Finance owns referenced codes
`ledger_entry`	`created_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC timestamp when the row was created; microsecond precision.	`—`	S&DP Commission; ERP/Finance owns referenced codes
`ledger_entry`	`updated_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC CDC timestamp of the latest row change; microsecond precision and ETL indexed.	`—`	S&DP Commission; ERP/Finance owns referenced codes
`outbox_event` Transactional outbox envelope for reliable asynchronous projection and integration.	`event_id`	`bigint`	PK	Required Default: `—`	Application-generated Snowflake identifier for an outbox event.	`—`	S&DP Integration
`outbox_event`	`partition_key`	`bigint`	PK · UK	Required Default: `—`	Application-maintained UTC year-month (YYYYMM) derived from updated_at.	`202608`	S&DP Integration
`outbox_event`	`is_active`	`tinyint`	PK · UK	Required Default: `1`	Lifecycle/partition state: 1 ongoing, 0 final or settled; never means deleted.	`1 = ongoing`	S&DP Integration
`outbox_event`	`partition_created_time`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	Timestamp recorded when the row first entered its partition lifecycle.	`—`	S&DP Integration
`outbox_event`	`aggregate_type`	`varchar(64)`	—	Required Default: `—`	Controlled discriminator for the integration envelope; governed by a closed registry.	`ACCOUNT`	S&DP Integration
`outbox_event`	`aggregate_id`	`bigint`	App-ref	Required Default: `—`	Snowflake identifier of the aggregate referenced by the envelope.	`—`	S&DP Integration
`outbox_event`	`outbox_dedup_key`	`binary(32)`	UK	Required Default: `—`	Application-computed SHA-256 identity preventing duplicate event publication.	`—`	S&DP Integration
`outbox_event`	`aggregate_version`	`bigint`	—	Required Default: `—`	Source aggregate version used to reject stale projection updates.	`2`	S&DP Integration
`outbox_event`	`event_type`	`varchar(128)`	—	Required Default: `—`	Stable integration event name.	`AgentApproved`	S&DP Integration
`outbox_event`	`payload`	`json`	—	Required Default: `—`	Versioned integration payload in bounded JSON.	`—`	S&DP Integration
`outbox_event`	`created_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC timestamp when the row was created; microsecond precision.	`—`	S&DP Integration
`outbox_event`	`updated_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC CDC timestamp of the latest row change; microsecond precision and ETL indexed.	`—`	S&DP Integration
`outbox_event`	`available_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC time after which a relay worker may claim the event.	`—`	S&DP Integration
`outbox_event`	`published_at`	`datetime(6)`	—	Optional Default: `—`	UTC acknowledgement time after successful downstream publication; NULL while pending.	`NULL = pending`	S&DP Integration
`outbox_event`	`attempt_count`	`int`	—	Required Default: `0`	Number of relay processing attempts.	`0`	S&DP Integration
`outbox_event`	`last_error_code`	`varchar(64)`	—	Optional Default: `—`	Bounded machine-readable code for the latest publishing error.	`—`	S&DP Integration
`outbox_event`	`last_error_ref`	`varchar(512)`	—	Optional Default: `—`	External observability/S3 reference; raw logs are not stored in Aurora.	`—`	S&DP Integration
`outbox_event`	`deleted_at`	`datetime(6)`	—	Optional Default: `—`	Sole soft-delete marker. NULL means live; a timestamp means deleted.	`NULL = live`	S&DP Integration
`projection_receipt` Idempotent acknowledgement that a named projection processed an event/version.	`projection_name`	`varchar(64)`	PK	Required Default: `—`	Stable name of the consuming projection, such as manticore-agent.	`manticore-agent`	S&DP Integration
`projection_receipt`	`event_id`	`bigint`	PK	Required Default: `—`	Application-generated Snowflake identifier for an outbox event.	`—`	S&DP Integration
`projection_receipt`	`aggregate_id`	`bigint`	App-ref	Required Default: `—`	Snowflake identifier of the aggregate referenced by the envelope.	`—`	S&DP Integration
`projection_receipt`	`aggregate_version`	`bigint`	—	Required Default: `—`	Source aggregate version used to reject stale projection updates.	`2`	S&DP Integration
`projection_receipt`	`processed_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC time the projection acknowledged processing.	`—`	S&DP Integration
`projection_receipt`	`deleted_at`	`datetime(6)`	—	Optional Default: `—`	Sole soft-delete marker. NULL means live; a timestamp means deleted.	`NULL = live`	S&DP Integration
`projection_receipt`	`created_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC timestamp when the row was created; microsecond precision.	`—`	S&DP Integration
`projection_receipt`	`updated_at`	`datetime(6)`	—	Required Default: `CURRENT_TIMESTAMP(6)`	UTC CDC timestamp of the latest row change; microsecond precision and ETL indexed.	`—`	S&DP Integration

JSON naming: attributes describes the row’s own aggregate; facts records immutable observations; definition contains policy rules; and payload carries an integration message. Governance: lookup values and JSON keys shown here are the current executable baseline. JSON remains bounded by versioned schemas; external Masterdata, AWB, Billing, Attachment, and ERP values are references rather than duplicated authority.

SQL Antipattern & Best-Practice Compliance Matrix

Audit scope: current schemas.sql, scenario-queries.sql, and partition-operations.sql. Sources: Bill Karwin's SQL Antipatterns taxonomy, AWS Aurora/MySQL guidance, internal DBE Rule-of-Thumb, and internal portable partition SOP. “Conditional” means the design is safe only when the stated application/runbook control is enforced.

Rule / risk	Source	Status	Evidence & control
Jaywalking / multi-valued attributes	SQL Antipatterns	Pass	Account hierarchy uses typed rows in `account_relationship`; JSON arrays are bounded profile/capability attributes, not relational FK lists.
Polymorphic association	SQL Antipatterns	Documented exception	Core domain links are typed. `outbox_event.aggregate_type + aggregate_id` remains an intentional polymorphic integration envelope; producers enforce a closed aggregate-type registry and validate ownership.
EAV / metadata tribbles	SQL Antipatterns	Pass	Stable invariants are typed; sparse profile/policy payloads use bounded versioned JSON. Search fields are projected to Manticore, avoiding JSON scans on Aurora.
Naive tree / hierarchy	SQL Antipatterns	Pass	MP-to-mitra relations are adjacency edges with validity and status; no comma-separated ancestry path.
Missing PK/FK, duplicate rows	SQL Antipatterns + MySQL	Documented exception	Non-partitioned tables use PK/FK. Partitioned tables include partition columns in every PK/unique key; Aurora's partition/FK restriction requires same-service validation plus dedup keys.
Random/oversized identifier mismatch	Manticore + client interoperability	Pass	Application-generated signed `BIGINT` Snowflakes map directly to Manticore document IDs; JSON transports decimal strings.
Rounding / money errors	SQL Antipatterns + PRD	Pass	Amounts use `DECIMAL(19,4)`, never float; ledger pins the policy version and immutable calculation facts.
Implicit columns / ambiguous joins	DBE RoT	Pass	No `SELECT *`; examples use explicit projection and explicit `INNER JOIN`.
Database wall-clock predicate	DBE RoT	Pass	UTC cutoffs are application-bound literals/parameters; no `NOW()` or `CURRENT_TIMESTAMP()` in `WHERE`.
Unbounded reads / oversized IN	DBE RoT	Pass	Relay walkthrough uses an ordered `LIMIT 10` workset, within the maximum batch/IN bound of 100; cursor pagination is required and broad reports are offloaded.
Soft-delete state duplication	DBE convention	Pass	`deleted_at` alone means deletion. `is_active` means ongoing/final lifecycle and never means deleted.
CDC precision	DBE / DEH	Pass	`created_at`/`updated_at` use microseconds; `updated_at` has `ON UPDATE CURRENT_TIMESTAMP(6)` and an ETL index.
Partition portability and pruning	Partition SOP	Pass	`LIST COLUMNS(partition_key,is_active)`, `YYYYMM`, explicit active/inactive pairs, no catch-all, and predicate examples include both columns.
Future partition / retention safety	Partition SOP	Pass	Runbook creates both next-month partitions before opening; archives first and drops only the inactive partition.
Partition row movement	Partition SOP	Pass	Settlement and outbox publish examples atomically bind `updated_at`, recompute `partition_key`, change `is_active`, and use the previous composite locator.
Outbox concurrency / poison payloads	Messaging best practice	Pass	`FOR UPDATE SKIP LOCKED LIMIT 100`, dedup key, aggregate version, receipt acknowledgement; only error code/reference stored, not raw logs.

Review conclusion: executable SQL gaps found by independent static review were corrected: explicit seed columns, lookup CDC fields/indexes, single deletion state, policy validity, bounded outbox workset, and atomic partition movement. Remaining exceptions are documented: partitioned-table FKs and the polymorphic outbox envelope. Application controls still require implementation verification.

ERD ↔ PRD/BRD Use-Case Traceability

Source calibration: the authoritative S&DP PRD is ClickUp doc 8crmjdc-130258, current page 8crmjdc-3278538 (predecessor 8crmjdc-3073858). The supplied workspace contains no separately identified S&DP BRD; therefore BRD coverage below is marked Not supplied, never inferred. Rows marked Partial show the bounded v3 ERD support and name the missing product aggregate.

Use case / source	Actors & system	ERD mapping	Coverage
PRD — public self-registration, referral/induk, unique agent identity	Calon Agen, MP, S&DP	`account`; `account_relationship(REFERRED_BY / MANAGED_BY)`; `outbox_event`	Covered
PRD — CMS registration by Sales/RM and creator attribution	Sales/RM, S&DP	`account.created_by_account_id`; role/profile JSON; `activity_event`	Covered
PRD — RN document review → S&P location approval → advanced-data activation	Retail Network, S&P, candidate	`account.status/version`; bounded verification JSON; `activity_event`; `outbox_event`	Partial — approver attribution and state transition are executable; dedicated approval-decision/reason aggregate is not modeled
PRD — active agent sync to Masterdata Customer/Partner/Gerai Partner	S&DP, Masterdata Core, OPS	`external_account_id`; account role JSON; `outbox_event`/`projection_receipt`	Covered as integration; Masterdata owns replicas
PRD — receive/scan existing AWB and idempotently mark DROP PARTNER	Agent, AWB Service	`operational_transaction`; `activity_event`; external AWB ID; idempotency key	Covered
PRD — create resi and retain immutable commission inputs	Agent, AWB/Tariff/SPK	`operational_transaction` typed money + JSON facts; `outbox_event`	Partial — S&DP stores transaction reference/facts; sender, recipient, package and tariff remain owning-service data
PRD — pickup/drop-off handover, cutoff and proof	Agent, SPK/Hub	`activity_event(AWB_HANDED_OVER)`; transaction facts; external attachment reference; outbox	Partial — schedule/evidence lifecycle is external; no local handover aggregate
PRD — configure effective commission/bonus scheme	RN, Head Commercial, MP	`policy_document` version, validity, status and JSON definition; audit event	Covered for calculation policy
PRD — threshold approval of commission/bonus scheme	RN, Head Commercial	Policy status/version + approval `activity_event`	Partial — decision/reason/threshold snapshot needs a dedicated approval aggregate before implementation
PRD — commission estimate/final, pending/ready, reconciliation and correction	Agent, S&DP, Finance	`activity_event` + pinned `policy_document` + `ledger_entry`; reversal as a new ledger row	Covered
PRD — AP settlement / payout and Finance references	Billing, ERP AP, Finance	Ledger subledger/cost/GL/period; `billing_external_id`; AP voucher; journal batch; settlement state	Covered as AP integration; AP voucher and journal batch are exercised
PRD — Manticore search/list/dashboard projection	CMS, Agent Dashboard	`outbox_event` → `projection_receipt` → Manticore; authoritative detail remains Aurora/owner	Covered
PRD — role-specific menus, Owner/Admin provisioning, wallet/rekening	Owner, Admin, CMS roles	Account attributes JSON for roles/capabilities and external IAM/payment references only	Partial — no credential, RBAC policy, wallet or bank-account aggregate in this ERD
PRD — KPI, tiering, penalty, claim charging	Agent, CMS, Claim/Finance	Immutable operational/activity facts can feed derived projections	Partial/out of bounded v3 scope — no authoritative KPI/tier/claim aggregate
BRD use cases	Business stakeholders	No source mapping possible	Not supplied — attach the S&DP BRD doc/page ID to complete bidirectional traceability

Gap decision: this matrix does not invent missing tables. Approval history, handover evidence, wallet, KPI/tier, and claim aggregates require confirmed ownership/lifecycle from source requirements before extending the ERD.

v4.0.0 Data Flow

1. Client / CMS
register or update agent

→

2. S&DP API
validate Masterdata, AWB, and ERP references

→

3. Snowflake Generator
allocate signed int64 IDs

→

4. Aurora MySQL
account + relationship + outbox atomically

→

5. Outbox Relay
upsert accepted sourceVersion

→

6. Manticore
search/list projection only

Commission → ERP AP Settlement

1. AWB Service
authoritative logistics event ID

→

2. Activity & Policy
idempotent event + pinned policy version

→

3. Commission Ledger
subledger, cost dimension, GL debit/credit, financial period

→

4. Billing / ERP AP
settlement callback + AP voucher / journal batch reference

Read Rules

Search & CMS

Read Manticore

Text search, filters, cursor pagination, and non-authoritative dashboard projection.

Authoritative Detail

Read Aurora / owning service

Hydrate external identity, AWB, billing, and ERP data from the owning service when needed.

Approval & Eligibility

Never decide from search index

Evaluate Aurora state and versioned policy.

Money & Settlement

Never decide from search index

Use typed ledger fields, pinned policy, ERP AP voucher, and Billing callback state.

v4.0.0 Data Ownership

Data	Source of Truth	Stored by S&DP v4.0.0
Customer/account identity, PIC, contact	Masterdata	`external_account_id` + bounded profile JSON
Address, region, attachments	Masterdata / Attachment	External IDs + S&DP verification status only
Agent role, hierarchy, lifecycle	S&DP	`account` + `account_relationship`
AWB, sender, recipient, delivery status	AWB Service	`external_transaction_id` + immutable commission facts
Commission policy and accrual/reversal	S&DP	Versioned `policy_document` + typed `ledger_entry`
ERP AP vendor/subledger & cost center mapping	ERP / Finance Master	`subledger_code`, `cost_center_code`, `branch_code` reference snapshots
ERP GL account mapping	ERP / Finance Master	`debit_account_code`, `credit_account_code`, `financial_period` snapshot used by accrual
Invoice, payment, settlement	Billing / ERP AP	`billing_external_id`, `ap_voucher_number`, `journal_batch_id`, settlement state
Internal 64-bit identifiers	S&DP application / shared Snowflake allocator	Signed `BIGINT`; same value used as Manticore document ID
Search projection	Derived	Manticore; rebuildable and non-authoritative

v4.0.0 Zero-DDL Change Test

Tambah MOBILE_AGENT

Tambah role, capability, document requirement, workflow, dan policy sebagai data.

Zero DDL

Komisi tier baru

Buat policy version baru dengan validity period. Ledger lama tetap menunjuk versi lama.

Zero DDL

Atribut profil baru

Tambah field JSON, naikkan schema version, validasi dengan JSON Schema, lalu update projection.

Zero DDL primary*

Multi-currency ledger

Jika belum tersedia sebagai invariant typed, lakukan migration dan update accounting rules.

DDL layak

Relationship bisnis baru

Tambah relationship type dan attributes selama constraint existing cukup.

Zero DDL

GL account mapping baru

Tambah pemetaan debit/credit account code melalui policy/configuration yang tervalidasi; kolom typed v4.0.0 tetap.

Zero DDL

ERP dimension fundamental baru

Dimensi yang belum memiliki invariant typed tetap memerlukan review model dan migration; jangan dipaksakan ke JSON.

DDL layak

* Perubahan searchable attribute mungkin tetap memerlukan perubahan konfigurasi/index Manticore. Zero-DDL database tidak berarti zero-governance.

User Journeys

Alur tulis selalu selesai di AWS Aurora MySQL 8.0 terlebih dahulu. Manticore diproyeksikan asinkron dan tidak dipakai untuk keputusan approval atau uang.

sequenceDiagram actor Applicant participant API as "S&DP API" participant MD as Masterdata participant DB as AWS Aurora MySQL 8.0 participant Relay as Outbox Relay participant MS as Manticore Applicant->>API: Self-register with MP-001 API->>MD: Validate external IDs MD-->>API: Valid API->>DB: Account, referral, outbox in one transaction DB-->>API: PENDING version 1 API-->>Applicant: Accepted Relay->>DB: Claim unpublished event Relay->>MS: Upsert newer sourceVersion Relay->>DB: Receipt and publish acknowledgement

Registration

Self-service stores a typed REFERRED_BY edge. Validated ERP vendor and cost-center references populate subledger_code and cost_center_code when applicable.

Touches: account, account_relationship, outbox_event

Verification

Document status lives in bounded JSON; approval audit is an idempotent typed activity.

Touches: account, activity_event, outbox_event

AWB & Commission

AWB activity is idempotent. Accrual pins activity/policy and records subledger, branch/cost dimension, financial period, and GL debit/credit mappings.

Touches: operational_transaction, activity_event, policy_document, ledger_entry

ERP AP Settlement & Projection

Billing callback settles the accrual and stores ERP AP voucher / journal batch references. Projection receipts make consumer processing auditable.

Touches: ledger_entry, outbox_event, projection_receipt

See USER-JOURNEYS.md for six complete sequence diagrams and exact columns touched.

v4.0.0 Partition & Query Operations

The complete executable runbook is partition-operations.sql: application computes partition_key=YYYYMM(updated_at), DBE pre-creates one _active and one _inactive LIST COLUMNS partition per month, and retention archives then drops only inactive partitions.

SQL Examples

Pilih skenario

Snippets are abbreviated for reading. The transactionally complete, rerunnable examples are in scenario-queries.sql; DDL and helper functions are in schemas.sql.

v4.0.0 Raw Schema & Sample Query

Read-only, exact release artifacts embedded in this explorer. Choose the Aurora MySQL DDL, executable walkthrough, or partition runbook. Use the copy button to copy the displayed artifact.

Production Guardrails

Transactional Outbox

Hindari dual-write DB + Manticore pada request yang sama.

Version Ordering

Projection membawa sourceVersion; event lama tidak boleh menimpa event baru.

Idempotency

Deduplicate berdasarkan event ID atau aggregate ID + version.

Schema Contract

JSON memakai schema_version, JSON Schema, validation, dan migration strategy.

Replay & Reindex

Manticore harus dapat dibangun ulang sepenuhnya dari primary DB.

Safe Policy DSL

Gunakan decision table/DSL terbatas, bukan arbitrary SQL atau JavaScript.

ERP Reference Validation

Validate subledger_code, cost center/branch, GL mappings, and open financial_period against ERP/Finance Master before writing the accrual.

ERP Scope Boundary

Only AP subledger, financial dimensions, accrual GL mapping, AP voucher, and journal batch references are in scope; no generic ERP modules.