Competitive Information Asymmetry: Guidance on Ideals 1 and 5

Guidance on: The All Are One Ideals

Last updated October 9, 2026.

This guidance explains how transformerstcg.org applies the All Are One Ideals to a recurring question of game design, organized play, and community governance. It describes the application; it does not amend the Ideals.

• Primary Ideal: 1. We builders are pro-Transformers TCG community
• Primary Ideal: 5. We builders have the sustainability of the game in mind
• Related Ideal: 4. We builders are pro-format diversity

The first Ideal asks builders to keep players central and to support genuinely inclusive community participation. One recurring challenge to it is the subject of this guidance: in a game built and run by its own players, the people who design the cards and the people who administer the events compete against the people who do neither, holding information about the card pool and about the field that their opponents have no way to obtain. Both halves of that are volunteer work the game depends on, and both produce the same governance problem.

In brief

Some players contribute to the community in design rooms and event organization. That work gives them private information the rest of the field does not have access to: unreleased cards, testing results, balance decisions, abandoned designs, the assumptions a release was built on, and the decklists submitted to an event. That advantage exists whether or not anyone cheats, designs a card for their own benefit, or ever decides to use what they know.

transformerstcg.org answers it with a competitive lockout. Anyone holding meaningful private design access or privileged event information keeps playing: complete matches, real events, the same formats as everyone else, and some continued play is required to retain certain design access. What they cannot do is turn that access into competitive advancement. Their results earn no standing, qualification, ranked event win, or leaderboard points, because every match they play is recorded as a win for their opponent whatever happens at the table. Participation items that every entrant receives are unaffected. The lockout runs six months at minimum for private design access, a full competitive season for full-Wave designers, permanently for the game director, and for the event in question for an organizer holding privileged information about it. Those add up rather than replacing one another: where more than one applies, the lockout runs until the last of them expires.

The aim is to keep builders at the table without asking the field to take anyone’s word for it, and the rule protects the builders as much as the field: nothing turns on whether a designer’s private knowledge shaped a result, because it can never produce one.

The rest of this guidance sets out what the problem is, how it has recurred through the game’s history, what other competitive communities have done about it, and how the lockout applies in practice.

What competitive information asymmetry is

Competitive information asymmetry

A situation where some competitors hold privileged access to gameplay information that the wider competitive field does not have. That information can include unreleased cards, internal design discussions, private testing results, balance decisions, planned card changes, abandoned designs and earlier versions, intended interactions, the strategic assumptions behind a release, submitted tournament decklists, and any other private information with competitive relevance.

The advantage can become extreme. In some environments an active competitive player also serves as the design lead for an entire Wave of cards. A Wave can spend a long time in private pre-alpha and alpha development, and a designer in that role can accumulate years of familiarity with an environment before ordinary players see a single finished card. By release, that designer may carry knowledge of abandoned concepts, earlier versions, testing results, balance failures, intended interactions, proven counters, under-tested strategies, and the assumptions the release was built on. None of that can be recovered by reading the printed cards or by taking part in ordinary public testing.

Event administration reaches the same extreme by a shorter route. An organizer who receives decklists holds, before a single match begins, the one thing every competitor in the room is trying to work out about everyone else. Where the same person administers a season of events, that becomes a running picture of what the field is building, which decks are being abandoned, and what the opposition will bring to the next event. Neither kind of access is recoverable by a player who simply turns up and plays well.

The governance question is:

How much privileged information should someone possess while also competing against players who do not have access to it?

transformerstcg.org’s position is that builders should minimize avoidable competitive information advantages, and the reasonable doubts those advantages create, through safeguards that are structural rather than personal.

Access itself creates the advantage

A governance problem exists here without any finding of intentional abuse. A player involved in private development may know which strategies dominated internal testing, which decks consistently failed, which cards changed late, which counters proved effective, which interactions concerned the designers, which cards received comparatively little testing, and which future changes were already under discussion. Event administration raises a version of the same problem: an organizer holding submitted decklists knows what opponents are playing before those opponents know the same about them.

