Repository navigation
docs: screen candidate runtime-worker context policy - #1181
Open
seathatflowsinourveins wants to merge 2 commits into
Open
seathatflowsinourveins wants to merge 2 commits into
seathatflowsinourveins wants to merge 2 commits into
Conversation
5 tasks done
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
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.
Scope
Screen a candidate context policy for a future TRIAL on Pi, OpenCode, fenced Muse and Claude Code workers: retain vendor compaction thresholds, propose a bounded current-state note and explicit handoffs at task boundaries. Record one unrun comparison of native resume versus a fresh worker within an unfinished task, with missing driver/fixture custody named as readiness inputs.
The 2026-10-15 20:48Z convergence correction is recorded in protocol.md (source record sha256 c75fd83da2664e94ff3064ff9d938ac36b9bde85a733803c3f0ebe4b6d98455c). Lead-note fields, size budgets, update conventions and relaunch heuristics are explicitly CANDIDATES, not requirements selected by CC design. The withdrawn 20:45Z definition is not a source of adoption authority. The paired experiment holds note conventions equal and tests history continuity only; it cannot qualify their exact format or budgets.
8053f14e7e0817d2502dff2bb284bfb7e1b0152flane:foundationevidence/artifacts/runtime-worker-context-engineering-20261015/and its six registrations inmanifests/evidence.json.Research only. No installs, inference, Muse invocation, configuration/default/fence changes, catalog/ledger/research-state changes or comparison execution. Command-center context and orchestration rows remain out of scope.
SOTA sources
04566631c2b51fb688486bc1f040f60d1518c126(1.1.0),packages/coding-agent/docs/{compaction,sessions,settings,configuration,rpc-commands}.md: native thresholds, structured summaries, session identity and accounting. Same-version installed documentation drift is explicitly retained.53d1eabb61e21162157817bf677da0a4ad3332e3(qualified 1.18.35),packages/opencode/src/session/{overflow,compaction,llm}.ts, core summary template and vendor CLI/rules docs. Shared installed 2.0.27 is recorded as drift, not silently substituted.2026-10-14-muse-file-fence.mdand2026-10-15-muse-toolchain-directory-grants.md. Dated public docs do not prove behavior at native 1.4.7-R6101.1; numeric thresholds and telemetry completeness remain gaps.03b5892ee77de289bcd5dfa39f541525ade74aff:CHANGELOG.md, relevant 2.1.296–2.1.301 changes; vendor documentation for context-window, settings, memory, hooks, subagents, CLI and monitoring, read 2026-10-15. The installed 2.1.301 version is distinct from the practice skill's 2.1.295 record.survivors.md; Agent Console's inaccessible retained pin is a named gap. No vendor benchmark claim is treated as a measured worker saving.8b28bbda7dca372baa8026ca0bc6dce21b5b5626; existing native-practice planning_2b public result and hash-verified private custody references, named without host paths.Evidence-class table
mechanisms.md,survivors.md; 33 pinned source files/line targets checked, no unresolved citation errorsprotocol.md; verdict/wave/sweep hashes checked; 5 token, 8 memory and 1 skills survivors retainedpolicy-trial.md,comparison.md; no quality parity or savings claimhost_receipts.register_filefor six files;python3 scripts/validate.pypassesLocal commands run
Source/relative-link checks returned 33 verified pinned files, no unresolved targets and no host-home literals. Six files are registered through the existing
host_receipts.register_fileAPI. No new Python script or source-policy grant is needed. The final validation was run after the last source correction and registration.Normal push also passed the repository's pre-push host-name scan, three registry coverage checks and published-digest privacy check.
Decision record
evidence/artifacts/runtime-worker-context-engineering-20261015/policy-trial.mdis a candidate design for trial, not an adoption decision.comparison.mdfixes the rule for the single unrun experiment, without making its controls production requirements.protocol.mdrecords the convergence correction, corrects the supplied workers-angle description to its actual two INSUFFICIENT verdicts and distinguishes current native binaries from qualified profile pins.The existing paired-run driver and sealed F5/F6 fixture manifest are missing custody inputs owned by cc-native-practice. The co-op confirmed their absence in the prior run directory. This PR supplies no invented execution command or replacement fixture.
Host evidence
No
evidence/hosts/receipt or platform status change.Checklist