In a card game, a failed card is not always a dead end. Sometimes it proves that an idea is too narrow. Sometimes it shows that a mechanic needs clearer timing. Sometimes it reveals that a Pilot needs a different kind of support. If that failed version is simply deleted, the lesson can disappear with it.
AFB: Full Sync treats failed card candidates as part of the project’s design evidence. When a card misses its intended use case, the original version can remain in the record while a repaired version is created and linked to it. That means the project can keep track of what changed, why it changed, and what problem the repair was meant to solve.
Why this matters
AFB has many moving parts: Pilots, Mech Frames, Drones, Modules, Operations, Reactions, Prototypes, Hangar choices, and Full Sync pressure. A card that looks exciting in isolation can fail when it enters that wider ecosystem. Preserving the failed version helps show whether the issue came from power level, timing, access, wording, role overlap, or a missing support lane.
Repair instead of erasure
The repair workflow gives the project a cleaner way to improve cards without pretending the first version never existed. A repaired card can keep a visible relationship to the earlier candidate, while the earlier version remains available as design history. That helps avoid repeating the same mistake later.
Better card decisions
This approach supports a more deliberate card database. A card record can hold more than card text. It can track why a card exists, what it supports, what risk it creates, what kind of deck or Pilot it helps, and what evidence exists from simulation or review.
Not final balance
This does not mean every repaired card is finished or balanced. It means the design process is easier to inspect. AFB can keep weak versions, repair them, compare them, and learn from them before cards move toward future playtest selection.