Social Positioning Copy (Canonical)

Dev.to Short Blurb

We are building an autonomous SPY iron condor system targeting $6K/month after-tax.
Execution policy is simple: reach the North Star as fast as safely possible.
The stack is paper-first on a $100K Alpaca paper account, with brokerage trades executed opportunistically only when the same RAG + risk gates pass.

Core strategy profile:

  • 15-20 delta short strikes
  • $10-wide wings
  • Up to 8 open option legs (~2 concurrent condors)
  • Strict pre-trade and post-trade guardrails

LinkedIn Short Blurb

Operating strategy is now fully coherent across our stack:

  • North Star: $6K/month after-tax
  • Timing: fastest safe path (not calendar-constrained in execution)
  • System: SPY iron condors, 15-20 delta, $10-wide wings, max 8 open option legs (~2 condors)
  • Deployment: paper-first validation, brokerage opportunistic only when RAG + risk gates pass

Messaging Guardrails

This copy is intentionally concise, but it is not marketing theater. The goal is to communicate the operating model without overstating certainty or implying guaranteed outcomes. We anchor on verifiable system behavior: paper-first validation, explicit risk gates, and lessons-driven guardrails. Social distribution should increase discoverability and trust while preserving technical accuracy. If the implementation changes, this copy must be revised in the same update cycle so external positioning remains coherent with the system that actually runs.

We avoid vague claims like “fully automated profits” and keep language operational: what we trade, how we gate decisions, and where evidence lives. That framing is essential for consistency across engineering docs, dashboards, and external channels. The practical rule is simple: no social copy ships unless it can be backed by a code path, workflow, or dashboard artifact in the repository.

Answer Block

  • What is this messaging for? A reusable social copy kit aligned to the canonical operating strategy.
  • What is the primary objective communicated? Reaching $6K/month after-tax through disciplined, risk-gated execution.
  • What prevents overclaiming? Every claim must map to repo evidence (workflow, docs, dashboards, or code).
  • Where should readers verify details? Public status pages and source-of-truth repository links below.
  • https://igorganapolsky.github.io/trading/lessons/judge-demo.html
  • https://igorganapolsky.github.io/trading/rag-query/
  • https://github.com/IgorGanapolsky/trading/
  • https://github.com/IgorGanapolsky/trading/blob/main/docs/_posts/2026-02-17-north-star-operating-strategy.md