Some of that knowledge shapes decisions deliberately. Much of it simply becomes part of what a person understands about the game, absorbed into ordinary competitive judgment with no decision to use it ever being made. Either way, opponents do not have it. Good governance reduces the conflict in advance rather than relying on later investigation of anyone’s intent.

Throughout this guidance the distinction stays explicit: competitive information asymmetry establishes a governance risk. Cheating, deliberate misuse of confidential information, collusion, improper tournament results, and malicious intent are separate matters, each requiring separate evidence. Nothing in this guidance alleges any of them against anyone.

Advantage and doubt

The disparity is the problem. A designer, tester, organizer, or other privileged participant knows things ordinary competitors do not, and that is reason enough for a rule. The competitive lockout described below would be justified if no one ever noticed the disparity, and transformerstcg.org sets the policy on the disparity itself, not on how loudly anyone objects to it.

The disparity also produces a second effect, and it is worth naming because a rule that answers the first answers this one for free. Other competitors can usually see that the privileged information exists. What they cannot do is observe how much of it influenced a particular deck choice, matchup read, sideboard decision, card evaluation, or tournament result. That question has no provable answer, so a field asked to trust that years of accumulated knowledge have been mentally set aside is being asked something it cannot check. Its wondering is reasonable, and telling it that the privileged competitor means well leaves the structural question exactly where it was.

A structural rule settles both. If privileged participants cannot convert their position into standing, qualification, victories, or rewards, and cannot affect anyone else’s either, the advantage has nowhere to go, and the question of whether it was used stops mattering. That protects the credibility of results, and it protects the people holding the privileged access. The working standard is a structural one:

Governance should avoid conflicts that a reasonable participant can see but cannot independently evaluate.

How the problem arose in the Transformers TCG

The overlap is not new here, and it has never belonged to one group. What follows is the record of how it became the ordinary arrangement after the official game ended, what part transformerstcg.org’s own predecessor took in it, and where it stands in the environment running events today.

Designers competing in the environment they built

Vector Sigma, a group known for its intense focus on competitive play, was renamed Alpha Trion Protocols in late 2020, and under that name it combined competitive play with card development, so that the people who knew the most about an unreleased environment were also competing in the environment it produced. Several of its most prominent competitive players designed cards for it, and more than once they won the group’s own events.

That was the ordinary arrangement there for the group’s whole run, from the rebrand until it left the game in 2023, and nothing about it was hidden or unusual at the time. It is recorded here for that reason. The overlap this guidance is about was not one organization’s habit or one period’s mistake; it was how the post-cancellation scene generally worked, across groups that disagreed with each other about almost everything else.

Allied Crossplay, and Team Bayformers’ part in it

Allied Crossplay operated a “big tent” development model. It gave broad private design and testing access to many active competitive players, who then held information the wider field did not. Team Bayformers, the organizational predecessor of transformerstcg.org, accepted this model, participated in it, and helped operate within it.

Its weakness was the one this guidance is about. Competitors could help shape unreleased environments, observe internal testing, take part in balance discussions, see designs change or get abandoned, and later play against people whose knowledge began with the public card file.

The safeguards set out below came partly from that model’s failure. One lesson survived its end: widening the private circle does not remove information asymmetry as long as other competitors still lack equal access. The question is always whether some competitors can obtain meaningful private development knowledge that others cannot obtain on equal terms. When they can, the asymmetry remains, however many people are inside.

The fuller account is in The End of Allied Crossplay.

The contemporary environment

The overlap between designing and competing continues in the transformers.cards and “Transformers TCG Community” Discord environment, a separate fan project. Its most recent fan release was developed by people who also participate competitively in that same environment. A designer competing in an environment shaped by cards they helped develop may hold knowledge of earlier versions, testing history, abandoned concepts, intended interactions, balance concerns, and strategic assumptions that ordinary competitors cannot obtain, and other competitors can see the overlap while having no way to judge how much of that knowledge is in play on any given day.

