Arcana Codex: A Software Architecture Tarot

Seventy-eightSeventy-eight cards, one question, and a reading of your project's past, present and probable future. Draw a spread below, click each card to turn it over, and see what the deck makes of your migration.

Why a Tarot Deck for Software

AA tarot card does very little on its own. It hands a group a picture and an excuse to talk. That is also what a good retrospective needs: a way to raise the outage everyone is avoiding without pointing at whoever pushed the change.shared vocabulary cuts through blame

Software already has its archetypes. Every team knows the God Class, the Forgotten Server and the Flaky State, and has a story about each. The deck gives those recurring shapes faces, so "this feels like the Circular Dependency" becomes a sentence people can say in a meeting.

The Deck

TheThe structure follows a standard tarot deck: 22 Major Arcana and 56 Minor Arcana.

The Major Arcana carry the large forces of a project's life, from The Greenfield (0) through The Monolith (IV), Technical Debt (XV) and The Outage (XVI) to The Release (XXI). Each has a tarot counterpart. The Debugger is the Hermit, The Code Review is Justice, The Unknown Unknowns is the Moon, The Retrospective is Judgement.

The Minor Arcana come in four suits, each covering one layer of a system:

Suit	Domain	Sample cards
Messages	How parts of the system talk	The Handshake, The Race Condition, The Distributed Tracing Nightmare
Structures	How the code is shaped	The Clean Interface, The God Class, The Deep Hierarchy
States	What the system remembers and when it changes	The Happy Path, The Hidden Mutation, The Eternal Spinner
Nodes	Where the system runs	The Load Balancer, The Network Partition, The Forgotten Server

Each suit runs from Ace to Ten, then Page, Knight, Queen and King. The court cards are roles: in Messages, the Client, the Courier, the Gateway and the Broker.court cards: the human roles in the system

Reading the Cards

EveryEvery card can land upright or reversed, and each orientation has its own meaning. A reversed card is rarely the opposite of an upright one. The upright Fresh Instance is a clean start; reversed, it is an instance nobody configured and nobody remembers. Each reading ends with advice drawn from the cards that came up.

Four spreads are built in:

• Sprint Triad (three cards): past context, present blocker, eventual release. The everyday reading for a milestone or a stalled project.
• Retro Icebreaker (one card): each person says in a sentence or two how the last iteration felt, using the card as a metaphor, then passes the deck on.
• ADR Constraints (three cards): a design prompt built from the cards drawn, plus a skeleton Architecture Decision Record to fill in.
• Project Storytelling (five cards): the arc of a project told as a narrative, useful for onboarding or a post-mortem.

Readings can be copied as text or as a link that restores the same cards, in the same orientation, for whoever opens it.

Try It With a Team

DrawDraw the Sprint Triad before your next planning session, with the real question on the table, and give the group five minutes with the three cards before anyone reads the interpretations aloud. Compare what people saw in the pictures with what the text says. Disagreements between the two are usually the most useful part of the reading.

The deck is a conversation prompt. It says nothing reliable about your release date.