Reasoning that works with or without advisors, and review that is recorded rather than claimed

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.

Where it sits

domain

Coordination — Every worker declares the paths it will touch, sees who else is working and where, and hears about a collision before it is committed.

areas of work

coordination

names

MeshModels

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.

in the Cockpit, of a running server

/cockpit/reasoning Reasoning

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.

• ○declared status: guaranteed ○recorded evidence: not run Majordomus reasons, decides, implements and validates with no advisor at all: absent advisors are reported as ordinary state, material uncertainty gets a structured local review, and the conclusion claims no independent review test/cases/730_reasoning_works_with_no_advisor.sh
• ○declared status: guaranteed ○recorded evidence: not run Every advisor transport is held to one contract — typed failures, deadlines, cancellation, normalised answers, reported usage, redacted secrets — proven against fakes with no network, model or credential test/cases/731_advisor_transport_contract.sh
• ○declared status: guaranteed ○recorded evidence: not run Advisors that disagree never decide by count: a conclusion is refused while a disagreement on its assessment is unsettled, a resolution needs evidence, and every answer received must be weighed test/cases/732_disagreement_is_settled_by_evidence.sh
• ○declared status: guaranteed ○recorded evidence: not run An advisor that times out, is rate limited, refuses its credential or answers malformed is recorded as exactly that, never blocks the work, opens a circuit that closes again after its cooldown, and never fails the session test/cases/733_advisor_failure_and_recovery.sh
• ○declared status: guaranteed ○recorded evidence: not run A decision and its provenance survive the session: the next session finds them in its context and handover, reuses a standing conclusion instead of consulting again, and reopens it only on new evidence test/cases/734_reasoning_survives_the_session.sh
• ○declared status: guaranteed ○recorded evidence: not run Advisors are declared once, in share/advisors.yaml, by reference to the provider table and the model catalogue; a new advisor reaches the command line, the policy, HTTP, OpenAPI, MCP and the Cockpit with no consumer edited test/cases/735_a_new_advisor_needs_no_consumer_edit.sh
• ○declared status: guaranteed ○recorded evidence: not run A session cannot claim review it did not get: a consultation must name an advisor its recorded plan selected, a conclusion's review is computed, and reasoning check and doctor refuse a forged record, provider coupling, a model credential in CI and a refused claim in a document test/cases/736_reasoning_check_refuses_drift.sh

The rules that hold it

• ✕blocking Advisors are optional; reasoning, governance and CI never depend on oneproject.advisors-are-optional
• ✕blocking Independent review is a recorded fact, weighed by evidence, never claimed and never countedproject.review-is-recorded-not-claimed

The decisions behind it

• adr-0098Reasoning is provider-independent, advisors are optional, and review is a recorded fact rather than a claim proposed

Using it

From the executable's command line

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

• majordomus reasoning advisors [OPTIONS]

  Every advisor with its status and why, the mode in force, and who can provide each advisory capability now; no advisor at all is an ordinary answer

• majordomus reasoning plan [OPTIONS]

  Whether a stated uncertainty warrants independent review, how much, and from which available advisors — with every advisor left out and why; records nothing

• majordomus reasoning record [OPTIONS]

  Record one reasoning step of the open task from JSON (`{"kind":"assessment",...}`) read from --file or standard input; a record that breaks a rule is refused and nothing is written

• majordomus reasoning status [OPTIONS]

  The reasoning state of the open task — assessments, consultations, disagreements, conclusions, the timeline — and the report a handover carries

• majordomus reasoning explain [OPTIONS] <ID>

  One record with the whole chain of its assessment: why a decision was made

• majordomus reasoning check [OPTIONS]

  Check that reasoning stays provider-independent and that every record is consistent; exit 10 on a finding

Where this page comes from

the file

.ai/repo/features/reasoning.md

the same answer

majordomus product show reasoning

read further

Reasoning

Related features

• same domain

  Coordination

  ✓feature status: stable

  Every worker declares the paths it may touch, every session can see who else is attached and what they announced, and a collision is reported before it is committed.

  Explore Coordination →

• same domain

  Worktrees

  ✓feature status: stable

  A branch's worktree is where git says it is, never where somebody chose to put it, and a misplaced one is a diagnostic with a remedy rather than a mystery.

  Explore Worktrees →

• named by this feature · same domain

  Mesh

  ✓feature status: stable

  Majordomus runtimes of one repository — on one machine or several — discover each other, link through a signed handshake, and share sessions, claims, handovers and reviews through one replicated journal that survives disconnects, crashes and partitions.

  Explore Mesh →

• named by this feature · same domain

  Models

  ✓feature status: stable

  One declared catalogue of vendors and models — capabilities, context, lifecycle, no fabricated facts — and a routing answer that names why every candidate was chosen or excluded.

  Explore Models →

• same domain

  Planning

  ✓feature status: stable

  An issue records what happened to it and the engine derives whether it is blocked, ready, active, verifying or done from the dependency graph, so the roadmap cannot disagree with the plan.

  Explore Planning →