EngineeringFeatured
What should we measure before enforcing a policy?
A high agreement rate in shadow mode is not enough. Diverging requests, missing signals and rollback conditions need to be reviewed together.
3 min read
Read the story
Modelion / Engineering journal
What happens inside the gateway
Engineering notes on the policy engine, routing and guardrails. Not product announcements; the reasoning behind decisions we made, and the walls we hit along the way.
Latest posts
6 posts found
Product
Why a budget limit is different from a cost report
Reporting spend after the fact and deciding whether a call may start are different jobs. Estimates, concurrency and actual usage need separate treatment.
3 min read
Modelion Engineering
Engineering
How do you explain why a request reached that model?
A model name describes the outcome, not the reason. Read a decision trace from input signals through the winning rule to enforcement obligations.
3 min read
Modelion Engineering
Architecture
Why we stop switching models once streaming begins
Once the first response chunk reaches the user, retrying means something different. The boundary between a partial answer, a failure and a new attempt.
3 min read
Modelion Engineering
Architecture
Why prompt hydration runs before policy
PII arrives inside the variables, not inside the template. That single observation fixes the entire stage ordering in the gateway.
2 min read
Modelion Engineering
Compliance
Failover is a hole in the compliance path
A fallback chain normally buys you resilience. While a residency rule is in force it does the opposite — and it does it silently.
3 min read
Modelion Engineering
Engineering
Moving the policy decision out of code
When model selection, redaction and refusal logic is spread through application code, two things break together. What changes when the decision lives in one place.
3 min read
Modelion Engineering