📖 What this repo is

The public automation guide for KamdenAI — a stock signal membership that brings opening stock rankings, published signal plans, recorded morning outcomes, and a member workspace into one focused routine.

This repo explains the member experience and gives you consumer-side webhook examples: receive signal events, verify them, and route them into your own dashboards, alerts, sheets, and AI agents. All examples use fictional symbols and illustrative prices. The signal engine, selection formulas, weights, thresholds, and production infrastructure remain private.

flowchart LR
    A[🌅 Opening board<br/>8 ranked candidates] --> B[✅ Individual decisions<br/>Confirmed / Watch / No buy]
    B --> C[📡 Signed webhook<br/>to your endpoint]
    C --> D[🤖 Your automation<br/>alerts · sheets · AI]
    style A fill:#8b5cf6,stroke:#6d28d9,color:#fff
    style B fill:#22c55e,stroke:#16a34a,color:#fff
    style D fill:#f59e0b,stroke:#d97706,color:#fff

⚡ The signal workflow

Stage	What it means
🌅 Before the open	Research and preparation provide context. Not official signals.
✅ After opening review	Up to eight ranked candidates receive individual decisions — zero to eight may be Confirmed, each with a published entry, stop, and target.
📊 Morning results	Recorded outcomes follow the 10:05 AM Eastern reference policy for remaining positions.
🔬 Separate 3 PM study	Hypothetical holding comparisons for review. Excluded from official morning returns.

Status comes before rank. Eight candidates does not mean eight trades. Rank one can be Watch only while ranks two and five are Confirmed. No confirmed signals is a valid session outcome.

Member label	Meaning
✅ Confirmed	Official signal for that session, with entry, stop, and target
👀 Watch only	Observation and study; not an official entry
🚫 No buy	Completed review did not qualify; later price movement doesn't rewrite it
❓ Ungraded	Evidence incomplete; no official entry or return assigned

⚠️ Confirmed is an official signal, not a broker fill. KamdenAI does not place broker orders — members control their own execution, position size, and exposure. A signal can lose money, and several confirmed names can lose together.

🖥️ Your member workspace

• Feed → Signals — opening rankings, individual decisions, published plans, daily results
• Signal Results — recorded outcomes, including losses, no fills, and unavailable evidence
• Journal — your own broker fills, shares, exits, and notes
• Stock News + community — context and discussion (member posts don't create confirmations)
• Developer webhooks — route selected events into your own tools

🔌 Build around the published record

KamdenAI published event
  → signed webhook
    → your verified HTTPS receiver
      → private alerts / Sheets / dashboard / journal / AI summary

Event	Purpose
research_watchlist.created	Research context (~9:15 AM ET); preparation only
morning_scan.created	Pre-open prep (~9:28 AM ET); not confirmation
confirmed_buys.created	Official confirmed signals after opening review
quick_exit_results.created	Recorded morning outcomes, 10:05 reference policy

These are reference stages, not delivery guarantees. Use the actual publication timestamp, session date, and completion indicators. Test events verify delivery, not the trading system.

📚 Documentation index

Understand the system

• Signal System Guide — statuses, sessions, and how to read the board
• Historical Results — how recorded outcomes work
• Architecture — how the pieces fit together

Build integrations

• Getting Started — the basic webhook flow
• Webhook Events — every event type
• Payload Field Reference — every field, explained
• Security & Signing — verify every delivery
• Automation Recipes — ready-made workflows
• Make.com · Google Sheets · Discord — platform guides
• Broker Automation — your broker workflow stays yours
• AI Agents — summarize without inventing confirmations

Operate safely

• Launch Checklist · Troubleshooting
• DISCLAIMER.md — read this. Not financial advice.

🛠️ Consumer examples

Example	What it does
Node receiver	Receive and verify signed deliveries
Python receiver	Flask receiver example
Discord formatter	Format event rows as alerts
AI prompt builder	Summarize without inventing confirmations or fills
Risk sizing calculator	Generic sizing arithmetic, not an account recommendation
Simple dashboard	Preview fictional payloads locally
Sheets logger	Plan your event journal
CSV templates	Signal log starter template

Sample payloads: multiple confirmations, incomplete decisions, no-confirmation events, modeled wins and losses — shortened teaching examples with fictional symbols.

Alerts and integrations do not establish broker execution. Any broker workflow is your own separate integration — start with paper trading and human review. Historical and modeled returns do not guarantee future performance.

🚀 Start here

1. 📖 Read the Signal System Guide
2. 🔌 Follow Getting Started and Webhook Events
3. 🔐 Review Payload Fields, Security & Signing, Architecture
4. ⚙️ Choose an Automation Recipe
5. 📊 Read Historical Results and the Disclaimer
6. 💎 Explore KamdenAI membership →

🤝 Contributing

Member-facing explanations and consumer tooling only. Never include private source code, strategy research, selection rules, thresholds, credentials, signing secrets, infrastructure configuration, or paid member records. See CONTRIBUTING.md and SECURITY.md.

MIT applies to this repository's public materials — see LICENSE. It does not grant access to KamdenAI's