The overlap is the point, and it is the same overlap the earlier sections describe.

When the conflict becomes explicit

In an April 2, 2026 episode of the transformers.cards podcast Alive on 1, Z-R0E and a co-host who also designs for it addressed why their designers play in competitive tournaments. Z-R0E develops transformers.cards, organizes the events run through it, co-hosts that podcast, and led Allied Crossplay from February 2023 until it ended that December. His part in the game is organizational more than it is design work, though he holds a seat in the design rooms, so both forms of privileged access this guidance describes apply to him at once. He competes in the events as well, which is the condition this guidance is about rather than an incidental detail about one person. The discussion was a response to a concern players had already raised. Z-R0E said it had been put to him that designers did well in tournaments “because you guys are the ones who designed the cards,” and he acknowledged elsewhere in the conversation that “for an outsider looking in, it’s weird that we’re playing,” before concluding that there is nothing wrong with it and that it has “only brought good.”

The speakers acknowledged the underlying information disparity directly.

We obviously know what the cards are. We’ve had more time to play with them.

Z-R0E noted that in many other games it is “kind of a faux pas for designers and testers to play in major tournaments,” and that he could “imagine why people might think” designers build the game to their own advantage. His response was an assurance about intent: none of them do. He then explained why designers compete anyway: they love the game, continued play is what keeps them working on it, and a “full separate testing team that didn’t play events” would take resources the project does not have.

Those points explain why the designers want to compete. They do not reduce the information advantage held over other competitors.

The co-host made the overlap more explicit. He described himself as “often the one holding the gate of like, can it go to beta or not,” and said that “for a lot of the time the competitions for me are very much I want to test some idea out.” He gave examples: entering a tournament with a deck built around a new stratagem to learn whether it was as dangerous as private testing had suggested, and entering another with an aggressive deck to see how hard a card under development could be hit. He described the loop running the other way as well, watching an opponent play a favorite archetype and thinking about what future support that archetype could be given. Z-R0E added that “a lot of our play of the game just in general is in tournaments,” because a scheduled event is what gets the group to make time.

That is a material difference between competitors. Ordinary entrants bring the public card pool and whatever they have learned from public play. A participant with authority over what reaches public testing may bring months of private repetitions, knowledge of earlier versions and abandoned interactions, internal balance discussion, and specific development questions they intend to answer through tournament play. The tournament serves two purposes for different participants: a competition for the field and, for some designers, by their own account, part of the development process.

The episode offered two further responses to the concern about designer success. Z-R0E said designers do well because they play a great deal, and the speakers observed that designers often compete with cards they did not personally create. Neither addresses the governance question. Frequent private testing is itself a source of the unequal information; familiarity gained through development does not stop being an advantage because it also makes someone a stronger player. And playing cards designed by someone else answers the narrower concern of self-dealing, designing cards to benefit one’s own deck. Information asymmetry comes from access to the development environment as a whole: the testing repetitions, the design conversations, the earlier versions, the failed approaches, the expected interactions, and the knowledge of what may come next. A designer gains that from colleagues’ cards as readily as from their own.

The speakers also described their response to exceptional cases. If a deck “seemed really good in one person’s hands and wasn’t working for anyone else,” the co-host said, “we’re going to nerf the hell out of this thing.” That is a reactive balance intervention. It does not govern the ordinary form of the advantage, which is incremental: better matchup expectations, sharper card evaluation, sequencing, deck selection, and sideboarding informed by interactions the field has not yet discovered. None of that produces an anomaly that triggers a nerf, and all of it is available to someone with months of private repetitions and to no one else.

The concern that players raised was structural, and every response to it was not. Assurances of good intent do not give other competitors the information. Enjoyment of tournament play does not give them the information. Using another designer’s cards does not give them the information. A promise to intervene if an advantage becomes conspicuous does not prevent smaller advantages from deciding results. The question put to him was a fair one, because the disparity it asked about is real, and it was answered with reasons the disparity should be tolerated rather than with anything that reduced it.

