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

spec: undefined semantics — default observe strategy, mixed strategies, policies-in-profiles #3

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

IR allows constructs whose runtime meaning the spec never defines:

  1. `observe` is optional on every condition (`Maybe ObserveStrategy`). What does the Watcher do when it's absent? Default poll interval? Event-driven? Reject?
  2. `and`/`not` compose conditions whose leaves may carry different strategies (DSL `via` overrides all leaves, but `(<&&>)` of two independently-observed conditions is legal). When is the composite re-evaluated?
  3. `ProfileSection` has `policies` and `ServiceSection` has `actions` (IR.Types), but the spec only describes profile-actions and service-policies. What does a policy scoped to a profile mean? An unconditional action in a service section?

Each of these is representable on the wire today, so the Planner/Watcher will have to invent semantics ad hoc. Spec should define or forbid them (and the IR should stop representing the forbidden ones).

IR allows constructs whose runtime meaning the spec never defines: 1. \`observe\` is optional on every condition (\`Maybe ObserveStrategy\`). What does the Watcher do when it's absent? Default poll interval? Event-driven? Reject? 2. \`and\`/\`not\` compose conditions whose leaves may carry **different** strategies (DSL \`via\` overrides all leaves, but \`(<&&>)\` of two independently-observed conditions is legal). When is the composite re-evaluated? 3. \`ProfileSection\` has \`policies\` and \`ServiceSection\` has \`actions\` (IR.Types), but the spec only describes profile-actions and service-policies. What does a policy scoped to a profile mean? An unconditional action in a service section? Each of these is representable on the wire today, so the Planner/Watcher will have to invent semantics ad hoc. Spec should define or forbid them (and the IR should stop representing the forbidden ones).
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#3
No description provided.