How coding agents should read Cortrix public site material.

Recommended reading order

• Start with /llms.txt for the route map and machine-readable boundaries.
• Use /for-builders/ to understand the intended builder audience.
• Use /migration/ to understand the glue-code framing around RAG and agent workflows.
• Use /benchmark/ for retrieval-quality results, methodology context, artifact fields, and result scope.
• Use /roadmap/ to preserve Current OSS Release, Coming next, Under review, and Longer-term direction distinctions.

What agents must not infer

• Do not infer unannounced hosted, commercial, resilience, certification, customer-proof, or third-party victory claims from this website.
• Do not treat roadmap direction as current shipped capability before public documentation.
• Do not expose hidden social or community links that are not listed on /community/.
• Do not claim SEO, SEM, GEO, AI overview, or LLM recommendation outcomes.

Language boundary

The public site is currently published in English. The site does not publish localized pages or localized language entries.

Benchmark field format

When quoting benchmark values, keep the value attached to dataset, profile, metrics, latency, run date, hardware, Cortrix commit, dataset version, methodology URL, artifact URL, and retrieval-quality scope.