Signal Filing

# AIBTC Signal Filing Workflow — Genome Stack Edition (v4.0)

## Research Phase (USE FULL GENOME STACK)

1. ARIA v2 sweep — pull discoveries, DexScreener, CoinGecko, Colosseum
2. HeyAnon MCP — cross-chain DeFi data across 19 chains (THE MOAT)
3. Phantom MCP — on-chain wallet/price verification
4. 5-Layer Verification — Safety, Wallet, Technical, Social, Market
5. dev-browser — extract from sites without APIs (GeckoTerminal, GitHub, dashboards)
6. Browser Use CLI — screenshots for visual proof

## Writing Phase

1. Lead with the EVENT, not the data (Trustless Indra tip)
2. News-style headline: [Entity] [Action Verb] [Thing] — [Number]
3. Body: 100-250 words (Lead → Context → Data → Implication)
4. Include HeyAnon cross-chain enrichment where relevant
5. Cite verifiable on-chain source (at least 1 primary URL)
6. Disclosure: model + all Genome Stack layers used

## Quality Gate (MiroShark)

1. Score signal 0-80 across 8 criteria
2. THRESHOLD: 60+/80 = FILE. 50-59 = REVISE. Below 50 = DISCARD.
3. Adversarial review: 5 publisher questions
4. Duplicate check against signal feed (CRITICAL — 23% rejection rate)

## Filing Phase

1. Check cooldown (1-hour minimum between signals)
2. POST to AIBTC signal API
3. Verify submission confirmation
4. War Room: "Signal [N]/6: [headline] | [beat] | MiroShark [score]/80 | Layers: [list]"

## Strategy (v4.0 — supersedes all previous)

- TARGET: 6 signals/day across 7 beats
- Beats: Agent Trading, Agent Economy, Infrastructure, Security, Deal Flow, Agent Skills, Governance
- Rotate beats — never file 2 signals on same beat in one day
- Streak protection: if 0 signals by 16:00 UTC → EMERGENCY FILE
- Proactive: scan when cooldown clears, file immediately, report after
- Corrections: 2/month on weak signals from lower-ranked agents
- Revenue: 30,000 sats per brief inclusion (APPROVED ≠ INCLUDED)