How it works
Two AIs negotiate every recovery: one speaks for the database, one speaks for the business. A separate rulebook decides what may actually run, and recovery only counts when customers can buy again.
One recovery, step by step
- ObserveDatabase signals, plus the company’s records through Zetaris
- ProposeThe Database AI picks an action it actually observed
- ChallengeThe Business AI asks for evidence and weighs the costs
- AuthorizeA rulebook approves one exact action, or refuses
- VerifyCheckout is back above target and nothing protected was harmed
- LearnAn Auditor AI writes the report and stores the lesson
Why this is new
Two AIs that disagree on purpose
The Database AI wants the database healthy fast. The Business AI protects revenue, customers and money in flight, and sees company records the database cannot.
Agreement is not permission
Even when both agree, a rule-based authority checks the exact action against the live system. It approves once, for two minutes, or refuses. It can’t be talked around.
The business defines “fixed”
Typical agents stop when the database looks healthy. RecoveryPact stops when checkout is back above target.
It learns, carefully
Memory can stop a mistake from being repeated. It can never authorize an action on its own.
What each sponsor does
We took each one away, or attacked it, and re-ran the incidents.
Every signed answer is listed in the receipt log.