FrogOS/spec
1
0
Fork 0
Code Issues 5 Pull requests Projects Releases Packages Wiki Activity Actions

spec: version-mismatch-reject contradicts atomic rollback to old generations #4

New issue
Open
opened 2026-06-11 15:37:08 +02:00 by yorunikakeru · 0 comments
yorunikakeru commented 2026-06-11 15:37:08 +02:00
Owner
Copy link

`IR.Types.IRVersion` doc: "A version mismatch causes the engine to reject the document and roll back." Spec sells rollback as an atomic symlink flip to any older generation.

Contradiction: gen-41 was written by an older DSL with IR version N-1. After upgrading the engine (which now requires version N), rolling back to gen-41 means re-reading an `intent.json` the engine rejects by policy. Worst case: a bad deploy of gen-42 cannot be rolled back because every prior generation is "version mismatch".

Spec needs a compatibility story:

  • a supported version window (engine reads versions [K..N]), or
  • migration of archived intent.json on upgrade, or
  • rollback that bypasses IR re-parsing entirely (symlink flip without replanning — but then reconciliation loop can't run against the restored intent).

Also note the IR already de facto uses a second compat mechanism (priority defaults to 100 when absent in FromJSON) — pick one strategy.

\`IR.Types.IRVersion\` doc: "A version mismatch causes the engine to reject the document and roll back." Spec sells rollback as an atomic symlink flip to any older generation. Contradiction: gen-41 was written by an older DSL with IR version N-1. After upgrading the engine (which now requires version N), rolling back to gen-41 means re-reading an \`intent.json\` the engine **rejects by policy**. Worst case: a bad deploy of gen-42 cannot be rolled back because every prior generation is "version mismatch". Spec needs a compatibility story: - a supported version window (engine reads versions [K..N]), or - migration of archived intent.json on upgrade, or - rollback that bypasses IR re-parsing entirely (symlink flip without replanning — but then reconciliation loop can't run against the restored intent). Also note the IR already de facto uses a second compat mechanism (priority defaults to 100 when absent in FromJSON) — pick one strategy.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#4
No description provided.