Choose one route.
Start with a workflow whose failures, policy needs, or provider dependencies are already visible to the team.
Developers / stable application boundary
Instrument one route. Expand deliberately.
View integration interface ↓
Keep application intent stable while routing, policy, trace context, and evaluation evolve behind an explicit integration boundary.
Integration interface / TypeScript
The application sends intent, not provider wiring.
route.ts
const result = await aurora.run({
route: "support.refund",
input: request,
context: {
environment: "production",
region: user.region,
toolScope: ["refund.lookup"]
},
evaluate: ["policy", "quality"]
});
return result.output;Integration sequence
Preserve context.
Attach application metadata and outcome signals before changing routing behavior or adding automated evaluation.
Promote gradually.
Introduce policy and alternate targets behind explicit environment changes, review, and rollback.
Reference event envelope
A trace contract should survive provider change.
event.json
{
"trace_id": "trace_8f2a",
"span": "route.selected",
"parent": "policy.resolved",
"attributes": {
"route": "support.refund",
"environment": "production",
"decision_version": "policy_v1"
}
}Continue the system view