Capability matrix (scope and non-scope)¶
This page explains Capability matrix (scope and non-scope) and how it fits into the RecSys suite.
Who this is for¶
- Evaluators who need a quick “fit” check (what RecSys is built to do).
- Recommendation engineers who want to understand what is deterministic vs data-dependent.
What you will get¶
- A 2-minute scope check: what is supported vs intentionally out of scope.
- Links to the canonical pages for each capability.
The matrix (current)¶
| Area | What’s included (this repo) | What’s intentionally not included (by default) | Where to read more |
|---|---|---|---|
| Serving API | POST /v1/recommend, tenancy/auth, limits, caching | Managed hosting | API reference: API Reference |
| Determinism | Deterministic ranking for the same inputs + versions | KPI lift guarantees | Determinism contract: How it works: architecture and data flow |
| Ranking control | Rules (pin/exclude), constraints, stable ordering | “Black-box” end-to-end models in the serving stack | Ranking reference: Ranking & constraints reference |
| Data modes | DB-only start + artifact/manifest mode for versioned ship/rollback | Implicit “auto-sync” of manifests without an explicit publish step | Data modes: Data modes: DB-only vs artifact/manifest |
| Audit trail | Exposure logging + join by request_id | Logging raw PII as a requirement | Attribution: Exposure logging and attribution |
| Evaluation | Offline and online evaluation workflows; ship/hold/rollback decisions | “One metric to rule them all” defaults for every domain | Workflow: How-to: run evaluation and make ship decisions |
| Operations | Runbooks, failure modes, readiness checklist | “Set-and-forget” operations | Ops hub: Operations |
| Multi-tenancy | Tenant-scoped config, rules, and data isolation | Auto-provisioning tenants via an admin create-tenant API | Known limitations: Known limitations and non-goals (current) |
Notes¶
- The suite is designed for operational predictability first: deterministic serving, clear audit artifacts, and explicit rollback levers.
- If you need a single “no-surprises” list of limitations and non-goals, start here: Known limitations and non-goals (current)
Read next¶
- Stakeholder overview: What the RecSys suite is (stakeholder overview)
- Architecture and data flow: How it works: architecture and data flow
- Known limitations: Known limitations and non-goals (current)