spec: IR wire example in README outdated vs IR v2 #1

Open
opened 2026-06-11 15:36:24 +02:00 by yorunikakeru · 0 comments
Owner

README architecture spec shows an IR example that no longer matches what the DSL/IR actually emit:

  • `"version": "1"` as a string; `IR.Types` serializes `IRVersion` as a JSON number and current version is `2`.
  • Service actions now always carry `priority` (IR.Domain.Service emits it unconditionally); example omits it.
  • `ServiceSection` serializer has no `omitNothingFields`, so services always emit `"actions": []`; example shows a service with policies only.

The README is presented as the stable wire contract for the Rust Planner — an outdated example is worse than none. Regenerate the example from a real `compile` run, and consider CI that diffs the README example against a golden fixture.

README architecture spec shows an IR example that no longer matches what the DSL/IR actually emit: - \`"version": "1"\` as a **string**; \`IR.Types\` serializes \`IRVersion\` as a JSON **number** and current version is \`2\`. - Service actions now always carry \`priority\` (IR.Domain.Service emits it unconditionally); example omits it. - \`ServiceSection\` serializer has no \`omitNothingFields\`, so services always emit \`"actions": []\`; example shows a service with policies only. The README is presented as the stable wire contract for the Rust Planner — an outdated example is worse than none. Regenerate the example from a real \`compile\` run, and consider CI that diffs the README example against a golden fixture.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
FrogOS/spec#1
No description provided.