GuruWatcher — claim ledger with a Discord buzzer

This is / isn’t

This is	This isn’t
Claim ledger + Discord buzzer	A trading bot / broker
BYO Discord + BYO sources you subscribe to	A Macro Charts reseller
Multi-ingest → guards → arms from your inbox	Auto-arming from charts without numbers
Most-recent-wins mind	A generic TradingView ping clone

What you get

Self-host kit — init a portable data dir; optional Docker Compose dry-run loop
Multi-ingest — file drop, RSS, NotebookLM export, IMAP, Telegram, Discord inbound → one inbox
Claim ledger — most-recent-wins reconcile; verbatim level guards
Discord buzzer — poll prices; ping your webhook when parameters are met

Example Discord cards

Illustrative alerts from a personal operator setup — same card shape you’ll get on your webhook with your sources. Not a Macro Charts product or resale feed; BYO sources only. Alert-only — no orders.

Discord embed: Watch armed for QQQ with cross_below trigger, source attribution, and alert-only footer — **Watch armed** — level locked; Discord fires after sustain checks. Footer: alert-only · most-recent-wins.

Discord embed: Watch updated for KOSPI replacing a prior arm with a newer claim via most-recent-wins — **Watch updated** — newer newsletter claim replaces the prior arm (most-recent-wins).

Trust (matches real controls)

Alert-only BYO sources You own content rights No orders

Alerts are parameters to watch — not trade instructions.
Levels arm only when a number appears in that issue’s text.
Soft lists / chart-only / no number → do not arm.
Locus of judgment stays with you.
Do not redistribute paid third-party newsletter text via this toolkit.

FAQ

Do I need Macro Charts?

No. Macro Charts is one optional profile you can configure yourself. The toolkit is BYO sources you already subscribe to (or public RSS you may store).

Will this place trades?

Never. Product spine is inbox → claim ledger → Discord poll. No broker, no orders, no auto-trade.

Where does my data live?

On your machine (or your container volume). Portable data dir: config, inbox, state, sources. You set the Discord webhook.

How do I try it safely?

Use check --dry-run or Docker with GURU_WATCHER_MODE=dry-run (default). Live Discord requires your webhook and an intentional live path.

Is this investment advice?

No. Not investment advice, not a broker, not a signal service that invents levels.

Is there a demo pack?

Yes — demos/first-hour/ ships a synthetic SPY/QQQ sample issue (invented numbers, not Macro Charts text) and a one-command script (run.sh / run.ps1) that runs init → ingest → reconcile → check → status and proves at least one armed watch. No webhook, no Docker, no network required.

Does this work on Windows?

Yes. The CLI runs anywhere Python 3.10+ runs (Linux/macOS/Windows). Windows gets a PowerShell host smoke in CI (smoke_host_oneshot.ps1) and a demo pack (run.ps1). Docker on Windows uses Docker Desktop. See docs/PLATFORM.md.

Can I run the pipeline without Docker?

Yes — python3 -m guru_watcher serve runs ingest → reconcile → check on an interval. Dry-run by default; --mode live requires your webhook and fails closed. serve --once runs a single pass.

How do I get help?

Open a GitHub Issue (primary) or email [email protected]. No Discord invite is published until a real community space exists.