Skip to main content

Inference Handoff

Blueprint · ← Autonomy shape · Inference handoff · Model routing →

Inside the loop, the agentic app does not call a vendor model id. It asks Plane ③ for inference, then treats the completion as a proposal.

THE CLAIM

Need inference → gateway. Need a side effect → PEP. Hard-coded model URLs and auto-run tools both skip a plane.

Request sequence (one loop step)

  1. Assemble messages from session memory (no credentials)
  2. Attach scoped tool schemas for this pattern/stage, or none
  3. Call Plane ③ with model_profile + task type (plan, synthesize, or classify)
  4. Receive completion (text and/or tool proposal)
  5. If text / done → validate output schema; observe; return or continue
  6. If tool proposal → check against pinned manifest → PEP
  7. On ALLOW → run downstream; observe; feed result into the next step
  8. On DENY / STEP_UP → follow PGAR; do not retry the same proposal as if it were allowed

Gateway how-to: Model routing. PEP how-to: PEP enforcement.

Task type on each call

Pass a task signal so Plane ③ can pick the endpoint. Do not bury it in the prompt.

TaskWhenTypical model_profile use
planPattern 1/3 next-step, Pattern 2 stage with llm_role: planReasoning tier
synthesizeUser-facing answer, Pattern 0 completionChat or reasoning per route
classifyRare in-loop; Plane ① fallback is a different callerLightweight

model_profile on the route is a coarse tier (reasoning-standard, fast-chat). The gateway resolves it to an approved endpoint. The app never stores a vendor model name as the production target.

Proposal gate (before PEP)

Unknown or out-of-manifest tools stop at the app. They never reach downstream.

CheckFail closed
Tool name ∈ pinned manifestReject proposal
Args match JSON schemaReject proposal
Current-stage allowlist (Pattern 3)Reject cross-stage tools
Loop / stage budget remainingStop the run

See PGAR LLM proposal · Manifest registry.

Failure classes

FailureSymptom
App calls vendor chat API directlyPlane ③ bypass; no capability matrix, cost, or canary
Model id hard-coded in the agentRegion/data-class routing skipped
Framework auto-executes toolsPEP skipped
Proposal retried after DENY as ALLOWPolicy bypass

Trace fields

orchestration_step, task_type, model_profile, model_route_id (from Plane ③), proposal, proposal_in_manifest, pep_verdict

Eval: Eval Tool plane · Eval Action plane.

Model routing playbooks (Plane ③) → · PGAR Agentic app