Workload classes

4. Workload Classes

Each syncable table MUST declare one mutation class.

4.1. APPEND

Rows are immutable after publication.

Permitted operation:

INSERT

Native representation:

PME-encrypted Parquet data object

4.2. APPEND_DELETE

Rows are immutable after insertion but may later be logically removed.

Permitted operations:

INSERT
DELETE

Native representation:

PME-encrypted data objects
+
encrypted delete objects

4.3. MUTABLE

Rows may be updated concurrently.

Permitted operations:

INSERT
UPDATE
DELETE

Native synchronization remains SSP/1 change events.

4.4. Classification is semantic

Mutation class MUST NOT be inferred from recent behavior.

A table that requires resurrection, concurrent replacement, or arbitrary updates SHOULD be classified MUTABLE even if updates are rare.

Example:

Table	Mutation class
datasets.health_samples	APPEND
datasets.location_history	APPEND_DELETE
datasets.browser_history	APPEND_DELETE
datasets.imported_transactions	APPEND_DELETE
entities.people	MUTABLE
catalog.*	MUTABLE
surfaces.*	MUTABLE
preferences.*	MUTABLE