More than an order ticket
A prediction market position is usually described as a simple choice: buy YES, buy NO, or do nothing. That is enough for a one-off view. It stops being enough when the view has a lifecycle: conviction can improve, weaken, or become less useful as a market approaches resolution.
A prediction market strategy builder turns that lifecycle into a visible plan. Instead of trying to remember a rule such as “take some profit if this reaches 72 cents, then keep the rest,” you express the rule alongside the capital it governs. In Miramarket, the goal is not to automate a vague instruction. It is to make every conditional route legible before it can run.
The Miramarket node model
Miramarket uses two alternating building blocks. An action moves capital: enter a market or return capital to a wallet. A condition observes a signal such as price or time and decides whether a downstream route can activate. Conditions do not hold capital themselves; they connect a chosen trigger to explicit actions.
That distinction is deliberate. A strategy tree starts with an action, then nests a condition under the position it watches. The actions triggered by that condition remain visually grouped with it. A reader can answer three important questions by following the tree: what is held now, what is being watched, and where does capital go if the condition is met?
This differs from a list of alerts or disconnected limit orders. An alert says a price changed. A conditional strategy records what should happen next, how much capital is affected, and whether some of it should stay exposed while the rest is protected.
A worked example using a live Polymarket market
On July 17, 2026, Polymarket's “Will Argentina win the 2026 FIFA World Cup?” market was trading YES around 0.4115. The market had roughly $8.9 million in reported liquidity, a 0.001 quoted spread, and a July 20 resolution date. Those facts do not make the trade good or bad. They make it a useful example of why a position should carry rules before an event gets closer.
The example below starts with a $1,000 illustrative YES position. If the price rises above 0.72, the strategy sells 30% and preserves 70% of the exposure. It is not a recommendation to buy Argentina. The numbers are model parameters: a thesis, a trigger, and a partial-exit rule that can be inspected together.
Model strategy
Take profit while retaining exposure
A price condition above 0.72 sells 30% of the illustrative $1,000 Polymarket YES position, leaving 70% in place. Illustrative only; not financial advice.
A price condition above 0.72 sells 30% of the illustrative $1,000 Polymarket YES position, leaving 70% in place. Illustrative only; not financial advice.
The useful part is the audit trail. The root action states the venue, market, outcome, and allocation. The condition states the observed signal and threshold. The partial-exit action states exactly how much of the position changes. Anyone reviewing the strategy can challenge any one of those choices without guessing what an automated instruction means.
Review the logic before it becomes automation
A strategy builder is valuable when it makes the hard questions unavoidable. Is 0.72 an outcome-price trigger or a return target? What happens if the market moves quickly? Does returning funds to a wallet make more sense than rolling them into another market? Does the position need a time-based exit as resolution approaches? The correct answer is specific to the user and the market; Miramarket's job is to make the answer explicit.
That is why we describe Miramarket as conditional trading automation rather than a black-box prediction market bot. Users create, review, and deploy the if/then logic. The system gives that logic a readable structure across supported venues such as Polymarket, Kalshi, Limitless, and Opinion Labs. It does not replace due diligence, market rules, liquidity checks, or jurisdictional eligibility.