Honesty seal

Fair shuffle: cards are not fitted to the answer

OmenHall's core rule: the result is drawn first, then the interpretation is created. Beautiful text should not change drawn cards, orientations, or positions.

The symbol speaks after the draw, not instead of the draw.

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.

checklist

What the user should understand

  • The deck contains unique cards.
  • Orientations are created before reveal.
  • Deck cut happens before selection.
  • The result is not rebuilt after payment.
  • Customer UI hides unnecessary tech.

FAQ

Short answers

Can fairness be shown without hashes on screen?

Yes. Ordinary users need a clear process. Technical records are for internal checks, support, and audits, not the main result text.

If I refresh, do the cards change?

A sealed result should reopen the same result. A new reading is created only as a new action.

related doors

Where to go next