How the oracle works
A realistic digital deck without card tampering
This project is built like an oracle room: question first, then shuffle, cut, card selection, locked record, and only then interpretation.
1. The question is fixed before the cards
The client first sets the topic and question. These values enter the reading seed record and do not change after the ritual begins.
- The question receives a gentle quality check.
- The system discourages dependency on another person's will.
- Sensitive domains remain framed as self-reflection.
2. The deck is truly shuffled
The virtual deck contains 78 unique cards. Order is created through SHA-256 Fisher-Yates, not by choosing cards to fit the question.
- A card cannot repeat within one deck.
- Two-deck spreads use separately shuffled decks.
- A self-test confirms algorithmic reproducibility.
3. Orientation is hidden and not user-controlled
Upright or reversed orientation is created with the deck before selection. The user cannot set reversal odds and cannot see orientation before reveal.
- Orientation has its own hash.
- Interpretation cannot change card orientation.
4. The deck is cut before selection
After shuffling, the client or oracle cuts the deck into three piles. The pile order changes the technical deck order before card selection.
- The client can cut the deck manually.
- The oracle can cut the deck on the client's behalf.
- The cut is stored in the locked record.
5. Cards are selected by the client or oracle
The client may choose hidden cards from the scattered deck or ask the oracle to draw from the top after cutting.
- Cards enter spread positions in strict order.
- Two-deck spreads know which deck feeds each position.
6. AI does not choose the cards
After the reading is locked, an AI-ready packet is created. The future AI layer can only interpret the already selected cards, positions, and orientations.
- Cards cannot be changed after interpretation.
- No guaranteed future outcomes.
- No fear, curses, or pressure-based upsells.