Bootstrap durable managed scheduling state #1

Open
opened 2026-08-24 08:51:33 +00:00 by lost-rob0t · 0 comments
lost-rob0t commented 2026-08-24 08:51:33 +00:00 (Migrated from github.com)

Task Steward reconciliation found the designated durable state/control repository empty. state/managed_github.yml and state/managed_decisions.json are absent, so current Prolog-managed scheduling cannot be proven and worker allocation must fail closed.

Acceptance:

  • bootstrap durable state artifacts in this repository without renaming or redirecting repositories;
  • encode explicit hard stops for lost-rob0t/prolog-rlm and lost-rob0t/local-recall;
  • mark evidence incomplete until a real reconciliation/prolog evaluation populates current managed GitHub evidence;
  • do not fabricate next_external or destructive keep/pause/yield decisions;
  • later replace bootstrap/unavailable state with current evidence + a real Prolog-derived decision artifact.

Because the repository has no commits/branch content yet, the initial state bootstrap may need to land directly as the repository's first commit; subsequent changes should use normal issue/branch/PR/exact-head gates.

Task Steward reconciliation found the designated durable state/control repository empty. `state/managed_github.yml` and `state/managed_decisions.json` are absent, so current Prolog-managed scheduling cannot be proven and worker allocation must fail closed. Acceptance: - bootstrap durable state artifacts in this repository without renaming or redirecting repositories; - encode explicit hard stops for `lost-rob0t/prolog-rlm` and `lost-rob0t/local-recall`; - mark evidence incomplete until a real reconciliation/prolog evaluation populates current managed GitHub evidence; - do not fabricate `next_external` or destructive keep/pause/yield decisions; - later replace bootstrap/unavailable state with current evidence + a real Prolog-derived decision artifact. Because the repository has no commits/branch content yet, the initial state bootstrap may need to land directly as the repository's first commit; subsequent changes should use normal issue/branch/PR/exact-head gates.
Sign in to join this conversation.
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
nsaspy/task-steward-rage#1
No description provided.