# TRADING4AI Public Artifact Samples

This directory contains public artifact package samples for TRADING4AI.

These packages are safe, indexable examples that explain expected artifact structure. They are not private paid delivery bundles and do not grant entitlement to customer-specific files.

## Sample Packages

### ETH Breakout Playbook

- HTML page: `/samples/artifacts/eth-breakout-playbook`
- Manifest: `/artifact-samples/eth-breakout-playbook/manifest.json`
- README: `/artifact-samples/eth-breakout-playbook/README.md`
- Examples: `/artifact-samples/eth-breakout-playbook/examples.json`
- Reference strategy: `/artifact-samples/eth-breakout-playbook/reference_strategy.py`

### BTC Trap Playbook

- HTML page: `/samples/artifacts/btc-trap-playbook`
- Manifest: `/artifact-samples/btc-trap-playbook/manifest.json`
- README: `/artifact-samples/btc-trap-playbook/README.md`
- Examples: `/artifact-samples/btc-trap-playbook/examples.json`
- Reference strategy: `/artifact-samples/btc-trap-playbook/reference_strategy.py`

## Recommended Reading Path

1. Start with `/samples`.
2. Read `/examples` when you want the top-level raw example hub and shared machine entry points.
3. Read `/samples/artifacts`.
4. Read `/examples/artifacts` when you want the raw artifact landing page.
5. Inspect one artifact sample HTML page.
6. Fetch `/examples/artifacts/index.json` when you need the category-level machine-readable artifact catalog.
7. Fetch `/examples/README.md` when you want the top-level plain-text public examples guide.
8. Fetch the raw package files only when exact sample content is needed.
9. Read `/samples/delivery/quant-lab-standard` to understand how public package structure differs from private delivery.

## Core Machine Links

- `/llms`
- `/llms.txt`
- `/.well-known/agent.json`
- `/for-agents`
- `/samples`
- `/examples`
- `/examples/README.md`
- `/examples/index.json`
- `/examples/artifacts`
- `/examples/artifacts/index.json`
- `/examples/artifacts/README.md`
- `/openapi.json`

## Which Entry Should You Start With?

- Crawler or search engine: start with `/samples/artifacts` because it provides crawlable HTML, internal links, and structured data.
- LLM or agent needing compact discovery: start with `/examples/artifacts/index.json` because it gives the category-level machine catalog without parsing HTML.
- LLM needing plain text context: start with `/examples/artifacts/README.md` because it is the category-level Markdown guide for artifact discovery.
- Reader needing the raw package directory guide: start with `/artifact-samples/README.md` because it focuses on the underlying package-file namespace rather than the wider machine surface.
- Agent runtime or tool caller: start with `/.well-known/agent.json`, then use `/for-agents` and `/openapi.json` before deciding whether category HTML, category JSON, or raw package files are needed.

## Guide Roles

- `/examples/artifacts/README.md` is the category-level plain-text discovery guide for artifact samples.
- `/artifact-samples/README.md` is the raw package directory guide for the underlying artifact file namespace.
- Use the category guide first when you need navigation across the wider artifact sample surface, and stay with the raw package guide when package-level file browsing is the main task.

## File Roles

- `manifest.json`: package-level metadata and delivery shape.
- `README.md`: human-readable package overview.
- `examples.json`: public input/output examples.
- `reference_strategy.py`: illustrative reference implementation, not a production execution engine.

## Boundary

Public artifact samples teach file structure and package semantics. Real paid delivery remains behind Worker authorization, claim tokens, entitlement state, and access tokens.

Do not treat these public sample files as proof of purchase, private bundle access, or executable trading guarantees.