AI contract

Kipper AI contract

AI must not turn Kipper into pretty mush. It must hold role, position, document layer, waiting, risk ledger, and archive.

01

Input packet

AI must receive not just a question, but a sealed packet: 36-card deck, chosen spread, positions, cards, shuffleCount, drawActor, language, scene, and safety rules.

  • Cards cannot change after interpretation.
  • Reversals are not used.
  • Role, paper, and waiting are passed explicitly.

02

Output JSON

The answer must return direct_answer, social_scene, role_map, document layer, waiting corridor, card evidence, proof chain, social risk ledger, archive trace, and next_best_format.

  • No free-flowing pretty text.
  • All fields are checked by quality gate.
  • Weak answer goes to repair loop.

03

Repair loop

If the answer fails to name a card, confuses role with identity, promises an official outcome, or gives no practical step, it is not shown to the client.

  • Repair proof.
  • Soften dangerous claims.
  • Add archive Echo.