feat(framework): run a build under an Open Loop domain preset (#251)#253
Merged
Merged
Conversation
runFramework({ preset, modes }): the preset's skills frame every phase, the
domain + modes are narrated, and its loops + prompts are materialized into a
driver-backed LoopEngine exposed as result.loop (new driverLoopPrompts bridge).
Opt-in; a run without a preset is unchanged. Driving the loop as a phase is #252.
Closes #251
suleimansh
added
enhancement
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Phase 2 of Open Loop (#204): make a framework run actually consume a domain preset from the first slice.
runFramework({ preset, modes }):LoopEngine(each pass = a freshDriverSession.prompt, matching the driver contract) and exposed asresult.loop. NewdriverLoopPromptsbridge.Opt-in and additive: a run with no preset is byte-for-byte unchanged.
Deliberately deferred (open decision for you, @brillout): I did NOT auto-run the domain loop as a phase, because where it sits relative to Bootstrap's production-grade checklist loop is a product call (replace it? run after as a domain review? interleave?). Filed as #252. This PR exposes the materialized loop so a caller can drive it; #252 decides placement.
95 framework tests (3 new: framing, driver-backed chain runs, no-preset stays clean). Typecheck green across 21 projects. Changeset: minor.
Closes #251