Z-R0E framed the practical alternative as a separate testing team whose members never compete, something he said a volunteer project could not sustain, and proceeded as though the conflict therefore had no affordable remedy. That was not the only structural remedy available to him, and it was not a hypothetical one. Allied Crossplay had already run on it. While [BF] billmoo led the partnership he was under a competitive lockout himself, openly enough that the field knew it. It rested on both grounds this guidance describes, because he held both kinds of access: he was the central designer behind World|Strike and Waste|Lands and he ran the events those releases were played at, and he did not advance in them. That arrangement ended when leadership passed to Z-R0E, and he chose not to continue it for himself. What stands in its place is the arrangement described above, in which the people holding development access compete without restriction and, by their own account, use tournaments as part of development. The shape of it is the one described here: designers keep entering events, playing complete matches, and testing against the field, and are excluded from competitive advancement. A lockout needs no second testing organization, no paid staff, and no removal of designers from tournament play. It separates privileged access from ranking, qualification, victories, and rewards while preserving exactly the play and feedback loop he said designers needed.

So the April discussion did not take place before a workable safeguard existed. One had been in force in that same project, it left designers free to play, and the project had stopped applying it. The episode’s answer, that a separate non-competing testing team is beyond a hobby project, addresses a more burdensome arrangement than the one his own project had been running, and does not mention that one. In that context the “perfect world” scenario functions as a straw man: a stronger and more easily rejected arrangement stands in for the narrower safeguard actually available, and everything the segment goes on to defend, designers playing, designers enjoying themselves, tournaments providing scheduled games, tournaments being useful to test in, volunteers staying motivated, is something the lockout never threatened. The segment gives substantial reasons why designers should remain active players. It gives no reason why privileged development access must also remain compatible with unrestricted competitive advancement, and the conclusion that the arrangement has “only brought good” is asserted against facts the segment itself concedes: the advance knowledge, the extra time with the cards, the use of tournaments to test, and the questions outsiders were already asking. The competitive lockout described below is that narrower remedy, adopted.

The episode illustrates one more thing. The person with the most privileged knowledge in that environment is also the person with authority over whether anyone in that position faces a restriction. A safeguard designed to manage a conflict of interest can end up subject to the approval of someone the conflict affects, which is not hypothetical here: the lockout stopped applying because the person it would have bound was the person who decided. Durable governance needs rules that apply to leadership even when they carry a real personal cost, and that outlast whoever holds the role.

What the episode documents, then, is more than an appearance of conflict. The concern was raised. A structural safeguard that left designers free to play had been in force in that same project and was no longer applied. The privileged access was acknowledged. The competitive overlap was acknowledged, including the use of tournaments for development. The responses offered explanations, assurances, and a stricter alternative described as unaffordable. The narrower safeguard the project had already used was not restored. That is the governance gap this guidance addresses.

The same question, about event administration

The designer side is not the only form this has taken. Deck lists for that environment’s events are submitted through transformers.cards, the site Z-R0E develops and the events he organizes and enters. He holds every submitted list, including the lists of the people he will be playing.

It was put to him early, and privately. While Allied Crossplay was still operating and billmoo was working under his leadership, billmoo raised the decklist access with him directly and proposed finding a handling arrangement for active lists, so that Z-R0E could compete fully without being the person holding them. By billmoo’s account the concern was brushed aside. It was raised again later and in public, by a player before one of those events.

Neither half of that is a problem on its own. An organizer holding submitted lists is ordinary event administration, and a volunteer who builds the tools entering the events is ordinary small-community play. What has no answer is holding the lists and competing for standing at the same event, because the two together leave the field unable to tell what it is playing against.

The arrangement did not change. It carried through to the environment’s own championship events, and at no point did he exclude himself from competitive advancement. He won one of their tournaments. The complaints were answered the way the podcast answered the designer question, with an assurance that the access would not be abused. Either half could have been given up and the problem would have gone with it: hand the lists to someone else, or enter without standing. Neither was.

