# TRADING4AI Delivery Public Examples

This directory contains public delivery-shape examples for understanding how artifact bundle shapes were described in older sample surfaces.

Current reliability materials live at `/agent-verification/materials`; this category is secondary reference.

These files are examples only. They do not grant access to protected delivery, customer-specific bundles, or current request-time execution.

## Primary Entry Points

- Current reliability materials: https://trading4ai.com/agent-verification/materials
- 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
- Agent entry point: https://trading4ai.com/.well-known/agent.json
- Legacy runtime snapshot: https://trading4ai.com/openapi.json

## 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 `/agent-verification/materials` for current agent-facing reliability work.
2. Start with `/samples` when you want the top-level HTML public sample hub.
3. Read `/examples` when you want the top-level raw example hub and shared machine entry points.
4. Read the HTML overview at `/samples/delivery`.
5. Read `/examples/delivery` when you want the raw category landing page with discovery guidance.
6. Inspect `/samples/delivery/quant-lab-standard` to understand the public delivery-shape example.
7. Inspect `/samples/artifacts/eth-breakout-playbook` to see the related public artifact package structure.
8. Fetch `/examples/delivery/index.json` if you need the category-level machine-readable catalog.

## Which Entry Should You Start With?

- Crawler or search engine: start with `/samples/delivery` when this secondary archive is needed.
- LLM or agent needing compact discovery: start with `/examples/delivery/index.json`.
- LLM needing plain text context: start with `/examples/delivery/README.md`.
- Tool caller: start with `/.well-known/agent.json`, then use `/llms.txt` and `/for-agents` for static discovery and access-boundary guidance.
- Current reliability task: start with `/agent-verification/materials`, not this sample archive.

## 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.
- `claim_token_required`: documents an older protected-delivery concept without granting access.
- `access_token_required_for_files`: documents an older protected-file concept without granting access.

## Boundary

No live request, order, payment, entitlement, or delivery flow is implied by these public examples.

Public delivery examples explain structure only. They do not prove current delivery, access, customer delivery, or current service output.

Use `/openapi.json` only when intentionally reviewing the legacy runtime snapshot.

For current Pages-only public work, use `/agent-verification/materials`, `/llms.txt`, and `/.well-known/agent.json`.