Skip to content

I0504 — Prove the recommendation is advisory and publish it as such

Prove with a case that a recommendation never changes the profile a task runs under, and publish the routing claim stating that Majordomus recommends and does not route.

BLOCKED wave 3 · p3 · implementation profile · runs alone

Part of routing-recommendations — Routing recommendations derived from measured cost.

Blocked. This issue cannot start until I0503, milestone:routing-recommendations are done. The status is derived from that, not declared.

Objective

Prove with a case that a recommendation never changes the profile a task runs under, and publish the routing claim stating that Majordomus recommends and does not route.

Why

The distance between recommending a profile and selecting one is one convenience commit wide. A case is the only thing that keeps it, and the claim is where a reader is told which side of the line the tool is on.

Current state

The command answers with a profile and a basis. Nothing proves it cannot act on its own answer.

Desired state

A case starts a task after a recommendation and shows the profile is whatever the worker asked for, and the claim says recommendations only.

Scope

  • test/cases
  • docs
  • site/data/generated

Out of scope

  • Any automatic application of a recommendation, behind a flag or otherwise

Dependencies

Acceptance criteria

  • A case shows a task starting under a profile different from the recommended one, unimpeded
  • The claim cites an implementation path and a test path that both exist and says recommendations only
  • The generated site data regenerates with no stale file

Validation

  • bash test/run.sh
  • scripts/generate-site-data --check

Evidence required

  • suite
  • docs_build

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Risk

A tool that recommends is one flag away from a tool that decides; the case is the record of the decision not to add the flag.

Timeline

started
—
verified
—
completed
—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I0504.yaml. Read it back with majordomus plan show I0504.