Starting OSIRIS JSON Toolbox core development

After drafting the Architecture Development Guidelines, it’s time to start writing the core foundation. OSIRIS JSON Toolbox core, CLI and SDK, the foundation for validation, producers and editor integrations.

This is the moment where OSIRIS JSON moves from “spec and schema” into something developers can actually use in their daily workflows: validate generated OSIRIS documents, produce deterministic snapshots, and integrate OSIRIS into CI/CD and editor tooling.

The plan is simple:

• Build @osirisjson/core first the foundation baseline
• Then @osirisjson/cli the user-facing orchestration layer
• Then @osirisjson/sdk types and helpers with ergonomics for tooling and integrations

Core and CLI are the critical path. SDK can follow right after.

Why core first and what core really means

OSIRIS JSON is not “just a schema”. If you want reliable infrastructure snapshots, you need more than JSON Schema validation.

@osirisjson/core will implement the OSIRIS Toolbox validation engine and the foundation layers that every other component depends on. Core is the engine. It should be boring, deterministic and trusted.

More soon with code, not promises.