Publish schema format as a language-neutral spec for ecosystem tooling

[zeevdr]

Status: Raw idea — needs exploration and refinement

Idea

Today the OpenDecree schema format is defined by Go structs and proto messages. External tools (renderers, validators, UI editors, format converters) cannot consume it without going through a Go SDK. Publishing the schema format as a language-neutral spec — JSON Schema draft 2020-12, an OpenAPI-style profile, or a custom formally-versioned document — would unlock an OAS-style ecosystem where anyone can write a Python/TS/Rust renderer, a VS Code extension, or a schema-diff tool without touching Go.

Concrete example: sdk/tools/docgen is Go-only. If the schema were published as JSON Schema, someone could write an alternative Markdown/HTML/PDF renderer in their language of choice, exactly how Widdershins and Redoc coexist against the OpenAPI spec.

Open questions

• Which format? JSON Schema 2020-12, a custom spec, or an OpenAPI profile?
• How do we version the schema-of-schemas independently of the Go SDK?
• Is this in scope for core, or better as contrib/integration?
• What's the simplest useful version — just the field type system, or full schema + constraints + metadata?
• Do we wait for demand signal (someone asking "can I write a Python renderer?") before committing?

Next steps

Refine using the idea checklist, then decide if it warrants an issue.

[zeevdr]

Update: scoped into milestone Schema Spec v0.1.0 with design brief at .agents/context/schema-spec.md. 10 phased sub-issues: #118 → #127. Post your thoughts on open questions (hosting target, bundling tool, default $schema injection on export, post-v1.0.0 URL migration) in this thread.