I3662 — models.route names the funding source a route would draw on, as an inference with its basis, in the declared source order

!CANCELLED wave 2 · p2 · implementation profile · parallel safe

Part of every-model-call-is-paid-from-a-declared-source — How a model call Majordomus starts can be paid is declared by the vendor with evidence, and each call names the source it was declared to draw on.

Objective

Extend models::route so that its RoutingDecision carries the funding source the chosen model would draw on, labelled inferred with the credential presence and holding that implied it, chosen by a repository policy that orders source kinds (local, then credit_grant, then metered; a subscription only for the client that owns the seat); a held source whose credential is unset is excluded with that reason.

Why

Routing today picks a model by capability and credential presence alone. With several sources on one vendor, the same model can be paid by a credit grant or by metered billing, and the owner wants the grant used first; the choice must be policy data the route reads, and what it says about payment must be a prediction, not a measurement.

Current state

RoutingDecision names a model and the models it excluded; nothing names how the call would be paid.

Desired state

Every route names its predicted source and the basis of the prediction, and the order is declared policy.

Scope

• apps/majordomus-cli/src/models/mod.rs
• apps/majordomus-cli/src/capability/builtin/models.rs
• .ai/repo/policy.yaml
• docs/generated

Dependencies

• I3660○READY A vendor declares its funding sources in the model catalogue, each with dated, quoted vendor evidence
• I3661!CANCELLED Which funding sources the owner holds, and their caps, are the owner's local declaration and never projected

What waits on this

• I3667!CANCELLED A run that would fall through to metered billing while a grant is held, or cross a declared cap, is told before it starts

Acceptance criteria

• With a held credit grant and a held metered source on one credential, the route names the credit grant, labelled inferred, with its basis
• Reordering the declared policy changes the answer without a code change (test)
• A subscription source is never chosen for a headless caller
• No held source usable: the route answers local or none, as a status, never an error

Validation

• cargo test --manifest-path apps/majordomus-cli/Cargo.toml models::
• majordomus generate --check

Evidence required

• test_a_route_names_its_funding_source_as_an_inference

Evidence

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

Completion report

Cancelled 2026-10-21 on feature/intent-funding-sources by the plan's critique (findings one-credential-cannot-carry-a-source-order and route-loses-its-purity): the credit grant and metered billing are reached through one ANTHROPIC_API_KEY, so which balance a call draws on is the vendor's billing order and no source order Majordomus declares changes it; and reading the environment and holdings in models::route would break ADR 0049's pure routing. Reopen only with vendor evidence of draw order, or for an order across different credentials, passed to route as an explicit input.

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/I3662.yaml. Read it back with majordomus plan show I3662.