Semantic plan dependency in parallel execution is model judgment #160
Labels
No labels
already-shipped
bug
documentation
duplicate
enhancement
external-review
good first issue
help wanted
in progress
invalid
needs-decision
proposal
question
security
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: crenshawdev/cadence-archived#160
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Source: strict re-review C-17
Verdict: DISPUTE - by design, closing
Claim as reviewed
Parallel dependency safety partly relies on model judgment - "no plan builds on another's output" - while only file overlap is deterministic.
At HEAD
f354864(v3.3.0)Accurate and said plainly at the site:
cadence-core/workflows/execute.md:107- "no plan builds on another's output (your judgment, from the plans' goals and ordering)". The file-overlap half is explicitly labelled "arithmetic, not judgment" two lines below.Note
The split is the design: the deterministic half is a seam, the semantic half is not mechanizable from declarations. The actual defect near this - the two seams disagreeing about what a declaration means - is filed and open separately.