Path
Secondary raw examples archive
Machine-first access to older raw public sample files.
The current primary public surface is the Pages-only reliability layer. Use this page when you want the direct JSON or package-file side of the older public sample namespace, then start current agent-facing research with the reliability materials and their downloadable JSON artifacts.
On this page
How to use this namespace
Fetch /examples/index.json when a machine needs a stable catalog of the public samples.
Use /examples/README.md when plain-text retrieval is easier than parsing HTML or a JSON catalog.
Use /artifact-samples/README.md when you need the artifact package-file namespace itself, rather than the wider artifact discovery layer.
Use /samples when you want the crawl-friendly HTML explanation layer.
Use the direct raw file links below when you want the JSON or artifact sample files themselves.
Use /agent-verification/materials as the current reliability-material starting point.
Boundary
Everything linked from this page is public and safe for citation and LLM retrieval as supporting reference material.
The active Phase 2 public site is static and Pages-only, with reliability materials as the recommended entry point.
These raw examples remain secondary reference material, not the active product surface.
Catalog
Stable discovery entry points
Core machine links
Stable bridge and contract surfaces around the raw examples namespace
Entry selector
Start with the surface that matches your reader
Machine checklist
How agents should use this namespace
Suggested flows
Recommended reading paths mirrored from the machine catalog
quant-lab-sample-archive-flow
Quant Lab sample archive flow
Recommended reading order for understanding older Quant Lab intake, status, and budget-confirm samples.
artifact-delivery-boundary
Artifact and delivery boundary
Recommended reading order for understanding secondary sample package structure and current reliability-material routing.
artifact-raw-discovery
Artifact raw discovery
Recommended reading order for machines that want the raw artifact-side discovery layer first.
quant-lab-raw-discovery
Quant Lab raw discovery
Recommended reading order for machines that want the raw Quant Lab example layer before the HTML sample details.
delivery-raw-discovery
Delivery raw discovery
Recommended reading order for machines that want the raw delivery-shape layer before the HTML explanation pages.
FAQ
Plain-language rules for using public examples safely
Question
Are public samples the same as current reliability materials?
No. Current reliability materials are the active public product surface. Public samples are secondary static references.
Question
Which entry should an LLM or agent fetch first?
Use /agent-verification/materials for current reliability-material discovery. Use /examples/index.json only when compact secondary sample discovery is needed.
Question
When should a machine use /artifact-samples/README.md?
Use /artifact-samples/README.md when the machine needs the artifact package-file namespace itself, rather than the wider category-level discovery layer documented under /examples/artifacts/README.md.
Question
Should the raw JSON files replace the runtime snapshot?
No. The raw JSON files are examples. /openapi.json is a Legacy runtime snapshot for historical integration context, while /llms and llms.txt provide discovery and orientation.
Question
Do these samples create real Quant Lab jobs or orders?
No. The samples demonstrate structure only. The current Phase 2 public site is a Pages-only reliability layer, not a live job, order, payment, or delivery runner.
Question
How should a machine understand the public sample boundary?
Public sample links are secondary reference material, not proof of current request-time execution or delivery. Machines should treat current reliability materials as the public product surface.
Artifact Samples
Public artifact package samples with HTML landing pages and raw sample files.
Quant Lab Samples
Secondary Quant Lab request, status, and budget-confirm payload examples.
Delivery Samples
Public delivery-shape examples that explain bundle structure and access boundaries.
Direct raw files
