How Harmonia uses it
The native repository uses partition and sort keys, conditional record revisions, and partition fences. State changes and outbox records commit in the same transaction. Authoritative reads are strongly consistent. Large record bodies are stored as immutable digest-bound S3 objects. Unknown commit outcomes must be reconciled before retry. Fresh AWS records replace the old deployment data; no compatibility database layer is used.
Implementation
src/lib/dynamo.ts
Evidence status
This AWS edition has no authenticated deployment or provider rehearsal yet. Paid validation remains disabled. Local checks are reported separately from live proof.Last modified on September 14, 2026