Your allocation policy, running on our intelligence
Bring your own rules for how tokens get allocated — by team, model, consequence, or budget. Arcline evaluates every work item against them in real time, proposes better rules from your data, and self-tunes inside approval gates you control.
Bring your integration
Point your gateway, proxy, or agent framework at the policy API. Rules evaluate inline on every request.
Rules as code
Policies are a versioned condition → action DSL. Manage them in the UI or sync from your repo via CI.
Approval gates
Set autonomy per category. The engine tunes freely inside bounds, and escalates anything outside them.
Downgrade low-consequence work
Org-definedRoute work items scored below complexity 3 and consequence 2 to a cheaper model tier.
complexity < 3 AND consequence < 2route_model(tier = 'efficient')Protect high-consequence work
Org-definedForce frontier-tier models for payments, auth, and incident-response work regardless of budget pressure.
repo IN ('payments', 'auth') OR label = 'incident'route_model(tier = 'frontier', override_budget = true)Retry budget circuit breaker
Arcline intelligenceCut token allocation 50% for any person-model pairing whose rolling 14-day ship rate drops below 40%.
pairing.ship_rate(14d) < 0.40throttle_allocation(0.5) THEN notify(lead)Verbosity guard
Self-healingFlag sessions exceeding 2.5x median token volume for equivalent complexity; suggest context pruning.
session.tokens > 2.5 * median(tokens | complexity)flag_session() THEN suggest(playbook = 'context-pruning')Weekend batch deprioritization
Org-definedShift non-urgent bulk analysis jobs to off-peak windows with cheaper batch pricing.
job.type = 'batch' AND priority < 3defer_to(window = 'off-peak')Route Legal contract review to Sonnet tier
Claude Sonnet matches Opus ship rate (94% vs 95%) on contract-review work at 42% of the cost. Quality delta is inside noise for consequence ≤ 3.
Evidence: 212 work items · 8 weeks · Legal team
team = 'Legal' AND task = 'contract-review' AND consequence <= 3route_model('claude-sonnet-4.5')Raise allocation for top-decile pairings
The top 6 person-model pairings are hitting allocation ceilings weekly while returning 19x. Every throttled week costs ~$34K in unrealized value.
Evidence: 6 pairings · 4 consecutive weeks at ceiling
pairing.roi(30d) > 15 AND pairing.utilization > 0.95raise_allocation(1.5x, review_after = '30d')Anomaly: Gemini retry loop in CI pipeline
A CI automation account is burning 4.2M tokens/day in a retry loop against a failing test harness — 96% of attempts rejected since Tuesday.
Evidence: 1 account · 4.2M tokens/day · 96% rejection
account = 'ci-bot-7' AND rejection_rate(24h) > 0.9suspend_allocation() THEN alert(oncall)Drift: Support deflection quality declining
Support's assisted-resolution value per token has drifted -18% over 6 weeks as ticket complexity rose. Current model tier no longer fits the workload.
Evidence: 1,840 tickets · 6-week trend
team = 'Support' AND value_per_token.trend(6w) < -0.15escalate_model_tier() AND refresh(playbook = 'support-triage')72% of tuning actions execute without human review. Raise or lower this per policy category.
- Tightened verbosity guard threshold 2.8x → 2.5x
False-negative rate dropped after last week's loosening; re-tightened within approved bounds. Savings up 11% with no new false positives.
Today · 09:41 · Auto-tuned - New pattern extracted from top pairing
Dana Okafor × Opus context-staging pattern codified into playbook PB-31; candidates identified in 3 teams for propagation.
Today · 07:15 · Learned - Rolled back aggressive batch deferral
Deferral window pushed a priority-3 job past SLA. Policy reverted to previous window; incident logged and bounds narrowed.
Yesterday · 22:03 · Rolled back - Circuit breaker fired 3x for same pairing
Repeated throttling of the same pairing suggests a workload mismatch, not a usage problem. Escalated to team lead with model-fit analysis attached.
Yesterday · 14:37 · Escalated