design: IR repo should own cross-language golden wire fixtures (canonical contract for Rust Planner)

yorunikakeru commented

2026-06-11 15:37:59 +02:00

Owner

IR's reason to exist is being the stable JSON contract between Haskell and the future Rust Planner. Today the only on-disk wire artifacts are in the DSL repo (test/fixtures/*.json), and IR's own tests check Haskell-internal roundtrips only.

When the Rust side lands, serde definitions become a third independent encoding of the same contract (after Haskell ToJSON and Haskell FromJSON). Without shared fixtures, drift is detected by integration failure at runtime.

Proposal:

Move/copy canonical `intent.json` fixtures into IR repo (`fixtures/v2/*.json`), one per feature: profile+condition+observe, priorities, policies, and/not composition.
IR CI: decode each fixture, re-encode, byte-compare (golden).
Rust Planner repo consumes the same files in its serde tests.
Optionally generate a JSON Schema from the fixtures for documentation.

This makes IR the single source of truth instead of "whatever the DSL currently emits".

IR's reason to exist is being the stable JSON contract between Haskell and the future Rust Planner. Today the only on-disk wire artifacts are in the **DSL** repo (test/fixtures/*.json), and IR's own tests check Haskell-internal roundtrips only. When the Rust side lands, serde definitions become a third independent encoding of the same contract (after Haskell ToJSON and Haskell FromJSON). Without shared fixtures, drift is detected by integration failure at runtime. Proposal: 1. Move/copy canonical \`intent.json\` fixtures into IR repo (\`fixtures/v2/*.json\`), one per feature: profile+condition+observe, priorities, policies, and/not composition. 2. IR CI: decode each fixture, re-encode, byte-compare (golden). 3. Rust Planner repo consumes the same files in its serde tests. 4. Optionally generate a JSON Schema from the fixtures for documentation. This makes IR the single source of truth instead of "whatever the DSL currently emits".

yorunikakeru referenced this issue from FrogOS/Planner

2026-06-11 15:38:53 +02:00

bootstrap: Rust crate skeleton — IR v2 deserialization + contract tests against IR fixtures #1

yorunikakeru commented

2026-06-11 15:49:34 +02:00

Author

Owner

Scope update: Planner core is Haskell (GHC native lib behind FFI, Rust actor wrapper). Rust never deserializes IR - it passes intent.json as opaque bytes to the Haskell core, which uses the existing aeson instances. So fixtures here guard Haskell encode/decode stability across IR versions, not Rust serde drift. Cross-language golden fixtures are still needed, but for SystemState and Plan - they belong in the Planner repo (see FrogOS/planner#1).

Rows
Columns

design: IR repo should own cross-language golden wire fixtures (canonical contract for Rust Planner) #4