docs(kickoff): FRS S1-S3 stage kickoffs + PMCB F5 ratified — parallel aif dispatch prep - #1480
Merged
Merged
Conversation
…MCB F5 ratified (narrow the claim) + B1 done marker
Three stage kickoffs under frontier-residue-sweep-s{1,2,3}/ so each stage
dispatches as its own aif task (dispatch.ts dedups by kickoff content hash;
one file = one task). Each carries the §4c park-don't-guess contract, the
host-verify acceptance block, T-enumeration + domain traps, and URL-form PR
citations (dup-detect signal).
pre-merge-carrier-build/kickoff.md: F5 row records the operator's 2026-08-18
fork answer (narrow the INSTALL-FOR-AI claim; lane runners stay; non-npm
delivery is trigger-gated) with the fingerprint measurement backing it; B1 row
gains the MERGED marker + the §1b park contract for autonomous B2 dispatch.
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
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.
Stage kickoffs for parallel autonomous dispatch of frontier-residue-sweep S1/S2/S3 (one aif task per kickoff — dispatch.ts dedups by content hash), plus the pre-merge-carrier-build kickoff amendment: F5 ratified by the operator 2026-08-18 (narrow the INSTALL-FOR-AI «every profile» claim; measured: python/go/cargo greenfield fingerprints carry 38/3/5 lines and zero scripts/ entries vs 184-196 on npm lanes), B1 row gains its MERGED marker (frontier.sh now emits FRONTIER: B2 B3), and both umbrellas gain the §4c park-dont-guess contract required for aif dispatch.
§1.7 Forward-check applied
Checked the dispatch-input disciplines this PR touches: kickoff content gates and channel rules.
kickoff-staging-placement.md— this PR IS the merge-to-staging step that must precede dispatch; no dispatch happens before it lands. file:line evidence:.claude/rules/kickoff-staging-placement.md:20destination-environment-verification.md— all three stage kickoffs declarehost-verifyfenced contracts;scripts/host-verify.sh --listexits 0 on each. file:line evidence:.claude/orchestrator-prompts/frontier-residue-sweep-s1/kickoff.md:79ai-laziness-traps.md §3— each kickoff enumerates active T-numbers + 2 domain traps (T-FRS1-A/B, T-FRS2-A/B, T-FRS3-A/B); principle 12 suite 9/9 green. file:line evidence:.claude/orchestrator-prompts/frontier-residue-sweep-s2/kickoff.md:62build-first-reuse-default.md— no new capability: kickoffs are dispatch inputs (docs); the PMCB F5 verdict REJECTS building non-npm delivery until first live demand.no-paid-llm-in-ci.md— no CI change, no LLM calls.§1.7 Backward-check applied
Class of this change: dispatch-input kickoffs authored for aif autonomous dispatch. Swept the sibling surfaces where the same class lives.
.claude/orchestrator-prompts/frontier-residue-sweep/kickoff.md— the umbrella kickoff stays the scope SSOT; stage kickoffs quote its rows verbatim and link back, no scope fork. file:line evidence:.claude/orchestrator-prompts/frontier-residue-sweep-s1/kickoff.md:12.claude/orchestrator-prompts/pre-merge-carrier-build/kickoff.md— sibling dispatch input under the same aif-dispatch class: gained the same §4c park block (it had none — grep for «park it as a question» returned 0 before this PR) + F5 + B1 marker. file:line evidence:.claude/orchestrator-prompts/pre-merge-carrier-build/kickoff.md:53dup-detect.shhash-number signal — all PR references in the new/edited kickoff rows use the URL form so the umbrellas stay visible to /pipeline (the frontier-residue-sweep discoverability incident class). file:line evidence:.claude/orchestrator-prompts/frontier-residue-sweep-s3/kickoff.md:17frontier.shmarker layer — B1 marker written in the documentedMERGED + evidence-within-60-charsgrammar; verified by a local frontier run emittingdone=yes basis=marker-unverified+ the ATTN line, with the §6 gh check (merged PR) as the actual authority.Fidelity verdict
FIDELITY: skipped — docs-only dispatch-input kickoffs + kickoff amendment; no dispatched-worker substrate, no shipped-artifact diff to audit.