Skip to content

Restore authoritative Opsle program control - #22

Merged
sneakocom merged 1 commit into
mainfrom
chore/reconcile-program-control
Sep 5, 2026
Merged

sneakocom merged 1 commit into
mainfrom
chore/reconcile-program-control

Conversation

@sneakocom

Copy link
Copy Markdown
Contributor

Outcome

Restores opsle/research as the authoritative control plane for the 21-repository Opsle program.

  • makes program/registry.json the single machine authority for portfolio and NOW / NEXT / THEN / LATER / PARKED priority state
  • makes Durable Supervisor v0.1 the bounded NOW objective and Opsle Tasks the gated NEXT workload
  • records ten explicit DS v0.1 stopping criteria, the anti-nitpick admission rule, evidence-triggered concept activation, parked work, and the Visible Value receipt/summary target
  • renders both PROGRAM_STATUS.md and program/PRIORITY.md deterministically from the registry
  • reconciles live organization HEADs, promotes Durable Supervisor from stale THEORY to evidence-bounded VERIFIED, and moves speculative concept tasks to workload-triggered waiting
  • preserves all 21 repositories exactly once and all five experiment records
  • preserves the Taslos Tasks no-move/no-transfer/no-rename/no-release/no-provider boundary

Verified reconciliation

Validation

  • python3 tools/validate_program.py: PASS, 21 repositories / 18 concepts / 5 experiments
  • unit tests: PASS, 100/100
  • EXP-001 offline qualification: PASS, 6 tasks / 48 provider-free renderings / 0 experiment runs / 0 provider-model runs
  • five captured Visible Value receipts: PASS
  • generated status and priority consistency: PASS
  • live GitHub inventory parity: PASS
  • actionlint: PASS
  • gitleaks: PASS
  • git diff --check: PASS

Boundaries

Only opsle/research changed. No provider/model subject, production mutation, deployment, Taslos/Opsle Tasks migration, DNS/TLS change, or other repository implementation was performed.

@sneakocom
sneakocom merged commit 98b4b9d into main Sep 5, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant