Every feature against every interface

Every mark is derived. A feature is on an interface because a capability module, a shell command or an object kind it names is projected there — a command-line path, an HTTP route, an MCP tool or resource, a Cockpit area, a document. No page and no file says so.

declared + test

Of the claims a feature names, how many docs/CLAIMS.yaml declares guaranteed, each naming the test that is to prove it. A declaration, not a verdict: nothing here says the test ran.

supported by a run

Of the same claims, how many a recorded run supports, as majordomus evidence show derives it from the ledger; unknown when no evidence reached this build. How evidence is recorded.

What every part of the product belongs to

The other direction: each capability module of the executable, each public command of the shell tool and each kind of object of the layer, with the features that name it. A row with no feature is a gap this page shows rather than hides, and closing it is one reference in one file.

The same two tables on the command line: majordomus product matrix. Over HTTP: GET /api/v1/product/matrix. Over MCP: majordomus_product_matrix.