# Kite / Auto Trade — Product Documentation (Draft)

_Last updated: 2026-03-31 (UTC)_

## Scope
This document is based on:
- the currently accessible Kite group session history in OpenClaw, and
- host-level deployment/config checks on this server.

## Executive summary
Kite / Auto Trade appears to be an automated trading product (likely in the Kite/Zerodha ecosystem) with a deployed web frontend at:
- **https://autotrade.winds-os.com**

## Verified hosting & deployment findings
1. Active assistant workspace (`/home/usr1/clawd`) does **not** contain the Kite/AutoTrade application repo.
2. Nginx config on this host shows:
   - `autotrade.winds-os.com` is configured.
   - Document root points to: `/home/usr1/code2/Autotrade/frontend/dist`
3. A historical cache path exists:
   - `/home/usr1/.cache/claude-cli-nodejs/-home-usr1-code2-Kitetrade`
   - This suggests an earlier project path named `/home/usr1/code2/Kitetrade` likely existed.
4. Current path `/home/usr1/code2/Kitetrade` is not present now.

## What the product appears to do (current confidence: medium-low)
From available context/naming:
- likely automates market trading actions,
- likely offers a web UI (frontend deployed via `autotrade.winds-os.com`),
- likely intended for strategy execution around Kite-linked trading flows.

> This is still partially inferred due missing repository and limited chat history visibility.

## Group history coverage note
Despite requesting complete Kite group history, only the currently retained OpenClaw session transcript for this group is accessible here. That transcript alone is insufficient to derive full product behavior/specification details.

## Documentation gaps to close
To produce a full product document, provide one of:
- full Telegram group export for Kite,
- current repository path(s) and access,
- architecture docs/README for AutoTrade.

## Recommended final documentation structure (once data is provided)
- Product vision and target users
- End-to-end trading lifecycle (signal -> pre-trade checks -> order -> monitoring -> exit)
- Broker/Kite integration details (auth/session/token refresh/order APIs)
- Strategy engine and configuration model
- Risk controls (position sizing, stop-loss, max daily drawdown, kill-switch)
- Operational monitoring/alerts and incident response
- Security, secrets management, and compliance considerations
- Deployment topology and runbook

---

This is a factual draft based on currently accessible evidence and should be upgraded once full history/repo access is available.