Jev chooses a rule, not arbitrary credentials
fm-dispatch-resolve.sh exposes rule_ IDs and default as the closed Choice set. Provider/scope eligibility and ranking are calculated afterward in code.
Inspect the supporting source ↗Firstmate can optionally use Jev to match task briefs to dispatch rules before local policy chooses an Agent configuration.
Sends the task brief and candidate rules to Jev, then resolves execution profiles with confidence and local conditions.
Separates semantic matching from the final dispatch policy.
This is opt-in dispatch assistance, not a claim that the whole Firstmate workflow uses Jev by default. Task briefs are sent to TypeSafe.
Choose an eligible coding-agent profile from an owner's dispatch rules and quota evidence.
Material analysed:
fm-dispatch-resolve.sh exposes rule_ IDs and default as the closed Choice set. Provider/scope eligibility and ranking are calculated afterward in code.
Inspect the supporting source ↗The 0.6 floor produces ambiguous status; unverifiable quota floors and captain-approval rules can escalate. A high model score cannot make an unknown account balance trustworthy.
Inspect the supporting source ↗Use this pattern when owner-defined quota and approval constraints matter. It is more specific than asking a model to pick a cheap provider from prose.
Trace the response key checks, confidence-floor branch and final eligible-candidate ranking in the pinned shell script. Use synthetic config/quota fixtures before dispatching a real agent.