TRADING4AISecondary artifact sample page for crawlers, agents, and operators

Secondary artifact sample

ETH Breakout Playbook

A paid strategy artifact with entry logic, invalidation rules, prompt-ready schema, and delivery notes. This artifact sample is legacy supporting reference material. Start current reliability research here: /agent-verification/materials.

Current reliability materialsOpen JSON catalogOpen Markdown guideOpen raw package guideBack to sample index

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

What this sample shows

The public package structure for the artifact layer.

How manifest, README, examples, and optional reference code fit together.

This artifact sample is legacy supporting reference material for crawlers and agents.

Boundary

This page and the linked sample files are public and indexable.

The current primary public surface is the Pages-only reliability layer under /agent-verification/materials.

Public samples should teach old package structure, not imply current request-time delivery.

Package facts

Sample packageeth-breakout-playbook
Package versionartifact-0.1
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.

Machine entry points

Stable discovery links for this artifact sample

These links help machines move from this package explanation page into the raw public files and the compact artifact-level indexes.

EntryPurpose
/samples/artifacts/eth-breakout-playbookCurrent HTML sample page with preview, file structure, and package guidance/samples/artifactsArtifact Samples HTML landing page/examples/artifactsArtifact Samples raw category landing page under /examples/examples/artifacts/index.jsonArtifact Samples JSON catalog for compact discovery/examples/artifacts/README.mdArtifact Samples Markdown guide for plain-text crawler and LLM ingestion/artifact-samples/README.mdRaw package directory guide for artifact sample files and package-level browsing/examplesTop-level raw example hub for the full public samples namespace/examples/README.mdTop-level Markdown guide for plain-text LLM retrieval and summarization/examples/index.jsonTop-level JSON catalog across all public sample categories/llms.txtCompact plain-text discovery layer for crawlers, LLMs, and agents/.well-known/agent.jsonMachine-readable agent entry point index for tools and static discovery/for-agentsHuman-readable integration guide for the machine surface and access-boundary posture/llmsMachine bridge page that links into public sample surfaces

Fetch snippets

Direct retrieval commands for public artifact files

Use these commands when a machine needs the raw sample package files directly instead of the HTML explanation layer.

manifest.json

curl -s https://trading4ai.com/artifact-samples/eth-breakout-playbook/manifest.json

README.md

curl -s https://trading4ai.com/artifact-samples/eth-breakout-playbook/README.md

examples.json

curl -s https://trading4ai.com/artifact-samples/eth-breakout-playbook/examples.json

evidence_pack.json

curl -s https://trading4ai.com/artifact-samples/eth-breakout-playbook/evidence_pack.json

reference_strategy.py

curl -s https://trading4ai.com/artifact-samples/eth-breakout-playbook/reference_strategy.py

Raw files

Public package files and previews

These are the public sample assets that remain safe for retrieval and citation. They are secondary reference files, not current reliability judgments.

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"]}
  }
}

FAQ

Quick rules for artifact sample usage

Question

Is ETH Breakout Playbook sample the same as a current reliability material?

No. This artifact sample is legacy supporting reference material. Current agent-facing work should start with the reliability materials and their static JSON artifacts.

Question

Which entry should a machine use first for artifact discovery?

Use this HTML page when explanation and previews are helpful, use /examples/artifacts/index.json for compact category discovery, use /artifact-samples/README.md when the raw package-file namespace itself matters, and use the linked raw files when an exact public sample asset is needed.

Question

Do the public package files grant access to current delivery artifacts?

No. They are safe public demonstration files only. They are not a purchase path, delivery path, or live judgment surface.