Fresh workers and clears reread unchanged canonical artifacts #154
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#154
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-01
Verdict: DISPUTE - by design, closing
Claim as reviewed
The disposable-worker and clear-then-reconstruct strategy systematically rereads unchanged project artifacts, consuming context and tokens where a more sophisticated state layer could avoid reinjecting unchanged material.
At HEAD
f354864(v3.3.0)Accurate as a description.
cadence-core/workflows/execute.mdhas every plan in a phase reread the shared set; the README recommends/clearbetween commands.Note
This is the architecture, not a defect in it: durable state read back from files is what makes continuity survive a cleared conversation. Reducing repeated ingestion is already an active, separately tracked line of work with its own ledger.
Closed as a finding; the cost work continues on its own track.