Skip to content

The failure modes it answers are objects, not marketing pages

Every operational moment the tool exists for is one file with the signals that identify it and the mechanisms that answer it, and a reader's own symptoms resolve to a diagnosis by counting, not by inference.

status
feature status: stable
domain
Surfaces

What it does

majordomus why lists the moments, narrowed by any facet the catalogue reports; why diagnose takes the signals a reader recognises and answers with the areas they weigh towards and the mechanisms that answer them, each recommendation carrying the moments that produced it; why validate refuses a reference that resolves to nothing, offering the nearest candidate.

What it does not do

A moment that would be fixed by a better model does not belong in the catalogue. There is no weighting and no percentage in a diagnosis, because there is no model behind one.

How it works

The capability modules of the executable this feature names, each with the capabilities it composes. The interfaces each one reaches are listed under Interfaces below: they are projections of one declaration, not separate registrations.

Why why behaviorally verified

The operational failure modes this tool is a response to: the moments a reader recognises, the audiences that recognise them, the areas they fall under, and what a reader's own symptoms imply. Every entry is a file under the layer's why section; nothing here holds a list, and a moment added there is answered by all of these without a registration anywhere.

The objects it is made of

Kinds of the layer. Each is a schema, a source class and a file on disk; the number beside it is what this repository holds today, counted at build time.

  • moment38
  • audience8
  • area9

Where it sits

domain
Surfaces — One declaration in the repository becomes the command line, the HTTP API, MCP, the UI, the Cockpit, the documentation and this site, and a projection that disagrees with it fails the build.
areas of work
documentation
names
Declare onceUse cases
named by
Use cases

Interfaces

Each capability behind it, on every interface it is projected onto. A link goes to this site's reference for that interface; an HTTP route and an MCP tool are answered by a running majordomus serve, not by this site.

The capabilities behind this feature, by interface
capabilitycommand lineHTTPMCP tool
why.areas majordomus why areas GET /api/v1/why/areas majordomus_why_areas
why.audiences majordomus why audiences GET /api/v1/why/audiences majordomus_why_audiences
why.diagnose majordomus why diagnose GET /api/v1/why/diagnose majordomus_why_diagnose
why.list majordomus why list GET /api/v1/why majordomus_why
why.moment majordomus why show GET /api/v1/why/moment majordomus_why_moment
why.validate majordomus why validate GET /api/v1/why/validate majordomus_why_validate

Evidence

What is guaranteed

Each claim this feature names, with the status its row declares, the verdict the recorded runs support, and the test that settles it.

Executable use cases

The rules that hold it

  • blocking An operational failure mode is a catalogue object, never a pageproject.why-catalogue-is-canonical

The decisions behind it

Using it

From the executable's command line

The synopsis of each, as the executable's own help prints it.

Where this page comes from

the file
.ai/repo/features/why.md
the same answer
majordomus product show why
read further

Why — the operational moments, as data

Searches the titles and descriptions of every page this site publishes.