Skip to content

Routing recommendations will be derived from measured cost and outcome data

**Planned.** Once cost per accepted outcome exists per profile and task class, Majordomus can say which profile produced the best acceptance rate per unit cost for a class of work — as a recommendation to change a profile, never as an automatic model choice.

planned Specified and not implemented. Named so the omission is visible.

Recommendations only. Majordomus does not invoke a model.

What it means

Planned. Once cost per accepted outcome exists per profile and task class, Majordomus can say which profile produced the best acceptance rate per unit cost for a class of work — as a recommendation to change a profile, never as an automatic model choice.

How it works

Nothing is implemented. Recommendations would be derived from the ledger and telemetry; Majordomus will still not invoke a model.

How to see it

There is nothing to run.

What it does not cover

Everything, today. Dynamic routing of requests is not on the roadmap at all; recommendations to a person are.

Why it exists

The source environment routed by the worker's job title with invented performance figures. Routing that is recommended from measured outcomes, and decided by a person, is the honest version.

Detail rendered from docs/claims/routing.md.

Provenance

defined in
read it on this site · docs/DESIGN.md
implemented in
nothing yet
proved by
no test — which is why this is not marked guaranteed
claim id
routing

What would make this guaranteed

0.5 Routing recommendations derived from measured cost BLOCKED Blocked by cost-per-accepted-outcome, so this claim cannot move yet. Shipping the milestone does not promote the claim: it reaches guaranteed when an implementation, a behavioural test and a blocking CI job exist for it.