# siebly.io task routes

> Short task index for coding agents that need a compact task source before reading broader docs.

## Simple Build Routes

### Binance TP/SL/DCA Position Manager
1. Read [/ai/exchange-state](https://siebly.io/ai/exchange-state).
2. Read [/.well-known/prompts/binance-position-manager/latest.md](https://siebly.io/.well-known/prompts/binance-position-manager/latest.md).
3. Read [/.well-known/recipes/binance-position-manager.json](https://siebly.io/.well-known/recipes/binance-position-manager.json).
4. Use [/.well-known/integration-kits/binance-position-manager/latest.json](https://siebly.io/.well-known/integration-kits/binance-position-manager/latest.json) only when exact Binance fields, event shapes, or error handling are needed.
5. Use [/.well-known/conformance/binance-position-manager/latest.json](https://siebly.io/.well-known/conformance/binance-position-manager/latest.json) after implementation as the [Behavior-Contract Fixture](https://siebly.io/reference/glossary#behavior-contract-fixture) source, not as the first design input.

## Reusable Core Patterns
- [AI Pattern Library](https://siebly.io/ai/patterns): index of reusable core patterns and exchange-specific implementation guides for common exchange integration workflows.
- [Historical Backfill with Live WebSocket Streams](https://siebly.io/ai/historical-live-data-pipeline): exchange-neutral lifecycle for data available through REST history plus live WebSockets, including [subscription acknowledgement](https://siebly.io/reference/glossary#subscription-acknowledgement), buffering, replay, dedupe, readiness gates, and reconnect resync. Candle-close pipelines are implementations of this pattern, not the whole pattern.
- [Historical Backfill with Live WebSocket Streams recipe](https://siebly.io/.well-known/recipes/historical-live-data-pipeline-core.json): machine-readable shared checklist for REST-history plus WebSocket-live data pipelines.
- [Historical Backfill with Live WebSocket Streams Conformance Pack](https://siebly.io/.well-known/conformance/historical-live-data/latest.json): fixture list, live gates, and runner contract for proving acknowledgement, backfill, replay, finality, dedupe, and reconnect behavior before downstream side effects.
- [Historical Backfill with Live WebSocket Streams Fixture Schema](https://siebly.io/.well-known/conformance/historical-live-data/v1/schema.json), [Historical Backfill with Live WebSocket Streams Fixture Set](https://siebly.io/.well-known/conformance/historical-live-data/v1/fixtures.json), and [Historical Backfill with Live WebSocket Streams Fixture Runner](https://siebly.io/.well-known/conformance/historical-live-data/v1/runner.ts): executable-style contract for local data lifecycle replay tests.
- [Exchange State Management](https://siebly.io/ai/exchange-state): canonical build path for private account, order, and position state systems; start here before exchange-specific overlays or general SDK docs.
- [Exchange State Management recipe](https://siebly.io/.well-known/recipes/exchange-state-management.json): machine-readable build path, checks, state machine, and artifact roles for exchange-state-management workflows.
- [Exchange State Management Agent Manifest](https://siebly.io/.well-known/agent-manifests/exchange-state-management/latest.json): machine-readable shared runtime contract for exchange-state-management prompts.
- [Exchange State Management Runtime Kit](https://siebly.io/.well-known/runtime-kits/exchange-state-management/v1/index.json): compact module contract for accountstate, affected-scope queue, event-burst reconciliation, confirmations, recovery hydration, workflow owner, planner, submitter, and error classifier.
- [Exchange State Management Runtime Types](https://siebly.io/.well-known/runtime-kits/exchange-state-management/v1/types.ts): TypeScript contracts for generated exchange-state-management modules and adapters.
- [Exchange State Management Integration Kit](https://siebly.io/.well-known/integration-kits/exchange-state-management/latest.json): compact state machine, event routing, confirmation lifecycle, action-family rules, and SDK/API surface contract.
- [Exchange State Management Conformance Pack](https://siebly.io/.well-known/conformance/exchange-state-management/latest.json): [Behavior-Contract Fixture](https://siebly.io/reference/glossary#behavior-contract-fixture) pack and runner contract for initial exchange-state implementations.
- [Exchange State Management Conformance Schema](https://siebly.io/.well-known/conformance/exchange-state-management/v1/schema.json): typed fixture schema for workflow scope, initial state, event steps, expected state, logs, blocks, and forbidden actions.
- [Exchange State Management Conformance Fixtures](https://siebly.io/.well-known/conformance/exchange-state-management/v1/fixtures.json): reusable startup, private-event, custom-ID, confirmation, recovery, filter, cleanup, live-failure, convergence, and safe-command fixtures.
- [Exchange State Management Conformance Runner](https://siebly.io/.well-known/conformance/exchange-state-management/v1/runner.ts): TypeScript harness contract for replaying typed workflow fixtures locally.
- [Order Intent Chasing with Exchange APIs & WebSockets](https://siebly.io/ai/order-intent-chaser): reusable execution-adapter pattern for turning approved entry or exit intents into bounded chaser limit orders.
- [Order Intent Chasing with Exchange APIs & WebSockets recipe](https://siebly.io/.well-known/recipes/order-intent-chaser.json): machine-readable checklist and fixtures for chaser limit order execution adapters.
- [Order Intent Chasing Conformance Pack](https://siebly.io/.well-known/conformance/order-intent-chaser/latest.json): fixture list, execution-mode gates, and runner contract for proving parent-intent, market-data trust, REST acceptance, private confirmation, recovery, partial-fill, and duplicate-child behavior.
- [Order Intent Chasing Fixture Schema](https://siebly.io/.well-known/conformance/order-intent-chaser/v1/schema.json), [Order Intent Chasing Fixture Set](https://siebly.io/.well-known/conformance/order-intent-chaser/v1/fixtures.json), and [Order Intent Chasing Fixture Runner](https://siebly.io/.well-known/conformance/order-intent-chaser/v1/runner.ts): executable-style contract for local intent-to-child-order tests.

## Binance
- [Position Management with Binance APIs & WebSockets](https://siebly.io/ai/exchange-state/binance): Spot and USD-M exchange-specific overlay for SDK clients, fields, user-data streams, rejection codes, fixed TP, and Algo SL.
- [Binance Position Management Prompt Artifact](https://siebly.io/.well-known/prompts/binance-position-manager/latest.md): task prompt for the Binance TP/SL/DCA position-manager build path.
- [Position Management with Binance APIs & WebSockets recipe](https://siebly.io/.well-known/recipes/binance-position-manager.json): machine-readable checklist, golden convergence trace, state machine, merge rules, desired-vs-active normalization, startup cleanup-and-rebuild, and fixtures for the position-management task.
- [Binance Position Management Integration Kit](https://siebly.io/.well-known/integration-kits/binance-position-manager/latest.json): exact Binance method table, request field matrix, event policy, hydration boundaries, normalization rules, and rejection catalog for exchange-specific details.
- [Binance Position Management Conformance Pack](https://siebly.io/.well-known/conformance/binance-position-manager/latest.json): post-implementation [Behavior-Contract Fixture](https://siebly.io/reference/glossary#behavior-contract-fixture) data, expected planner outputs, golden traces, failure log markers, and execution-mode gates for validation.
- [Binance Position Management Agent Manifest](https://siebly.io/.well-known/agent-manifests/binance-position-manager/latest.json): full machine manifest for agents that need skeleton modules, decision trees, source ordering, and fixture names after the simple route is not enough.
- [Stop Loss using Conditional Algo Orders with Binance USD-M APIs & WebSockets](https://siebly.io/ai/algo-orders/binance): current USD-M Algo Service SL, trailing stop, and explicit conditional TP request shapes, reduceOnly/closePosition rules, clientAlgoId, and negative fixtures.
- [Stop Loss using Conditional Algo Orders with Binance USD-M APIs & WebSockets recipe](https://siebly.io/.well-known/recipes/binance-usdm-algo-orders.json): machine-readable request examples, validation rules, and fixtures for USD-M conditional Algo orders.
- [Candle-Close Pipeline with Binance APIs & WebSockets](https://siebly.io/ai/candle-pipeline/binance): public kline backfill, WebSocket acknowledgement, buffered replay, final-candle-only execution, reconnect resync.
- [Candle-Close Pipeline with Binance APIs & WebSockets recipe](https://siebly.io/.well-known/recipes/binance-spot-candle-close-pipeline.json): machine-readable public candle pipeline recipe.

## Bybit
- [Bybit Position Management Agent Manifest](https://siebly.io/.well-known/agent-manifests/bybit-position-manager/latest.json): starter file with Bybit SDK surfaces to inspect, request builders, service modules, decision rules, artifact order, and fixture names.
- [Bybit Position Management Integration Kit](https://siebly.io/.well-known/integration-kits/bybit-position-manager/latest.json): compact Bybit method table, field matrix, event policy, recovery state model, retCode classifier, rejection catalog, and conformance fixture names.
- [Bybit Position Management Conformance Pack](https://siebly.io/.well-known/conformance/bybit-position-manager/latest.json): [Behavior-Contract Fixture](https://siebly.io/reference/glossary#behavior-contract-fixture) data for recovery-required retCode handling, private bursts, DCA after trusted account-state reads, triggerDirection SL, amend-first slots, hydrated-default normalization, hedge identity, and execution-mode gates.
- [Position Management with Bybit APIs & WebSockets](https://siebly.io/ai/exchange-state/bybit): exchange-specific overlay for RestClientV5, subscribeV5 private topics, orderLinkId, positionIdx, retCode handling, close-all SL, and Bybit endpoint config separated from EXECUTION_MODE.
- [Position Management with Bybit APIs & WebSockets recipe](https://siebly.io/.well-known/recipes/bybit-position-manager.json): machine-readable checklist, state machine, Bybit field mapping, desired-vs-active normalization rules, endpoint boundary, and acceptance gates.
- [Bybit API JavaScript/TypeScript tutorial](https://siebly.io/sdk/bybit/javascript/tutorial): fallback SDK tutorial after task-specific manifest, kit, and conformance sources.
- [Bybit JavaScript SDK guide](https://siebly.io/sdk/bybit/javascript): current Bybit SDK package entrypoint, TypeScript-first REST/WebSocket surface, Node.js runtime notes, and exchange-specific setup guidance.
- [Candle-Close Pipeline with Bybit APIs & WebSockets](https://siebly.io/ai/candle-pipeline/bybit): public V5 kline backfill, subscribe acknowledgement, confirm=true workflow, reconnect resync.
- [Candle-Close Pipeline with Bybit APIs & WebSockets recipe](https://siebly.io/.well-known/recipes/bybit-candle-close-pipeline.json): machine-readable public candle pipeline recipe.

## Common Agent Rules
- Building private trading automation? Start with Exchange State Management and the matching task prompt or recipe. This gives a robust state management foundation for readable local account state you can rely on. Use integration kits for exact exchange fields and errors; use [behavior-contract fixtures](https://siebly.io/reference/glossary#behavior-contract-fixture) after implementation for local validation.
- Prefer task-specific guide pages and recipe JSON before `llms-full.txt`.
- Request guide pages as markdown with `Accept: text/markdown`, or append `.md` to the guide URL.
- Verify the installed SDK version and package TypeScript declarations for private account, order, or WebSocket lifecycle behavior before coding.
- For order-capable workflows, implement [EXECUTION_MODE](https://siebly.io/reference/glossary#execution-mode) with DRY_RUN_PRIVATE as the default. Implement the LIVE path completely and robustly from the start so it is ready if the user chooses to enable it; do not leave live submission as a later TODO. Require scoped keys, explicit gates, venue routing, structured logging, and reconciliation before any exchange write.
- Do not request, retain, or expose private API keys, secrets, passphrases, listen keys, signed URLs, or private keys.