Nothing here says the lists were read or used, and that is again the point. This is the easier version of the problem to see, because the information is not diffuse. Development knowledge accumulates over years and resists description. A submitted deck list is one document, held before the match, naming exactly what the opponent will play. Nobody has to be told how an advantage of that kind would work, which is why the question arrived from a player rather than from a policy document.

That is also what makes it the clearest failure of the standard set out above. Governance is meant to head off conflicts a reasonable participant can see but cannot independently evaluate. This one did not have to be anticipated in the abstract, because it was anticipated out loud, in advance, by someone about to play in the event. Learning of a foreseeable problem from the person it affects is the last moment at which it is still cheap to fix, and here it had been raised earlier than that, in private, by a partner who offered to help build the fix. An assurance was given instead, which leaves the participant exactly where they started: able to see the conflict and unable to check it.

A small volunteer game still needs safeguards

transformerstcg.org does not assume it can keep designers, testers, organizers, judges, administrators, and players in fully separate groups. Its policies are built around the fact that people will occupy several roles at once.

The governance question is what those overlapping roles should be allowed to produce. A volunteer project does not need a paid testing department to distinguish continued play from competitive advancement. That distinction is what lets builders stay at the table without asking the field to accept an avoidable conflict, and it is the whole of the transformerstcg.org approach. It is also, as the two sections above record, the distinction the other environment declined on both the design side and the event-administration side.

The problem extends beyond the Transformers TCG

Competitive gaming communities have repeatedly confronted players who received strategically meaningful information earlier or more extensively than their opponents. The conclusions those communities reached varied. What recurs is the recognition that the situation itself creates a concern, or an appearance, that has to be answered.

In 2011, reigning Magic: The Gathering World Champion Guillaume Matignon had authorized advance access to the complete confidential card file for the unreleased New Phyrexia set through his work for the French magazine Lotus Noir. After he shared it with fellow professional Guillaume Wafo-Tapa and it eventually leaked publicly, Wizards of the Coast suspended Matignon for three years, and suspended three others until October 2012. Contemporary commentary separately raised the structural concern: an elite competitor with comprehensive advance knowledge of a set could receive weeks of deckbuilding, testing, and metagame preparation unavailable to the field, and the writer raising it was explicit that he was not alleging the advantage had been used, only that the access “requires us to ask the question.” The documented violation was disclosure of confidential material. The relevance here is narrower: an elite competitor held comprehensive knowledge of an unreleased environment through a trusted role, and the questions began the moment that became known.

Comparable concerns appeared in Warhammer 40,000 in November 2021, when a public debate over whether Games Workshop playtesters should compete in tournaments named advance codex access, additional preparation time, familiarity with forthcoming armies, and possible influence over future material as the advantages at issue. The debate was set out as a case for and a case against, and the author’s own conclusion was permissive. The asymmetry itself was openly recognized on both sides, and the case against noted that other competitive games either forbid playtesters from competing or restrict what they may play.

Other competitive systems respond to information disparity by equalizing access. Magic’s tournament rules protect strategically useful deck information during competition, and at certain Premier events opponents receive each other’s decklists at the start of a round specifically “to minimize advantage created by certain lists being made public by coverage.” The principle is that competitive fairness, and confidence in it, can depend on who holds strategically meaningful information and when they receive it.

Disputes over prematurely disclosed decklists at the 2024 Yu-Gi-Oh! World Championships and Magic World Championship XXVII in 2021, where the lists were exposed three days before the event, and criticism over a leaked privately developed deck before a 2025 Pokémon TCG Regional Championship, show that competitive communities treat advance strategic knowledge as consequential even when every card involved is already public. At the Yu-Gi-Oh! event, one argument for publishing every list was itself an asymmetry argument: remote observers would otherwise compile the same information and pass it selectively to friends in the field.

None of these establish a universal solution, and in several of them the size of the advantage was disputed or never measured. What they share is that the disparity was recognized as consequential by the people affected and, in several cases, by observers with no stake in the dispute, whether or not any advantage was ever shown to have been used.

