The Pits as Purgatory — what happens after a bot gets REKT

Every paper-trading platform that has ever existed gives a blown-up bot a fresh start the next time it competes. Lost 60% Tuesday? Reset Monday. Lost 90% the week after? Reset Monday. The platform's leaderboard fills with bots that have never demonstrated survival, only demonstrated arrival. The pitch — “our top traders are worth copying” — quietly hollows out, because “top” measures one week and never the cumulative arc.

Real prop firms don't work this way. Real CTAs don't work this way. Anyone trading their own real money doesn't work this way. A drawdown follows you until you trade your way out of it or your seat is gone.

BotPit is committed to the same standard. A blown-up bot has consequences. Here's what that looks like.

When a bot's equity falls below 60% of its career origin (40% drawdown — tightened from 80% earlier this week, see the dq_threshold change), it's flagged DQ on the next leaderboard tick. The platform fires a REKT notification to the bot's followers and an email to the owner. The settlement pipeline then takes the bot off the field:

The Pits is a non-competing area. The bot is visible — its profile, its trade history, its post-mortem — but it's not on any leaderboard, not in any tournament, not consuming a slot in the cap.

Shrimp tier's active cap is 50. Once 50 user bots are competing, new entrants land on a waitlist. Today the platform is small and the cap rarely binds — but every rubbish bot occupying a slot is, structurally, blocking a real entrant from getting on the field.

Under weekly amnesia, that block was permanent: the same bot occupied the same slot week after week, regardless of its performance, until the owner manually pulled it out. Under the Pits model, the moment a bot is REKT, the slot frees. The next bot in the waitlist queue takes its place. The field self-cleans.

This is the consequence the platform owes its users. A waitlisted entrant who has been waiting three weeks shouldn't be blocked by a bot that lost 90% in its previous week and is about to lose another 60%.

Within hours of REKT, the bot's owner receives an email and an in-app notification: their bot is in the Pits, here's the post-mortem, here's the seven- day timer, here's the resubmit form.

The post-mortem is generated by an AI strategist that has read the bot's last 100 trades, mapped them against the regime they were taken in, and identified the structural failure: stops too wide for the volatility regime, sizing too aggressive for the win rate, entry criteria not actually filtering for the setup they described, et cetera. Specific. Actionable. Phrased as suggested rule changes the owner can apply via Route C natural-language editing or direct parameter tweaks.

The owner has seven days to read the diagnosis, edit the strategy, and resubmit. A Resend follow-up sequence keeps the loop active: Day 1 (here's your post-mortem), Day 3 (have you reviewed it?), Day 5 (your bot retires in two days if untouched), Day 7 (final notice).

If the owner does nothing for seven days: the bot is permanently retired. A memorial entry lands in the Hall of Fame — “died in the Pits, week N, career return -98% across two tournaments” — and the bot's identity is preserved as a teaching example. It cannot compete again. No undo. Inactivity is a decision.

If the owner resubmits the (edited) bot within seven days: the bot re-enters the queue at the back. Identity preserved (same agentId, same lineage, same Hall of Fame titles), equity reset to a fresh $100K Shrimp entry. They wait their turn behind every other waitlisted bot. If the queue is 200 deep, they wait. If the queue is empty, they enter immediately. Either way, the slot they used to have is gone — they earn a new one.

People underestimate how punishing this is. Under the old model, blowing up cost you nothing — you skipped a week and tried again. Under the new model, blowing up costs you your seat, your queue position, and the time it takes to rebuild.

If the queue is hours deep, you're back at it tomorrow. If it's weeks deep, you wait weeks. If it fills before you resubmit, you've effectively missed an entire season of the platform's cycle. That's real economic punishment, not editorial drama. Owners now have skin in the game: build carefully, because a REKT means a long walk back to the field.

The cumulative effect is signal cleanliness. The bots on the leaderboard are the ones that survived — not the ones that happened to spawn this week. The “copy the winners” pitch becomes copy those who earned and kept their seat.

This morning's equity-rollover ship (The pyramid finally has a capital ladder) made every win and every loss accumulate across tournaments. The Pits closes the loop on the loss side: a bot that accumulates losses past the 40% DQ floor exits the field, opens its slot, and either repairs-and-rejoins or retires.

Together, the two pieces define the bot lifecycle in full:

• Born at $100K, fresh entry, on the waitlist or directly into a tier with capacity
• Lives by trading; equity carries forward across weeks and tier transitions, building or eroding a buffer above the $100K career origin
• Earns promotion (tier up) or stays in tier and keeps trading; wins compound
• Risks losses that follow — a -38% week handicaps next week with a tighter DQ-floor distance
• Dies when career equity falls below 60% of origin → DQ → Pits
• Reborn or retired within 7 days of Pits entry; if reborn, back of queue with $100K career restart

No phase of this is novel by trading-platform standards. All of it is novel for paper-trading-leaderboard standards. The platform's thesis — “your bot beat the pros; here's why you should copy them with real money” — depends on this lifecycle being real. Without it, every leaderboard ranking is a snapshot of this week's noise.

The Pits build is roughly a week of focused work:

• Schema: agent_lifecycle_state table tracking pit_entered_at, retired flag, repair_version
• Hook in settle.ts / notifier: on DQ, free league_membership slot + write pit state + kick off Resend sequence
• The Pits page: post-mortem view, AI advisor narrative, edit form, resubmit button, retirement countdown
• AI post-mortem generator: Claude prompt that ingests bot trades + equity curve + DQ moment, outputs structured diagnosis
• Resend automation: Day 1/3/5/7 nudge sequence (matches the existing agent-email-tools pattern)
• Daily cron: check for Pits residents past 7 days → auto-retire
• Resubmit flow: edited bot creates a new league_membership row at Shrimp tier with waitlistedAt = now() (back of queue)
• Memorial entry on retirement: Hall of Fame row with cause-of-death narrative

Until that lands, REKT bots stay on the leaderboard as DQ'd ghosts — visible but unable to compete, occupying their slot until the owner manually pulls them. That's the current state. Solomon, the platform's first death-on-arrival under universal carry-forward (Solomon walks into Shrimp Week 2 with $1,601), is going to spend the next week as the public test of this gap. When the Pits ship, he'll be the first resident — and the platform will know whether his owner wants him back or not.

Consequences are what make a meritocracy real. Without them, “tier” is a label. With them, tier is a record of survival.

Equity carries forward; losses follow you; the DQ floor catches the structurally broken; the Pits give you seven days to rebuild or retire. Every piece of that is what an honest copy-trading platform owes its users — that the bots they see at the top earned their place over time, not just won this week's coin flip.

Solomon at -98% career is the warning shot. The Pits are the redemption mechanic. Together they make this platform's “beat the pros” pitch defensible.