Public-claim checks
Automated checks cover public claims, canonical repository links, package alignment, and README/website consistency.
Release · v0.10.2
Launch-execution hardening for a truthful public preview
v0.10.2 focuses on making the public surface executable, testable, and aligned with the actual security boundary rather than adding a new product category.
What v0.10.2 adds
Executable quickstart
The documented quickstart is tested for its expected decisions and local evidence creation.
Minimal tested SDK example
A runnable Node.js createRuleOak() example demonstrates a guarded function boundary.
Compatibility matrix
Fixture-tested paths are separated from independent real-world integration reports and from explicit non-claims.
Release-candidate workflow
A non-publishing workflow produces npm tarballs, SHA-256 checksums, and a machine-readable manifest.
Boundary clarification
protect guards supported routed tool-call traffic; it does not inspect arbitrary child-process internals.
Capabilities carried forward from v0.10.0–v0.10.1
- High-level
createRuleOak()SDK runtime and guarded tool/function wrappers - Structured deny and approval-required errors with decision/evidence metadata
- MCP Streamable HTTP gateway with supported SSE pass-through
- Optional loopback REST authorization API
- Policy-pack recommendation, learning mode, guided authoring, migration, linting, and tests
- Safe 60-second demo and clean-consumer npm package smoke tests
- Built-in policy packs included in the published CLI package
Public-preview status
RuleOak remains pre-1.0 software. Security-sensitive behavior and APIs may change between minor versions. The project does not claim OS containment, universal MCP compatibility, complete prompt-injection prevention, or tamper-proof local storage.