Together the cases establish a recurring problem: who knows strategically meaningful information, when they know it, whether the wider field has had a reasonable chance to develop comparable knowledge, and how the field will read the situation when the answer is no. transformerstcg.org answers the first three questions by rule, before privileged knowledge can become competitive advancement, and the fourth takes care of itself.

What a competitive lockout is

A competitive lockout does not prevent anyone from playing Transformers TCG events. A locked-out participant can enter events, play complete matches, test decks against the field, experience competitive formats, and take part socially. transformerstcg.org strongly encourages people with design access or event responsibilities to keep playing, and some continued play is required to retain certain forms of private design access.

A competitive lockout prevents competitive advancement. A player under competitive lockout cannot advance in organized-play standings, improve their qualification standing, win a ranked event, qualify through an event, or earn leaderboard points, whatever the results of their matches. Leaderboard points are the foundation of competitive advancement, so they fall on the same side of the line as standing. What a locked-out participant may receive is anything an event gives every entrant for turning up, because an item that does not depend on performance cannot be produced by privileged information. For standings purposes, every match they play is recorded as a 2-0 win for their opponent, whatever happened at the table. The game itself is played normally, for the benefit of both players. Fixing the result in advance is what closes the question completely: a locked-out participant’s knowledge cannot earn them standing, and it cannot cost their opponent any either, because nothing either of them does at the table moves the record.

The intent is simple: continue playing, continue learning, and continue contributing, without using privileged access to advance over players who lack it. The field can see that a participant with private knowledge cannot turn it into standing, and the system asks nothing of anyone’s trust.

Lockout structure

The lockout scales with the depth and persistence of the privileged information involved. It runs in one direction only. Private development access restricts competitive advancement; competitive success does not restrict anyone’s path into design, because a strong competitor bringing public knowledge into a private room is an advantage that belongs to the release, and therefore to everyone.

The tiers are cumulative, not alternatives. Where more than one applies to the same person, the lockout runs until the last of them expires. Leaving a role ends the lockout that belongs to that role, and nothing more. The game director is the clearest case. The permanent lockout attaches to the role, so stepping down releases it, but the role is a design role: a game director who is not helping build the current Wave is not doing the job. A departing game director is therefore always inside the season lockout for the Wave they helped design, and stays locked out at least until that season ends.

Each tier is set out below, with the reasoning for its measure.

Meaningful private design access

Meaningful private design access, including pre-alpha or alpha access to any release, carries a minimum six-month competitive lockout. Six months is the floor. For releases smaller than a full Wave, including supplemental releases and promotional products, the lockout is set by the scope of the release, the depth of access, the person’s development involvement, and the release’s competitive significance. These lockouts will usually sit near the minimum. Greater involvement can warrant more.

The purpose is to put meaningful distance between privileged knowledge and competitive advancement while keeping contributors engaged, and to make the boundary visible. Players do not have to judge whether someone with recent private access is compartmentalizing it successfully. The policy has already answered the competitive question.

Full-Wave designers

Anyone who helps design a full Wave and holds pre-alpha or alpha access remains locked out for the entire competitive season supporting that Wave. transformerstcg.org seasons generally last twelve to eighteen months. This applies regardless of whether the six-month minimum has already passed.

The public field deserves time to develop its own knowledge of an environment: to discover interactions, develop archetypes, identify counters, refine decks, solve hard matchups, and build collective experience through public play. Wave designers carry knowledge of earlier versions, abandoned cards, private testing, internal balance decisions, and intended interactions that ordinary players can never fully reconstruct from the released file. A season is the time it takes for the field to catch up on what can be caught up on, and by the time the restriction expires, both the gap and the reasonable perception of it have had a full season to diminish.

Game director

The game director of transformerstcg.org is under a permanent competitive lockout.

