TRADING4AIStrategy detail and delivery shape

Strategy detail

ETH Breakout Playbook

The paid layer is not just a signal. It is the whole strategy object an agent can reason over.

paidartifactETHArtifact

Quick actions

Artifact delivery after claim token

Use this when

  • Acquire a reusable ETH breakout playbook with structured risk framing.
  • Seed downstream agents with a higher-fidelity strategy asset.
  • Pair with internal research workflows.

Do not use this for

  • Copy-trading expectations.
  • Hands-free automated execution without supervision.
  • Users looking only for raw market data.

Evidence and positioning

  • The asset is intended to ship with logic summary, parameter suggestions, example cases, and delivery metadata.

Artifact delivery

  • Structured strategy logic
  • Parameter recommendations
  • Prompt-ready JSON schema
  • Sample historical cases
  • Delivery token after payment confirmation
Package versionartifact-0.1

The first paid delivery should be a strategy asset package. Python can exist as reference code, not as the only deliverable.

Asset thesis

What the buyer actually receives

ETH breakout quality improves when the 2,385-2,400 shelf becomes support on closing strength, rather than only an intraday wick reclaim.

Primary formatsjson / markdown
Suggested filesmanifest.json, README.md, examples.json, reference_strategy.py (optional)

Decision framework

  • Prefer continuation only when the 4h close reclaims the confirmation shelf and follow-through is not immediately faded.
  • Treat liquidity sweeps back through the shelf as a caution flag rather than a clean continuation trigger.
  • Let regime context and BTC structure act as a filter before sizing an ETH-specific breakout thesis.

Operating modes

confirmed_breakout

Participate in continuation when ETH is accepted above the shelf.

Lose the confirmation shelf on closing basis or print a failed reclaim.

decision_zone

Stay patient while ETH is still negotiating the shelf.

Do not force trend conclusions until acceptance or rejection becomes clear.

failed_breakout_risk

Reduce risk and prepare for rejection scenarios.

Only re-upgrade if ETH reclaims the shelf with fresh closing strength.

Parameter suggestions

primary_timeframe4h
confirmation_zone2385 / 2400
upside_projection_zone2550 / 2650
supporting_filterBTC regime must not be risk_off

Machine payload

Preferred inputs

price, close_4h, liquidity_sweep

Recommended follow-up

Call /api/v1/strategies/eth-breakout-vs-reversal/invoke for deterministic classification. Use the AI advice endpoint only for orchestration or explanation, not final execution logic.

Sample package

What the V1 artifact package can look like

This is the delivery shape we should standardize around in V1: machine-readable metadata, human-readable explanation, structured examples, and optional Python reference code.

Package filemanifest.json
Package fileREADME.md
Package fileexamples.json
Package filereference_strategy.py
Package nameeth-breakout-playbook
manifest.json/artifact-samples/eth-breakout-playbook/manifest.json
Open file
{
  "package_name": "eth-breakout-playbook",
  "package_version": "artifact-0.1",
  "strategy_slug": "eth-breakout-playbook",
  "strategy_name": "ETH Breakout Playbook",
  "delivery_type": "artifact",
  "pricing_tier": "paid",
  "market_scope": "ETH",
  "primary_timeframe": "4h"
}