Modules

• artifactsGenerated artifacts What `majordomus generate` writes: every document with the encodings it is committed in — JSON for a program, YAML beside it, Markdown for a reader — each with its schema, its source and its hash, reconciled with the working tree. The declaration is the generator's own manifest; nothing here keeps a list. artifacts.list apps/majordomus-cli/src/capability/builtin/artifacts.rs · behaviorally_verified
• capabilitiesCapabilities The registry seen through itself: every capability with its kind, stability, provenance, exposures, benchmark and cache policy, and one capability in full. capabilities.describecapabilities.listcapabilities.projections apps/majordomus-cli/src/capability/builtin/capabilities.rs · behaviorally_verified
• commandsCommand graph Every command this repository offers, from whichever program offers it: the Rust executable, the shell tool that carries the task lifecycle, and the workflows the repository declares for a person to run. Composed from the three declarations that already exist — the clap tree, the shipped command registry and the workflow runner's own dump — never from a list. Each command carries what running it changes, what it needs, where its argument values come from, and every surface that carries it, with the reason when one does not. commands.getcommands.graphcommands.list apps/majordomus-cli/src/capability/builtin/commands.rs · implemented
• continuityContinuity What this checkout's lifecycle is holding: the open episode, the record the next worker would resume from with the label that says how far to trust it, the newest progress note, and what is blocking acceptance. Read from the local half of the layer, which this process serves to the worker in front of it and never publishes. continuity.state apps/majordomus-cli/src/capability/builtin/continuity.rs · behaviorally_verified
• deployDeployment The deployments this repository declares, read from the canonical objects the index holds, and whether they would work — decided against the capability registry this process built and the workspace it sits in. Every operation is a read: a deployment is changed by the trusted command line and by CI, never over HTTP and never by an MCP client. deploy.checkdeploy.getdeploy.list apps/majordomus-cli/src/capability/builtin/deploy.rs · behaviorally_verified
• designDesign system The one declaration of how every surface of this tool looks — the semantic roles, the status vocabulary, the type scale, the theme contract — as this executable carries it: its fingerprint, its tokens, what any one of them means, and whether the colours it pairs are readable on one another. The stylesheets the site and the Cockpit load, the tokens the executable's own pages compile in, and the dataset the site's templates read are all projections of it; a page compares its `--mj-design` with this fingerprint to know whether it is wearing the design this executable was built with. design.contrastdesign.explaindesign.systemdesign.tokens apps/majordomus-cli/src/capability/builtin/design.rs · behaviorally_verified
• directoriesDirectory contracts The layer's directories as a hierarchy: the contract each one declares, what it owes and which contract said so, and the chain that applies to it once inheritance is resolved. directories.list apps/majordomus-cli/src/capability/builtin/directories.rs · behaviorally_verified
• distributionDistribution How this project is packaged, published and installed: the platforms a release builds, the artifact names the one naming function derives, the installer's canonical command, the releases that were published, and what this build itself is. Every answer comes from share/distribution.yaml and the release records; no surface here states a fact of its own. distribution.artifactdistribution.builddistribution.modeldistribution.releasesdistribution.status apps/majordomus-cli/src/capability/builtin/distribution.rs · behaviorally_verified
• environmentRepository environment What this checkout is right now: the project and its version, the repository and its layer, version control, the toolchains it declares, what the layer holds, the workflows a person can run, the provider projections and the local services — one typed snapshot, with a provenance entry for every value in it. The direnv banner, the Cockpit's overview and this route are renderings of the same value. environment.explainenvironment.status apps/majordomus-cli/src/capability/builtin/environment.rs · behaviorally_verified
• executionsExecutions Running a capability of this registry as work that can be watched: started, followed event by event over the live channel, read back afterwards, and asked to stop. In memory; an execution does not outlive the process that accepted it. executions.cancelexecutions.demonstrateexecutions.eventsexecutions.getexecutions.listexecutions.protocolexecutions.start apps/majordomus-cli/src/capability/builtin/executions.rs · behaviorally_verified
• graphGraphs The graphs derived from the registry and the index: the executable's own capability registry, the shape of the layer, the rule dependencies, the decisions and what they put in force, and the use cases and what they exercise. Canonical nodes and edges; a rendering library is a consumer, never the shape. graph.getgraph.list apps/majordomus-cli/src/capability/builtin/graph.rs · behaviorally_verified
• healthHealth Whether what this process serves is healthy, decided by the engines that already decide it: the index's diagnostics, the registry builder, the benchmark projection's coverage, the comparison `generate --check` makes and the lease reading `server.status` answers from. No check here has an opinion of its own. health.livehealth.readyhealth.report apps/majordomus-cli/src/capability/builtin/health.rs · behaviorally_verified
• objectsObjects The declarative objects of the repository's AI layer: rules, prompts, profiles, policy, documents, milestones, issues, claims, and whatever kinds the repository adds; listed, read by URI, and searched. objects.getobjects.listobjects.searchobjects.verify apps/majordomus-cli/src/capability/builtin/objects.rs · behaviorally_verified
• obligationsObligations What a task owes before it may be called completed, and whether the evidence that discharged each obligation still describes this tree. The vocabulary is data the distribution ships and answers in any clone; the closure is read from the local half of the layer, which this process serves to the worker in front of it and never publishes. Read, never written: `majordomus evidence` records, and a second writer for one ledger would be a second account of the same events. obligations.closureobligations.vocabulary apps/majordomus-cli/src/capability/builtin/obligations.rs · behaviorally_verified
• peersPeers The clients attached to this repository's shared server, named by their own initialize, and what each announced it is working on. In memory; gone with the process. peers.announcepeers.list apps/majordomus-cli/src/capability/builtin/peers.rs · behaviorally_verified
• perfPerformance This process's work counters and phase timings: what happened once at startup and what happens per call, for the structural tests and the benchmark evidence. perf.counters apps/majordomus-cli/src/capability/builtin/perf.rs · behaviorally_verified
• planThe plan and its derivations The milestone and issue model of this repository, and everything derived from it that nobody authored: the status of each record, the dependency graphs above and below the milestone boundary, the topological execution waves, the roadmap order, the milestone being executed and the one issue to take next. Status is never stored — a record says what happened to it and the status follows from that and from the state of its dependencies — so no file can contradict the graph. The four operations that write a lifecycle marker into a record stay on the command line: a capability of this registry never writes to the repository. plan.issuesplan.modelplan.nextplan.recordplan.roadmapplan.statusplan.validateplan.waves apps/majordomus-cli/src/capability/builtin/plan.rs · behaviorally_verified
• productProduct What this repository's product does for a person, as the features under the layer's features section declare it: each feature made of modules, commands, kinds, rules, documents, decisions, claims, use cases, Cockpit areas and web surfaces it names, with the interfaces it is exposed through, every count, the moments it answers and what is guaranteed derived from those references. The matrix of features against interfaces, the providers the tool has an adapter for, and the model's own validation. The homepage is a reader of this module and holds no inventory of its own. product.featureproduct.featuresproduct.matrixproduct.providersproduct.validate apps/majordomus-cli/src/capability/builtin/product.rs · behaviorally_verified
• qualityPublic API quality What this executable's own public surface is held to, measured from its syntax tree: documentation that says more than the signature, an executable example on everything that carries behaviour, a module boundary something exercises, and every command of the command line accounted for against the capability registry. The rules are project.rust-public-api-quality and project.operation-transport-parity; this is the measurement of them. quality.report apps/majordomus-cli/src/capability/builtin/quality.rs · behaviorally_verified
• releaseRelease What this project has shipped and what it would ship next, derived rather than maintained: the changelog composes the layer's release records, the decisions dated inside each release's window and the conventional commits in its range; the version report reads the two places the version is stated and says what the commits since the last release imply it should become. release.changelogrelease.version apps/majordomus-cli/src/capability/builtin/release.rs · implemented
• repositoryRepository The repository this process serves: its layer, its git state, the state of the index built from it, and its scope: what a worker reads of it and what it never reads. repository.inforepository.scoperepository.scope_classify apps/majordomus-cli/src/capability/builtin/repository.rs · behaviorally_verified
• serverServer The shared server of this checkout and of every other checkout of the same git repository: what each lease says, whether the server it names answers, whether what answers is the code on disk at this executable's version, and how many peers each one holds. server.status apps/majordomus-cli/src/capability/builtin/server.rs · behaviorally_verified
• traceTraceability Which branches and commits realised an issue, and which issue and milestone a commit served — derived from git and from the canonical project model on every call, stored nowhere. A branch names an issue when one of its path components is an issue id; a commit belongs to the issue whose branches hold it; a commit no such branch holds is reported as unattributed rather than left out, because work with no execution contract is what a traceability report exists to make visible. Pull requests are a GitHub fact and this executable makes no network call: `scripts/traceability` reads them and joins them to this answer over the branch name. trace.committrace.issuetrace.report apps/majordomus-cli/src/capability/builtin/trace.rs · behaviorally_verified
• webWeb surfaces What this repository exposes over HTTP, resolved from the producers that make it rather than from a register anybody maintains: the routes the executable answers itself, the documentation build, and every generated report that declared its own mount. The same resolution serves the router, renders the home page and composes a publication. web.surfaces apps/majordomus-cli/src/capability/builtin/web.rs · behaviorally_verified
• whyWhy 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. why.areaswhy.audienceswhy.diagnosewhy.listwhy.momentwhy.validate apps/majordomus-cli/src/capability/builtin/why.rs · behaviorally_verified
• worktreeWorktree topology Where every linked git worktree of this repository belongs and where each one is. The container is the primary checkout's sibling named with `-wt`, the path under it is the branch name with its hierarchy kept, and both are derived from git's own identity — the common directory, the registered worktrees, the branches — never from a registry, a configuration or the current directory. A worktree somewhere else is a typed diagnostic with a remedy; the migration that repairs it is a command-line operation of the same service. worktree.inspectworktree.migration_planworktree.statusworktree.topology apps/majordomus-cli/src/capability/builtin/worktree.rs · behaviorally_verified

The declarative modules — one per kind of the layer, one resource per object — are the kinds table on the registry page; their objects are the repository's, not the executable's.