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

spec: contradiction — who resolves policies, Planner or Executor #2

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

Spec says: "Planner — единственный кто думает" and "Executor — только делает... не знает контекста, не знает плана".

But `IR.Policy` haddock (IR repo) says a policy is "a decision space delegated to the Executor — the Executor resolves it against observed runtime state."

These cannot both be true. Resolving `fallback(port 5432, [5433, 5434])` requires observing port availability and making a choice — that is "thinking". Either:

  1. Planner resolves policies using state from Watcher (Executor stays context-free), or
  2. Executor gets a constrained decision capability (spec's actor separation must be rewritten).

Related question the spec is silent on: who observes port availability at all — Watcher only watches /proc/udev events in the spec. Decision blocks Planner bootstrap.

Spec says: "Planner — единственный кто думает" and "Executor — только делает... не знает контекста, не знает плана". But \`IR.Policy\` haddock (IR repo) says a policy is "a decision space **delegated to the Executor** — the Executor resolves it against observed runtime state." These cannot both be true. Resolving \`fallback(port 5432, [5433, 5434])\` requires observing port availability and making a choice — that is "thinking". Either: 1. Planner resolves policies using state from Watcher (Executor stays context-free), or 2. Executor gets a constrained decision capability (spec's actor separation must be rewritten). Related question the spec is silent on: **who observes port availability at all** — Watcher only watches /proc/udev events in the spec. Decision blocks Planner bootstrap.
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#2
No description provided.