Pegasus Docs
Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.
The collector’s workshop manual.
Everything you need to organize your inventory, build target decks, and turn a binder into clear, playable, cost-efficient options. Operating guide for serious TCG players — workflow-first.
01Browse by area
The docs are organised collection-first, not feature-first. Start where your workflow is.
From inventory to first analysis in five minutes. Best path for new accounts and migrating collectors.
- Quick start
- Core concepts
- Recommended workflow
Track owned quantity, location, and availability across binders and boxes — and keep physical copies aligned.
- Organize inventory
- Add and maintain cards
Construct target decks against your real inventory. Branch, iterate, and roll back when a swap underperforms.
- Build decks
- Manage deck versions
Consistency, coverage, risk — explained, not just scored. The bottlenecks that close the gap to playable.
- Analyze decks and scores
- Readiness and acquisition
- Compare and improve decks
Plan purchases against shortages, price confidence, and unlock value per dollar — what to buy, in what order.
- Readiness and acquisition
- Data sources and affiliation
What ships where. The scoring model in detail, public price feeds, and recovery paths for the rare bad state.
- Feature map
- Scoring model
- Troubleshooting
02Start with the loop
The repeatable workflow most operators settle on after a week of use.
gemma4 agent; EN remains the source of truth.combo-intel.03For developers
Pegasus is a workstation. The collection model is the API — everything in the app, you can script.
Readiness model
How readiness, coverage, and risk are computed. Inputs, weights, edge cases — and what each number means in practice.
Public sources
Public price feeds, attribution rules, and the non-affiliation posture that keeps Pegasus independent.
Troubleshooting
Import quirks, edition mismatches, and recovery paths for the rare bad state — with worked recipes for the common cases.
Stuck on something the docs don’t cover?
Pegasus is in alpha — gaps in the docs are gaps in the product, and we want to know about them. Open an issue on GitHub and we’ll triage within a day.