You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit dd10c9a
Browse filesBrowse the repository at this point in the historyBrowse files
|`limits?`| object | — | Hard limits, e.g. `maxEstimatedCostUsd`. |
106
+
|`limits?`| object | — | Hard limits, e.g. `maxEstimatedCostUsd` (enforced by the dry-run evaluator when candidate cost evidence is known). |
105
107
|`unknownEvidence?`| object | capability `exclude`, health/quota/cost `penalize`| How unknown evidence is treated per dimension: `allow`, `penalize`, or `exclude`. Unknown never becomes zero. |
106
108
107
109
`require` supports: `minContextWindow` (positive integer), and the booleans `tools`, `imageInput`,
@@ -112,6 +114,9 @@ Request evidence supplied to a dry-run (context window, tools, image input, stru
112
114
reasoning effort, service tier, encrypted Codex tasks) is evaluated against candidate capabilities
113
115
together with the profile `require` block; a candidate must satisfy both to be eligible.
114
116
117
+
The CLI dry-run accepts request-evidence flags but cannot supply candidate capability evidence yet;
118
+
candidate evidence is provided through the API (`POST /api/routing-profiles/dry-run`).
119
+
115
120
```json
116
121
{
117
122
"routingProfiles": {
@@ -147,8 +152,8 @@ without sending any upstream request.
147
152
requirements filter first, then deterministic scoring ranks the survivors.
148
153
149
154
Both are virtual namespaces with aliases and collision validation; they differ in *how* a candidate
150
-
is chosen. Profile scoring expands in capability (RI-05), health (RI-06), quota (RI-07), and cost
151
-
(RI-08) dimensions, each recorded in the per-request route-decision trace.
155
+
is chosen. Profile scoring will expand with capability (RI-05), health (RI-06), quota (RI-07), and
156
+
cost (RI-08) dimensions; per-request trace recording arrives with execution (RI-05).
0 commit comments