Tessen Docs

Capabilities

What Tessen can be asked to do — and what it registers, names and deliberately does not offer.

A capability is an outcome Tessen can reach, not a model. You do not choose a model; Tessen chooses what it needs to reach the outcome.

Status is declared, not inferred

Every capability carries a status of available, partial or unbuilt, and anything not available carries a written reason. Unbuilt capabilities are published deliberately: a list of only what works is a brochure, and a capability nobody registered is indistinguishable from one nobody thought of.

Each one also names the modules that back it, so the claim can be checked against the product rather than taken on trust.

GET /api/capabilities