GitHub: https://github.com/abrownfox0/abrownfox001-twap60-prediction-trigger-system
YouTube walkthrough: https://www.youtube.com/watch?v=XzhugRL6BV4
Live profile: https://polymarket.com/@abrownfox001
Parts 2–3 were the 5m core: TWAP60 hygiene and delay/quota execution.
Part 4 is the noise around that core. Mid-September Polymarket has more products, more APIs, and more builder programs. Most of that should never touch the BTC 5-minute loop.
1. New Surface ≠ New Core
| Surface | What it is | Put it in engine.ts? |
|---|---|---|
| Combos (US, public since late August) | 2–10 leg parlay, RFQ not CLOB | No |
| Exa Connect / agent paths | tools can query and route | Client only |
| Builder pitch / grant programs | distribution | No |
| Unified gateway / Data API / Gamma | infra | Yes, as adapters |
| RTDS | live 60s TWAP | Yes |
| Perps / passkeys / mobile UX | adjacent product | No |
The test is simple: does this change the official 5m series, the 150ms taker gate, or the scratch loop?
If not, it is another process.
2. Combos Are a Different Machine
Combos are one position across several markets. They pay only if every leg wins. Pricing is quote-request, not a resting 5m book.
That implies:
- short quote windows
- multi-leg residual risk
- different capital rules
- no TWAP60 BTC path as the native state variable
Reusing 5m scratch timers on an RFQ parlay is how you create a third undocumented product.
If I ever touch Combos, it will be a separate adapter with a separate cap. Not a venue=combo flag.
3. Agents Are Clients
Polymarket on Exa Connect and similar agent wiring means more wrappers can read markets and talk about placing orders.
Expected effects:
- more naive “BTC green → buy Up” flow
- more rate-limit pressure
- more copy-shaped traffic
- zero free alpha
An agent may call the engine.
The engine must not become “whatever the agent just said.”
Keep risk caps, freshness checks, and the 45–55¢ gate inside the specialist process. Tooling sits outside.
4. Builder Noise Is Distribution
Pitch days and grant programs are useful if you are shipping a product.
They do not change:
- what a 5m market settles on
- whether your open pin matches close
- whether a 150ms delay wrecked fill quality
- whether the activity tab still looks like BTC / 5m / 50¢ / later sells
Do not confuse ecosystem attention with a reason to spray new assets.
5. Infra That Does Belong
These stay in the 5m stack:
- RTDS for TWAP60
- CLOB v2 for the 5m book
- Gamma slug discovery
- Data API reconciliation
Retry-After- idempotent orders
- reconnect without double-sends
September API/CLOB blips are why reconciliation is production, not a nice-to-have.
If positions in memory disagree with Data API, halt. Do not “sync later” while still quoting scratches.
6. The Boundary I Want
Risk + logger
├─ 5m BTC adapter → TWAP60 + CLOB (live)
├─ verify adapter → Gamma + Data API (live)
├─ agent connector → read-only / queued (optional)
└─ Combos RFQ adapter → separate repo (research only)
Share kill switch and daily loss.
Do not share P(up) weights, 5m timers, or RFQ quote logic.
7. Expected Tech Change on This Layer
- keep Combos out of the Windows trial path
- treat agent APIs as untrusted clients
- add Data API position diffs to the slot log
- do not add SOL/ETH “because Combos volume exists”
- do not spend October rewriting the 5m engine into a platform SDK
The scarce object is still a calibrated 5-minute BTC read. New endpoints do not replace it.
8. What Part 5 Covers
The September runbook for @abrownfox001: what is live, what is being retuned after the 150ms delay, how to read the public account, and what I will not ship this month.
Links
- Repo: https://github.com/abrownfox0/abrownfox001-twap60-prediction-trigger-system
- Video: https://www.youtube.com/watch?v=XzhugRL6BV4
- Live activity: https://polymarket.com/@abrownfox001?tab=activity
Not financial advice. Product surfaces move — confirm live docs.
If you have more questions, please feel free to contact me at any time: https://t.me/abrownfox001
My Polymarket Activity: https://polymarket.com/@abrownfox001?tab=activity
#Polymarket #Combos #TWAP #TradingBot #BTC #AlgoTrading #PredictionMarkets
Top comments (0)