01
Bring Your Deck
Import what you actually play.
Loamoth starts from your real list, not a generic archetype template.
Experimental deck testing for Commander
Find what breaks. Keep what holds.
Real decks. Real questions. Real evidence.
Loamoth stress-tests the deck you bring, rejects changes that do not hold up, and keeps only what earns its place.
Controlled Alpha. Commander only. Interest signup does not guarantee admission.
Pressure reveals.
A change is not better because it looks stronger. It has to solve a real failure and survive the test.
Nothing changes until it earns it.
The Loamoth journey
Bring the deck. Define the question. Test it.
Loamoth teaches the workflow by doing. No chatbot maze, no setup wizard, and no endless confirmation gates.
02
Run Brief
See what Loamoth understood.
Confirm the objective, protected identity, constraints, environment, and what can defensibly be tested.
03
Experiment
Let the deck face pressure.
Loamoth tests hypotheses, evaluates candidates, challenges its own conclusions, and adapts autonomously.
04
Break Report
Get the conclusion first.
See what broke, what held, what changed, what was rejected, and what Loamoth learned.
05
Evidence
Open the full record when you want it.
Validation, conditions, provenance, limitations, and experiment history stay available behind the result.
Run Brief
What Loamoth understood, before it tests anything.
Loamoth infers the plan instead of forcing you through a questionnaire. You correct the brief only where it matters, then the experiment runs.
Run Brief
Eligible with limitations
Objective
Improve performance without replacing the deck's core plan.
Protect
Commander, deck identity, build-arounds, and declared constraints.
Environment
Commander tables, adversarial matchups, and pressure testing.
Testability
Claims stay bounded to what the available evidence can support.
Break Report
A clear result, including when the answer is no.
Loamoth is allowed to defend the baseline, reject its own proposed change, stop when the evidence is insufficient, or say the test did not complete.
A real failure was isolated.
The report connects the failure mechanism to the experiment and the change that addressed it.
The existing deck held up.
No change is treated as a valid result when candidates fail to earn their place.
The evidence was not enough.
Uncertainty stays visible instead of being converted into a confident recommendation.
The experiment stopped short.
Execution failure and experimental invalidity are reported rather than hidden.
Break Theory
Evidence before adaptation.
The system exists to answer a question, not to generate changes for the sake of activity.
ANALYZE. ADAPT. OVERCOME.
Contract
Define the question, the protected identity, and the limits of the test.
Integrity
Do not quietly change the experiment to make the answer look better.
Causality
Tie changes to observed failure mechanisms instead of generic upgrade logic.
Evidence
Separate observation, inference, uncertainty, conditions, and provenance.
Decision
Keep, reject, revert, or stop when the evidence justifies it.
Controlled Alpha / Commander first
Help us break the testing system.
Alpha access expands deliberately. We want testers who will challenge misunderstood decks, unsupported conclusions, broken workflows, and places where the evidence does not deserve confidence.
Submitting interest does not automatically grant access.