Starting OSIRIS JSON Toolbox Core Development

After drafting the Architecture Development Guidelines, it is time to start writing the code. We are beginning development on the OSIRIS JSON Toolboxthe foundation that will power our validation engines, CLI utilities, SDK integrations, and editor plugins.

This is the moment where OSIRIS JSON transitions from a conceptual “spec and schema” into concrete tools that developers can run in their daily workflows: validating topology documents, producing deterministic infrastructure snapshots, and integrating validation checks directly into CI/CD pipelines.

The roadmap is simple:

• Build @osirisjson/core first: The foundation validation and parse engine.
• Build @osirisjson/cli second: The user-facing command-line tool.
• Build @osirisjson/sdk third: Helper functions, typescript definitions, and ergonomics for third-party integrations.

The core validation engine and the CLI are on the critical path. The SDK and library wrappers will follow immediately after.

---

Why core first?

OSIRIS JSON is more than just a JSON Schema file. If you want reliable, production-grade infrastructure snapshots, standard JSON Schema validation isn’t enough. You need semantic checks to ensure logical consistency:

• Are there isolated nodes that violate network topology layouts?
• Are relationship edges pointing to entities that don’t exist in the snapshot?
• Are IP assignments structurally valid within their defined subnets?

@osirisjson/core will implement this semantic validation engine. Because it sits at the bottom of the dependency stack, it needs to be boring, deterministic, heavily tested, and completely trusted.

More soonwith real code, not slides or promises.