Changelog

The engine changes in this entry ship with @ordo-engine/cli 0.6.1 and 0.7.0.

Engine

• New decimal type for exact money math, with no floating point drift. Numeric equality, division and round(x, n) were fixed along the way.
• A ruleset can declare an inputSchema. Missing or mistyped input fields return 400 INVALID_INPUT instead of quietly taking the wrong branch.
• Assignments and outputs accept expression strings, such as "price * qty".
• New decision_table step. hitPolicy supports first (first matching row) and collect (every matching row, optionally reduced with sum, count, min or max).

CLI

• ordo impact <ruleset> runs your working copy next to the last version in git, over test cases, real inputs you provide and probe inputs generated on both sides of every threshold, and lists the inputs whose result changed. Supports --json and --fail-on-change.
• ordo mcp gains an impact tool, so coding agents can check the effect of their own rule edits.
• ordo guard upgrade brings Guard policies scaffolded by older versions up to the current default policy.

Rule packs

• New examples/rule-packs/ in the repository: credit approval, promo stacking and fraud scoring. Each is a complete Ordo project with tests that runs with ordo test.

Covers engine 0.5.0 to 0.5.2 and CLI 0.5.0 to 0.6.0.

New

• ordo guard: every command a coding agent wants to run goes through your local rules first, and is allowed, denied, or sent to you to decide. Works with Claude Code, Codex CLI and Cursor. The policy is an Ordo project with tests.
• ordo replay: replay recorded real decisions against a rule change and see which results move.
• Optional input and output capture on the server (--capture-io-path) to feed replay.
• Execution analytics: the engine reports execution stats, and Studio shows decision volume, outcomes and latency.
• Share a ruleset from the playground by URL.

Fixes

• Release flow on the platform: rollback, concurrent rollouts, crash recovery and re-inlining sub-rules.
• Cross-organization data isolation gaps.
• Several Studio states that could lose unsaved work or show misleading status.

New Features

• Platform Studio: New visual workbench with Catalog, Contracts, Templates, Version History (M1.1) and test backend (M1.2)
• Flow Editor: Vue component refactor, i18n support, build config optimization
• CLI Tools: New eval, exec, test subcommands
• Rule Testing Framework: Server-side API support, create and run tests in Studio
• 50+ Extended Built-in Functions: Merged in two batches (#48, #52)
• Rule Composition: CallRuleSet Action and Pipeline API for cross-ruleset invocation
• Python SDK: HTTP/gRPC dual-protocol support
• gRPC TLS/mTLS: Secure communication support
• Webhook Notifications: Rule change event push
• External Reference Data Store: Runtime loading of external data sources
• Write-Ahead Logging: Crash-safe rule persistence
• NATS JetStream Sync: Distributed deployment support
• Store Resource Limits: max_rules_per_tenant, max_total_rules
• Hot Reload Enhancement: Self-write suppression and Admin API

Performance

• HTTP serialization optimization, reduced lock contention

Testing

• Complete HTTP API integration test coverage

Engineering

• DevContainer, Docker Compose, and project toolchain
• Structured CHANGELOG based on git-cliff

Fixes

• Fixed decision table decompilation issue
• Docker build pipeline fix

New Features

• Cranelift JIT Compilation: Compiles numerical rules to native machine code, achieving 20-30x performance improvement in compute-intensive scenarios

Performance

• Rule engine CPU efficiency optimization, reduced hot path overhead

Improvements

• Fixed Clippy warnings
• Enhanced pre-commit hooks

New Features

• Implemented MetricSink trait for custom rule metrics collection and integration

New Features

• Core Rule Engine: Built with Rust, supports Decision, Action, Terminal, and other node types
• HTTP API Server: RESTful interface for ruleset CRUD and execution
• Expression Engine: C-like syntax with math, logic operators, and built-in functions
• Execution Tracing: Detailed decision path tracing for debugging