Security
Data integrity
Tamanor persists content and reputation atomically, ingests idempotently, uses account-level leases, and enforces referential integrity to prevent orphaned records.
Consistent by construction
Each piece of content and its reputation record are written in one atomic transaction. Ingestion is idempotent, so the same item is never duplicated. An account-level lease prevents overlapping syncs, and referential integrity prevents orphaned records.
Frequently asked questions
- Can a sync create duplicates?
- No — ingestion is idempotent on a unique key, so re-processing an item deduplicates it.