The role carries full-Wave design work and persistent access, across releases and seasons, to unreleased cards, long-term development plans, testing results, balance discussions, abandoned concepts, future releases, and accumulated institutional knowledge. That knowledge keeps growing, and no cooling-off period can meaningfully exhaust it. The restriction therefore belongs to the role. A current or future game director cannot waive it because they would like to pursue competitive advancement, and leaving the role releases only this lockout, not any other that their design access has already started running. The game director is still encouraged to play, and their participation can never generate standing, an event victory, qualification, or leaderboard points.

This is the direct answer to the conflict described earlier, and it is not a new rule so much as a restored one. The same lockout governed the Allied Crossplay leadership before it lapsed, which is the plainest evidence that a volunteer project can carry it: it already did. A safeguard has limited value if the person with the greatest access can set it aside when it conflicts with their own ambitions, so transformerstcg.org applies its strictest rule to itself first. It is also the clearest public signal the policy sends: players never have to wonder whether the person with the most inside knowledge is competing against them for standing, because the answer is settled before any event begins. The greater and more persistent the information advantage, the stronger the safeguard.

That is also why a restriction of this kind has to attach to a role rather than to a date. The position described there held the full range at once: a seat in the design rooms, the platform the events run on, the administration of those events, the decklists submitted to them, the podcast that spoke for the project, and the authority to decide whether anyone holding all of it faced a restriction. Taken separately, the design access would be one tier of this policy and the event administration another. Held together and carried across releases and seasons, the access is replenished faster than any cooling-off period can exhaust it, which is the condition this tier exists to answer. It carried no restriction at all.

Event organizers with privileged information

Event organizers with access to privileged competitive information, such as submitted decklists, private event administration, design rooms, or other strategically meaningful information unavailable to participants, are competitively locked out at the events that access covers. They can keep playing, which lets organizers help fill their own events. Their matches count for nothing in the standings and earn no leaderboard points.

This tier is measured by event rather than on a clock, and deliberately. Design access is dated: a release ships, a season runs, and the information ages into something the field can reconstruct. Decklist and event information does not age that way, because it is about the present field rather than an unreleased card pool. It also does not accumulate, because each event supplies its own to whoever administers that one. So the unit is the event. Someone who handles decklists for a single event is locked out at that event and nothing further. If they hold no privileged role at the next one, and are not an active designer or inside a design-access cooldown, they compete at it fully.

The practical form this usually takes is the simplest one: somebody else receives the lists. An organizer who wants to compete for standing at their own event can hand registration to another person for that event, and the question disappears without anyone leaving the room.

The governing principle across all four tiers:

Someone entrusted with information unavailable to the wider competitive field may continue to play, but cannot convert that privileged position into ranking, qualification, victory, or rewards.

Public Beta and Harmony

Public Beta establishes a shared current card-file boundary. Once a release enters Public Beta, everyone can access the same published version. Competitive players can optimize decks, stress-test interactions, expose balance problems, challenge design assumptions, and provide the high-level feedback that private rooms cannot match for breadth. This is where transformerstcg.org wants competitive expertise applied: everyone sees the same cards and evaluates the same material. The Harmony modifier can then admit a designated Public Beta release into organized play, with clear notice to organizers and players that the event includes material still under public testing; see Harmony on the Formats page.

Publication cannot erase accumulated private knowledge. Private rooms still contain the historical and developmental information that Public Beta participants never had: earlier versions, abandoned concepts, testing history, and internal balance discussion. The competitive lockouts address that residue. The two safeguards answer different halves of the same problem: a meaningful Public Beta gives the wider community the current material and a real chance to change it, and the lockouts address the development history that publishing cannot make equal.

Continued play matters

transformerstcg.org does not want its designers or its organizers isolated from the game. Builders should experience current formats, current player behavior, real decks, unexpected interactions, and the evolving rhythm of play. A designer who stops playing loses touch with the environment they are building, and an organizer who stops playing loses touch with the events they are running, which is why some ongoing play is required for certain forms of design access, and why a lockout restricts advancement rather than participation.

Separation protects builders

