refactor(routing): address code review feedback - simplify list filter, fix docs example

Co-authored-by: christianlouis <361235+christianlouis@users.noreply.github.com>
2026-03-09 23:38:25 +00:00
parent e95693d684
commit 1e5e35a26a
2 changed files with 15 additions and 12 deletions
@@ -662,13 +662,18 @@ based on their properties — no manual pipeline selection required.
 | `regex` | Full Python regex match (case-insensitive) |
 | `gt` / `lt` / `gte` / `lte` | Numeric comparison (greater/less than) |

-**Example:** Route all invoices over 1 MB to a dedicated pipeline:
+**Example:** Route invoices to one pipeline and large files to another:

 ```
 Rule 1: field=document_type, operator=equals, value=Invoice, target_pipeline=3
 Rule 2: field=size,          operator=gt,     value=1048576, target_pipeline=5
 ```

+With first-match-wins logic, an invoice of any size matches Rule 1 and is
+routed to pipeline 3.  A non-invoice file larger than 1 MB matches Rule 2
+and is routed to pipeline 5.  Everything else falls back to the default
+pipeline.
+
 You can test your rules without actually routing a document using the
 **evaluate** endpoint (`POST /api/routing-rules/evaluate`).  For the full
 API reference, see [API Documentation](API.md#routing-rules).