Skip to content

#87: Pin immutable Research Execution Profiles - #157

Draft
justsml wants to merge 5 commits into
dan/issue-89-workspace-skillsfrom
dan/issue-87-execution-profile
Draft

#87: Pin immutable Research Execution Profiles#157
justsml wants to merge 5 commits into
dan/issue-89-workspace-skillsfrom
dan/issue-87-execution-profile

Conversation

@justsml

@justsml justsml commented Aug 27, 2026

Copy link
Copy Markdown
Owner

Split from the Wayfinder mega PR #137.

Refs #87

Scope

  • Resolve, persist, and propagate immutable model, capability, skill, target, network, budget, UI, and policy selections.

Review notes

This PR is intentionally ticket-scoped. It does not close the referenced issue unless the issue is already complete; CI provides the final integration check.

@justsml justsml mentioned this pull request Aug 27, 2026
19 tasks
@justsml

justsml commented Aug 27, 2026

Copy link
Copy Markdown
Owner Author

Council of Dans review: repair/defer. Highest-priority gate: Restack off the closed #156 implementation and rebuild on native bounded Workspace search; then prove requested/effective profile propagation without no-op controller cost. Feature flags are not a substitute for authority, evidence-integrity, or durability fixes; use typed modes only where they provide a real rollout boundary.

@justsml
justsml marked this pull request as draft August 30, 2026 23:23
@justsml

justsml commented Aug 30, 2026

Copy link
Copy Markdown
Owner Author

Council hard-stop update after 3 review-and-repair loops:

Pushed 34abcc78e and a5c232a46. The PR is now draft because central immutability blockers remain.

Resolved:

  • exact run/profile lookup for background work;
  • full authority-free profile projection;
  • full model URI/provider-option gateway;
  • pinned skill bodies and server-owned handoff profile;
  • public drain route no longer accepts grants;
  • persisted-first resume and expanded profile propagation;
  • 47 focused integration checks, typecheck, and formatting pass.

Remaining P1 blockers:

  1. production target config still prefers the fresh nested thread workspace over the pinned profile;
  2. scheduler claims are project/thread-wide and can claim another run/profile task before rejecting it;
  3. the exported background boundary still accepts/persists caller approval grants;
  4. remote stages lose the pinned compute target ID;
  5. arbitrary nonexistent model IDs on supported providers still publish.

P2: enforce run/profile custody for parent handoffs and add a production Controller option propagation test.

Per the three-loop stop rule, this PR is parked and remains open as a draft.

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