Skip to content

The failure modes it answers are objects, not marketing pages

Moments, audiences and areas are kinds of the layer; a moment names the commands, capabilities, claims, rules and use cases that answer it, each reference validated; the catalogue, the questionnaire, the diagnosis and every page and filter are derived from those files.

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
stable
exposed through
area
documentation

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.

The capabilities behind it

The capability modules of the executable this feature names, each with the capabilities it composes. The command line, the HTTP route, the MCP tool and the reference beside every row are projections of one declaration, not four 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.

  • Operational areas query

    $ majordomus why areasGET /api/v1/why/areasmajordomus_why_areas

  • Audiences query

    $ majordomus why audiencesGET /api/v1/why/audiencesmajordomus_why_audiences

  • Diagnose a selection query

    $ majordomus why diagnoseGET /api/v1/why/diagnosemajordomus_why_diagnose

  • The catalogue query

    $ majordomus why listGET /api/v1/whymajordomus_why

  • One moment query

    $ majordomus why showGET /api/v1/why/momentmajordomus_why_moment

  • Validate the catalogue query

    $ majordomus why validateGET /api/v1/why/validatemajordomus_why_validate

apps/majordomus-cli/src/capability/builtin/why.rs

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

The rules that hold it

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

What is guaranteed

Executable use cases