refactor(acm): perfect dao-shu guidance — unconstrained Composer synthesis#11
Closed
KorenKrita wants to merge 3 commits into
Closed
refactor(acm): perfect dao-shu guidance — unconstrained Composer synthesis#11KorenKrita wants to merge 3 commits into
KorenKrita wants to merge 3 commits into
Conversation
This was referenced Jul 16, 2026
Owner
Author
|
Superseded by #12 (chosen merge target for ACM dao-shu guidance). Closing this alternative. |
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
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.
Summary
Unconstrained always-on ACM guidance: everything retained from #6–#9 when token budget is not the limiting factor (~9304 chars vs ~8500 lean ultimate).
What this adds over #8/#9
keep live what NEXT needs+ recoverable handoff +NEXTexecutableagainst this invarianteverywhere it matterswithout rereading archived summariesrestoredUnchanged good choices
handoff working setcueStructure
vs lean ultimates
Recommend for users/models where ~800 extra always-on tokens are acceptable. For strict budget, prefer #9.
Test plan
bun run verify:acmSupersedes
Optional merge target; lean production may still prefer #9. Closes the design exploration from #2–#8.
Worktree:
../pi-context-perfect