Conversation
The README described crucible as an optimization loop and mentioned the graph only as configuration for one. The graph is the thing most runs use, and a playbook never reaches a judge at all. The loop-free claim also predates revise rounds and routed branches. The task set is still fixed at compile time, but execution over it is cyclic: a revise pair re-dispatches its proposer until the reviewer stops failing, and `when` decides at runtime whether a branch runs. Both README claims of a DAG were wrong. Adds compiled-and-checked route and revise examples, and lists the control plane crates the layout table missed. Assisted-by: Claude
This branch has not been deployed
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.
The README opened with the optimization loop and called the compiled graph a DAG. Neither is true of v0.3.0: the playbook lane runs the graph once without a judge, and
revisepluswhenmake execution cyclic over a task set that is still fixed at compile time.Lead with the graph, name the playbook and autoresearch lanes, add a routing and a revise example (both compile with
crucible plan compile-workflow), retitle the Argo/Tekton section, and add the controller, crux and capability crates to the layout table.