Documentation

Technical depth when you need it.

The marketing site gives the overview. The technical documentation keeps the implementation details, API reference, runbooks, and procurement packet.

Technical documentation

The full MkDocs site with architecture, quickstart, operations, and reference pages.

Developer quickstart

Run the local stack and make one recommendation request.

Local end-to-end

Run the smoke-tested tenant bootstrap, rules, recommendation, and exposure-log path.

API reference

Endpoints, auth headers, payload shapes, and OpenAPI source ownership.

Operations

Health checks, rollback levers, and first triage runbooks.

Procurement packet

Security, legal, IT, finance, and evaluator review links.

Docs policy

Marketing at the root, technical detail one click away.

The technical documentation remains English-only in v1 because it is tied closely to commands, OpenAPI, schemas, and source files. The marketing site provides the bilingual entry point.

Next step

Evaluate RecSys with a focused pilot.

Start with a commercial evaluation, inspect the technical docs, or open a commercial licensing discussion when procurement needs a clearer path.

Contact Open documentation