Core concepts

Pegasus works best when each card copy has a clear operational role. The app is not only a deck list manager. It tracks how a physical collection supports many possible decks.

Inventory

Inventory is the set of cards you own. Each inventory row should answer:

• what card is this?
• how many copies do I own?
• where are those copies?
• are they available or already committed?

Inventory accuracy is the foundation for every readiness and acquisition result.

Location

A location is the physical place where a card can be found. Use locations that match real storage habits: binder, deck box, staples box, trade binder, or unsorted.

Locations are for retrieval and maintenance. They should be stable enough that you can keep them updated.

Available copies

Available copies are owned copies that are not already reserved by another target deck or physical deck commitment.

This matters because owning three copies of a staple does not mean every saved deck can use those three copies at the same time.

Target deck

A target deck is a list you want Pegasus to evaluate. It can represent:

• a deck you already play
• a deck you want to build
• a test list
• a benchmark or reference list

Readiness and acquisition depend on target decks.

Deck version

A deck version records a meaningful change to a deck list. Use versions when you want to compare the effect of edits instead of overwriting the old state.

Examples:

• v1: original import
• v2: lower deck size and add more starters
• v3: side-deck update for a local format

Readiness

Readiness answers whether a target deck can be built from your current inventory.

It looks at required copies, owned copies, available copies, and shortages. A deck can be mostly owned but still not ready if key cards are committed elsewhere.

Acquisition

Acquisition turns shortages into a prioritized buying plan.

The goal is not “buy everything”. The goal is to identify the purchases that unlock the most useful deck value for the least wasted spend.

Quick Analysis

Quick Analysis combines structural coverage and browser-side simulation.

Coverage asks why the deck should work. Simulation checks how often the deck produces playable hands under repeated samples.