# TRADING4AI Artifact Public Examples

This directory is the artifact-specific plain-text guide inside the `/examples` namespace.

Use it when a crawler, LLM, agent, or integration operator needs a compact Markdown overview of the public artifact sample layer without parsing the full website UI.

These files are examples only. They describe artifact package structure and public sample contents, but they do not grant access to private paid bundles or customer-specific delivery files.

## Primary Entry Points

- Category HTML landing: https://trading4ai.com/samples/artifacts
- Category raw landing: https://trading4ai.com/examples/artifacts
- Category JSON catalog: https://trading4ai.com/examples/artifacts/index.json
- Category Markdown guide: https://trading4ai.com/examples/artifacts/README.md
- Artifact raw package guide: https://trading4ai.com/artifact-samples/README.md
- Top-level JSON catalog: https://trading4ai.com/examples/index.json
- Top-level Markdown guide: https://trading4ai.com/examples/README.md
- Machine bridge: https://trading4ai.com/llms

## Files

- `/samples`
- `/examples`
- `/examples/README.md`
- `/samples/artifacts`
- `/examples/artifacts`
- `/examples/artifacts/index.json`
- `/examples/artifacts/README.md`
- `/examples/index.json`
- `/llms.txt`
- `/artifact-samples/README.md`
- `/artifact-samples/eth-breakout-playbook/manifest.json`
- `/artifact-samples/eth-breakout-playbook/README.md`
- `/artifact-samples/eth-breakout-playbook/examples.json`
- `/artifact-samples/eth-breakout-playbook/reference_strategy.py`
- `/artifact-samples/btc-trap-playbook/manifest.json`
- `/artifact-samples/btc-trap-playbook/README.md`
- `/artifact-samples/btc-trap-playbook/examples.json`
- `/artifact-samples/btc-trap-playbook/reference_strategy.py`
- `/llms`
- `/.well-known/agent.json`
- `/for-agents`
- `/openapi.json`

## Recommended Flow

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

## 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 compact Markdown guide for this category.
- Reader needing the raw artifact package directory: start with `/artifact-samples/README.md` because it focuses on the package-file namespace itself rather than the wider category discovery layer.
- Agent runtime or tool caller: start with `/.well-known/agent.json`, then use `/for-agents` and `/openapi.json` before deciding whether category HTML or raw 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 artifact sample surface, and use the raw package guide when you already know you need package-level file browsing.

## File Roles

- `manifest.json`: package-level metadata and delivery shape.
- `README.md`: human-readable package overview for the public sample package.
- `examples.json`: public example inputs and outputs.
- `reference_strategy.py`: illustrative reference implementation, not a production execution engine.

## Boundary

Artifact public examples teach structure, file roles, and package semantics. Real paid delivery remains behind Worker authorization, claim tokens, entitlement state, and access tokens.

Use `/llms` for bridge-page orientation, `/llms.txt` for compact plain-text discovery, `/.well-known/agent.json` for agent entry-point discovery, `/for-agents` for integration guidance, `/examples/artifacts/index.json` for compact category discovery, and `/openapi.json` as the canonical runtime contract.