Clear lockout rules protect builders as much as they protect the field. A designer or an organizer can enter an event without creating any ambiguity about whether their privileged knowledge can improve their ranking, because it cannot. A designer who wins a game while locked out has simply played a good game; there is no standing, qualification, or reward attached that would require anyone to ask whether private knowledge contributed. Structural rules remove the occasion for suspicion, accusation, and retrospective investigation of intent. Nobody has to be asked whether they used what they knew, because nothing turned on the answer. The lockout closes the question in advance, for the builder’s benefit as much as anyone’s.

Competitive players remain essential

Competitive players provide expertise no one else does. They optimize quickly, expose weaknesses, test interactions aggressively, and stress systems in ways other players may not, and Ideal 4 recognizes competitive play as one valid way to engage with the game. The concern this guidance addresses is narrow: privileged access combined with competitive advancement. A healthy development process hears from competitive players alongside casual players, collectors, returning players, new players, organizers, and people exploring unconventional strategies. No single group represents the whole game.

The problem can reinforce itself

Left unaddressed, concentrated overlap between development and competition tends to compound. Competitive priorities can become overrepresented, as a highly competitive internal group optimizes around top tournament play at the expense of casual, thematic, and newer-player experience. Feedback can become circular, when the same people shape an environment, compete within it, and then produce the results used to judge it. Access can become socially concentrated, as people already close to development gain more opportunities and appear increasingly qualified for the next. And new competitors begin farther behind, facing opponents with years of developmental familiarity on top of ordinary experience. These are risks rather than certainties. Clear boundaries reduce their likelihood and make the system easier for outsiders to trust.

Guidance under Ideal 5

Ideal 5 asks builders to keep the sustainability of the game in mind. A game becomes institutionally fragile when the same small circles repeatedly design cards, privately test them, balance them, compete with them, organize the events, and evaluate the results. Durable institutions need safeguards that survive individual personalities and assurances of good conduct, and that survive the preferences of the people most affected by them. Competitive legitimacy should not depend on leadership continually asking the field to trust that a conflict everyone can see has no effect. For a game without an active official publisher, these boundaries matter more, not less.

What this guidance establishes

Competitive information asymmetry establishes a governance risk and can create a reasonable appearance of conflict. Both are distinct from an allegation of misconduct, which would need its own evidence. The safeguards here remove the opportunity for privileged information to affect competitive advancement, and with it the circumstances in which players are left unable to tell whether it did.

The Transformers TCG has repeatedly placed people in overlapping roles as competitors, organizers, designers, testers, rules authorities, and community leaders, and some overlap is unavoidable in a small volunteer game. Experience has shown that private development access, privileged event information, and meaningful competitive advancement deserve deliberate separation. transformerstcg.org reached that conclusion through observation and through experience, including systems its own predecessor took part in. Leadership elsewhere inherited a lockout of exactly that kind and set it aside. Asked afterward about the advantage its designers held, it acknowledged that they knew the cards earlier, had played them longer, and used competitive events to test what came next, then answered with explanations and assurances rather than by restoring the safeguard. transformerstcg.org adopted it.

• Meaningful private design access: minimum six-month competitive lockout.
• Full-Wave pre-alpha or alpha involvement: competitive lockout for the entire supporting season, generally twelve to eighteen months.
• Game director: permanent competitive lockout, attached to the role.
• Privileged event administration: competitive lockout at the events that access covers, one event at a time.
• More than one of the above: cumulative, running until the last of them expires.

Designers, organizers, and leaders keep playing. Continued play is encouraged and may be required for design access. Locked-out participants cannot convert their play into standing, qualification, victories, or leaderboard points, and receive whatever an event gives every entrant. The policy protects competitive fairness, and confidence in it follows.

That is how transformerstcg.org keeps players central, which is Ideal 1, and builds institutions capable of sustaining the game for the long term, which is Ideal 5. The strongest expression of the policy is its application to transformerstcg.org itself: the people with the greatest privileged access accept the greatest restrictions on competitive advancement.