Skip to content

Every feature against every interface

The matrix both ways: each feature against the command line, the HTTP API, MCP, the Cockpit and the documentation, and each capability module, public command and object kind against the features that name it. Every mark is derived; a gap is shown.

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.

Features against the interfaces they are exposed through
Feature cli api mcp cockpit docs
Declare once ✓on Command line ✓on HTTP API ✓on MCP ✓on Cockpit ✓on Documentation
Interfaces ✓on Command line ✓on HTTP API ✓on MCP ✓on Cockpit ✓on Documentation
Coordination ✓on Command line ✓on HTTP API ✓on MCP ✓on Cockpit ✓on Documentation
Worktrees ✓on Command line ✓on HTTP API ✓on MCP ✓on Cockpit ✓on Documentation
Continuity ✓on Command line ✓on HTTP API ✓on MCP ✓on Cockpit ✓on Documentation
Knowledge ✓on Command line ✓on HTTP API ✓on MCP ✓on Cockpit ✓on Documentation
Doctrine ✓on Command line ✓on HTTP API ✓on MCP ✓on Cockpit ✓on Documentation
Finish contract ✓on Command line not on HTTP API not on MCP not on Cockpit ✓on Documentation
Policy ✓on Command line not on HTTP API ✓on MCP not on Cockpit ✓on Documentation
Cockpit not on Command line ✓on HTTP API ✓on MCP ✓on Cockpit ✓on Documentation
Provenance ✓on Command line not on HTTP API ✓on MCP ✓on Cockpit ✓on Documentation
Install ✓on Command line ✓on HTTP API ✓on MCP ✓on Cockpit ✓on Documentation
Planning ✓on Command line ✓on HTTP API ✓on MCP ✓on Cockpit ✓on Documentation
Context ✓on Command line ✓on HTTP API ✓on MCP ✓on Cockpit ✓on Documentation
Use cases ✓on Command line not on HTTP API ✓on MCP not on Cockpit ✓on Documentation
Skills ✓on Command line not on HTTP API ✓on MCP not on Cockpit ✓on Documentation
Why ✓on Command line ✓on HTTP API ✓on MCP ✓on Cockpit ✓on Documentation
Benchmarks ✓on Command line ✓on HTTP API ✓on MCP ✓on Cockpit ✓on Documentation
CI ✓on Command line not on HTTP API not on MCP not on Cockpit ✓on Documentation

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.

Capability modules

Modules of the Rust executable. Every capability, route, tool and reference page behind a feature comes from one of these.

  • Generated artifacts artifacts Declare once
  • Capabilities capabilities Declare once
  • Command graph commands no stable feature names it
  • Continuity continuity Continuity
  • Deployment deploy no stable feature names it
  • Directory contracts directories Context
  • Distribution distribution Install
  • Repository environment environment no stable feature names it
  • Executions executions no stable feature names it
  • Graphs graph Knowledge
  • Health health DoctrineCockpit
  • Objects objects Interfaces
  • Obligations obligations no stable feature names it
  • Peers peers Coordination
  • Performance perf Benchmarks
  • The plan and its derivations plan no stable feature names it
  • Product product Declare once
  • Public API quality quality no stable feature names it
  • Release release no stable feature names it
  • Repository repository InterfacesContext
  • Traceability trace Planning
  • Web surfaces web Interfaces
  • Why why Why
  • Worktree topology worktree CoordinationWorktrees

Public commands

Subcommands of the shell tool. A feature names the ones a person runs to use it.

Object kinds

Kinds of the layer, with the objects this repository holds of each.

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