RhoeJSON

Swift-native JSON engine, CLI, preview daemon, jq-inspired filters, binary codecs, and WASM facade.

RhoeJSON Public Release Strategy

Status: Phase 25 Sprint 4 QA hardening Target repository: RhoePlatform/RhoeJSON Target release: 0.1.0 License: Apache 2.0

RhoeJSON is the public Swift JSON engine in the RhoePlatform foundation line. The first release should feel complete for contributors who want a JSON library, CLI, browser preview, and WASM-friendly facade, while staying deliberately narrow enough to maintain a clean public boundary.

Release Positioning

The 0.1.0 release is an engine-first release, not a broad platform release. It should give users a practical JSON toolchain:

Public Package Surface

The first public wave includes:

The primary CLI identity is rhoejson. Homebrew aliases are planned as rhoejn and json.

Deferred Surface

The following areas stay outside 0.1.0 until they have explicit public contracts:

CLI Strategy

The CLI should be familiar to users of tools such as jq and jj, without claiming language compatibility with either. The public command families are:

The preview command is the interactive entry point:


rhoejson preview data.json -o /demo
rhoejson preview data.json --schema schema.json --route /validated --no-open

On macOS, rhoejson preview may launch rhoejson-preview-menu by default. Linux remains CLI-only.

The jq command supports the practical subset needed for common inspection and projection tasks:

Forward references between user-defined filters are available as a RhoeJSON-inspired extension, but they are not exact jq-compatible. Full jq language compatibility is deferred. Modules, label/break, broader regex replacement streams, Unicode normalization edge-case documentation beyond scalar code point conversion, jq streaming semantics, date/time, and environment or side-effect builtins such as env, $ENV, debug, and stderr are not part of 0.1.0. Raw environment exposure is deliberately deferred because public CLI environments frequently contain secrets. The staged compatibility roadmap is tracked in Documentation/Compatibility/JQCompatibilityRoadmap.md, with pinned subset cases under Tests/RhoeJSONFilterTests/Fixtures/jq-conformance/.

Preview Strategy

The preview server should remain dependency-free on the browser side. The HTML surface should provide:

The daemon control API is intentionally local and narrow. It is not a general HTTP API server for the engine.

Documentation Strategy

The public repo should include:

Documentation should describe what the release supports today and mark deferred features explicitly. It must not require users to know the history of the staging process.

Release Gates

The staging folder remains source-only until these gates pass:

Platform Boundary

The JSONSchemaAIGenerator source file must remain guarded by:


#if os(macOS) && canImport(FoundationModels)

This keeps the API available to macOS developers with Apple Intelligence support while preventing Linux CI and Linux package artifacts from compiling or exposing Apple-only symbols.

Only after these gates pass should the public repository be initialized, committed once, pushed privately, enabled for CI and Pages, and then switched public after the final audit.