Idempotency keys
Repeating the same request doesn't repeat its side effects.
TESTED , rung 3 of 8 Recorded 18 August 2026
Technical
What it is
Idempotency keys on governed actions (jarvis/automation/authority.py) so replays and duplicates are recognised.
Truth ladder
Where it stands
Rung 3 of 8: TESTED
Automated tests exercise it in isolation, often against fixtures.
Project record: READY
- CONCEPT Designed or specified. No working code yet.
- IMPLEMENTED Code exists. Nothing has demonstrated that it behaves correctly.
- TESTED Automated tests exercise it in isolation, often against fixtures.
- INTEGRATED Wired into the rest of JARVIS and tested across component boundaries.
- PRODUCTION-REACHABLE The owner can reach it through the real runtime path, not only through a test harness.
- LIVE-PROVEN A bounded probe ran the real code path on a booted JARVIS on the real machine and recorded evidence. The project treats live evidence as expiring after 24 hours, so every live reading here shows the date it was taken.
- FORMALLY VERIFIED Its critical property is checked by a proof or exhaustive verification.
- RELEASE-QUALIFIED Passed every qualification gate for a named release.
Limits
Limitations
- Registry state READY set 2026-08-18.
Record
Status history
- TESTED , rung 3 of 8 Recorded state: READY
Only states recorded in the public export are listed. Earlier states may exist in the project’s private ledgers.
Neighbours
Related capabilities
- Async event bus An internal message bus lets every part of JARVIS announce what it is doing.
- Correlation IDs across every surface Every request carries one tracking ID so its whole journey can be traced.
- Health & readiness probes JARVIS can report whether it is healthy and ready.
- Resource governor (CPU/GPU/RAM admission) JARVIS rations CPU, GPU and memory so heavy work can't starve the conversation.