Idempotency & Admission

Tentarc implements admission idempotency:

• dedupe happens before execution
• prevents repeated side effects from retries/double-submit
• does not rely on output caching

Admission contract

For every incoming intent:

1. normalize idempotency key
2. check duplicate window
3. accept or reject
4. remember admission result for replay safety

Pseudo-flow:

normalizeKey -> isDuplicate? -> reject_duplicate
                        \-> rememberAdmission -> enqueue_execution

Common duplicate scenarios solved

• user double-click send
• app retries after timeout
• two windows submit same operation
• reconnect after transient IPC/network issues

Practical implementation notes

• key should include workspace + instance + logical user action
• keep dedupe scope tight enough to avoid false positives
• expiration/retention should match retry horizon

Non-goal

Idempotency does not mean “same answer text.”
It means “same side effect is not executed twice.”