# TRADING4AI Delivery Public Examples

This directory contains public delivery-shape examples for understanding how artifact bundles are described without exposing private paid files.

These files are examples only. They do not grant access to private delivery sessions or customer-specific bundles.

## Primary Entry Points

- Category HTML landing: https://trading4ai.com/samples/delivery
- Category raw landing: https://trading4ai.com/examples/delivery
- Category JSON catalog: https://trading4ai.com/examples/delivery/index.json
- Category Markdown guide: https://trading4ai.com/examples/delivery/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/delivery`
- `/examples/delivery`
- `/examples/delivery/index.json`
- `/examples/delivery/README.md`
- `/examples/delivery/quant-lab-standard.json`
- `/examples/index.json`
- `/llms.txt`
- `/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 HTML overview at `/samples/delivery`.
4. Read `/examples/delivery` when you want the raw category landing page with discovery guidance.
5. Inspect `/samples/delivery/quant-lab-standard` to understand the public delivery shape.
6. Inspect `/samples/artifacts/eth-breakout-playbook` to see the related public artifact package structure.
7. Fetch `/examples/delivery/index.json` if you need the category-level machine-readable catalog.
8. Fetch `/examples/index.json` if you need the full public sample catalog.

## Which Entry Should You Start With?

- Crawler or search engine: start with `/samples/delivery` because it provides crawlable HTML, internal links, and structured data.
- LLM or agent needing compact discovery: start with `/examples/delivery/index.json` because it gives the category-level machine catalog without parsing HTML.
- LLM needing plain text context: start with `/examples/delivery/README.md` because it is the compact Markdown guide for this category.
- 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 delivery-shape JSON is needed.

## Important Fields

- `public_sample`: marks the object as safe for indexing and public explanation.
- `artifact_bundle`: points to public sample files that illustrate package shape.
- `private_access.claim_token_required`: documents that real fulfillment starts with a claim token.
- `private_access.access_token_required_for_files`: documents that real private files require an access token.

## Boundary

Public delivery examples explain structure. Real paid bundle files remain behind Worker authorization, claim state, entitlement state, and access-token checks.

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/delivery/index.json` for compact category discovery, and `/openapi.json` as the canonical contract.