Separating draw from text
The site should first lock deck order, selected cards, positions, and orientations. Only then is the answer assembled from already selected material.
- A card is not chosen to match the text mood.
- Payment does not change the result.
- The oracle does not rewrite the drawn card.
- Reopening does not draw a new result.
Why clients should not see hashes
Technical proofs help audits, but they scare ordinary visitors. On the customer path, clear explanation, an honesty seal, and trust page are enough.
- A hash should not sit at the center of the result.
- The technical record should appear only where needed.
- The user should see meaning, not code bookkeeping.
Two decks and complex spreads
If a spread uses two decks, each deck should be shuffled separately. Each position should know which deck supplies the card.
- Main deck.
- Shadow deck.
- Position rules.
- Unified result seal.