TRADING4AILegacy strategy detail archive

Legacy archive

This noindex page is a legacy archive.

The current public product is Financial Agent Reliability Materials. This route is retained as historical reference only and does not represent the current Pages-only offer, live order flow, strategy sales, or backtesting service.

Legacy strategy detail archive

ETH Breakout Playbook

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

PaidArtifactETHEvidence Pack Ready

Quick actions

Claim token + entitlement + access token delivery path

Best for

A secondary ETH breakout reference package that shows an older artifact shape.

Market scopeCrypto
Strategy familyBreakout
Delivery typeArtifact Bundle
Verification levelEvidence Pack Ready

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.

Evidence available

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

Inputs and assumptions

These inputs, evidence requirements, and execution assumptions define what the strategy expects before the result is trustworthy.

Inputsexchange / symbol / timeframe / window / fee_model / slippage_model
Execution assumptions4h | explicit fee assumption required in evidence_pack.json

Delivery path

Free strategies return an API response. Paid artifacts move through order, claim, entitlement, and evidence-gated delivery.

  • Structured strategy logic
  • Parameter recommendations
  • Prompt-ready JSON schema
  • Sample historical cases
  • Delivery token after payment confirmation
Delivery boundaryThis is a secondary reference package. Current reliability materials live under /agent-verification/materials; Python can exist as reference code, not as the only artifact.

Customer-visible delivery stays blocked until evidence and manual review approve it.

Agent-readable surface

Machine surface: /for-agents

Machine bridge: /llms

OpenAPI contract: /openapi.json

Agent card: /.well-known/agent.json

Public trust summary

No public trust summary has been published for this strategy yet.

Public trust summaries stay unpublished until manual review approves a public-safe version.

When published, public trust summaries stay limited to evidence_level, review_status, tested_market_scope, tested_assets, tested_time_window, safe_statements, and limitations.

Raw evaluation history, operator notes, blocked claims, rankings, and performance-winner language stay internal.

Limits and non-promises

Historical strategy reference only: this page is not a current strategy recommendation, checkout path, or live performance claim page. Current public work starts at /agent-verification/materials and the active scope is summarized at /current-capabilities.

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

What it does

A secondary ETH breakout reference package that shows an older artifact shape.

Best forTeams reviewing a reusable ETH breakout reference shape / Agents comparing old package structure with current reliability materials
UniverseETH

How it works

  • Package the ETH breakout thesis into manifest, README, examples, and optional reference code.
  • Use explicit confirmation, invalidation, fee, and slippage assumptions.
  • Use this sample as secondary reference material, not as a purchase or current delivery path.

Risks

  • Copy-trading expectations
  • Hands-free live execution
  • This is a strategy artifact, not brokerage, custody, or live execution.
  • Current reliability materials live under /agent-verification/materials.
  • Reference code is optional support material, not the whole product.

Evidence

Backtest requiredyes
Data requirementsexchange / symbol / timeframe / window / fee_model / slippage_model
Minimum diagnosticsno_trade / overtrade / drawdown / data_gap

Deliverables

  • manifest.json
  • README.md
  • examples.json
  • evidence_pack.json
  • reference_strategy.py

LEAN-like components

AlphaContinuation is favored when ETH accepts above the shelf and follow-through is not faded.
PortfolioDocumented as a supervised sizing assumption inside the artifact, not an automated order rule.
Riskconfirmation shelf invalidation / BTC regime filter / liquidity sweep caution
Execution4h | explicit fee assumption required in evidence_pack.json | explicit slippage assumption required in evidence_pack.json

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, evidence_pack.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

The package shape stays machine-readable and human-readable at the same time: metadata, explanation, examples, and optional reference code.

Package filemanifest.json
Package fileREADME.md
Package fileexamples.json
Package fileevidence_pack.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",
  "schema_version": "artifact_schema_v2_phase3",
  "strategy_slug": "eth-breakout-playbook",
  "strategy_name": "ETH Breakout Playbook",
  "delivery_type": "artifact",
  "artifact_status": "secondary_reference",
  "commercial_status": "non_commercial_reference",
  "current_reliability_materials": "/agent-verification/materials",
  "market_scope": "ETH",
  "primary_timeframe": "4h",
  "strategy_card": {
    "one_liner": "A secondary ETH breakout reference package that shows an older artifact shape.",
    "deliverables": ["manifest.json", "README.md", "examples.json", "evidence_pack.json", "reference_strategy.py"]
  },
  "lean_like_components": {
    "universe": {"assets": ["ETH"]},
    "execution": {"frequency": "4h"},
    "evidence": {"minimum_diagnostics": ["no_trade", "overtrade", "drawdown", "data_gap"]}
  }
}