docs(dag): 'one objective, one live DAG' downgraded from Invariant to Convention - #373
Merged
Conversation
… Convention CONTEXT.md claimed an engine-enforced invariant; the implementation is orchestrator guidance only (dag.create and the tool start accept a session with a live workflow; the wake model and lease tolerate multiples). The divergence was the defect (audit INV-A) — this records the truth: a modeling convention with documented bounded consequences, including the cross-workflow write-set caveat. Engine enforcement remains available as a future decision if the convention proves insufficient. Closes#348
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 freeto 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.
Closes#348
Decision (option b — record the truth)
CONTEXT.md's Invariant list claimed "one user objective has at most one live DAG" as an engine guarantee. The implementation is orchestrator guidance (workflow-routing.md / orchestration-policy.md);
dag.createand the workflow tool's start accept a session that already has a live workflow, nothing cross-process rejects a second one.The divergence was the defect. This PR moves the statement to a new Conventions section with the honest framing:
Option (a) — engine enforcement — remains a possible future decision if the convention proves insufficient; nothing here forecloses it.
Docs-only change; no runtime code touched.