--- name: mc-vf-move-v17 description: "Run Move-level acceptance verification for a CANONQ-NATIVE v1.7 Mission: the aggregate gate ahead of closure. Reads every governed artifact's verification and approval state from the VF ledger and the tracked table, runs mc17 check including the landed-IP-without-IR join, reads each Manifest closure condition's readiness against the records, and appends one Move Acceptance record with the whole state in it. It closes nothing and edits nothing: the closure act belongs to mc-close-mission-v17. Triggers on \"verify move v17\", \"mc-vf-move-v17\". No positional argument." --- # mc-vf-move-v17 Read this file to the end before acting. This skill is a sweep and a record: it performs no approval, repairs nothing, and edits no artifact. Its whole product is one ledger record a Business Owner reads before closing. `mc17` is the launcher `client/mc17` two levels above this skill's folder, from a POSIX shell, Git Bash included, and `client/mc17.cmd` from PowerShell or cmd. Every record this skill appends carries `recordedBy`, the name of the person or session that writes it down, on a ledger of either version. ``` mc-vf-move-v17 v0.1.0 (MC 1.7 - CanonQ-native) Parameters: ? (nothing else; the Mission resolves from context or is named) Mechanical half: mc17 (version, check, binding, fields, hash, tptrace, linkpass, rulings, orphans, ledger, history, evidence) plus ledger pointer reads. Product: one Move Acceptance record, verdict PASS or FAIL, in VF-{SCOPE}-001. ``` ## Step 0 - Which copy, which Mission, which line `mc17 version`, exact-title resolution of `MANIFEST-{SCOPE}-001`, pin gate as everywhere. Read the census (`mc17 read collection --id {collection_id}`), because every check below runs against what actually exists. ## Step 1 - The sweep, artifact by artifact For every governed artifact, read its verification and approval state from the ledger by selector (`/records/*[/refs/0/doc={name}]`) and its tracked row from the Manifest, and record what stands: - **The Manifest**: last verification PASS at the current binding (`mc17 binding` now, compared to the record). - **The three pinned documents**: `mc17 hash` on each asset the Methodology Reference pins, compared to the hash the pin line records. Equal means the law stands where the Mission pinned it. A moved hash means the pinned text was amended in place beneath the Mission: that is a FINDING named in the record with both figures and the pin line it belongs to, because every artifact of this Mission was verified against the text the pin recorded, and the BO closes knowing the law moved. Seventeen-16's closure re-verification found exactly this, hours after the amendment, and this sweep had run blind past it (its closure log's D-C5); the aggregate gate looks now. - **The SPEC**: verified PASS, Approved by the BO, carrying a current TO approval. Currency means the approval's recorded binding equals the verification's, which equals the binding now. - **The TP**: verified PASS at the current binding, Approved. - **The ARCH** where one exists: verified, TO-Approved, the Modules adoption performed. - **Every IP**: verified, approved at the radius its own Blast Radius claims, and where its tracked state word reads `Landed` or `Landed-on-branch`, the `mc17 check` join finds its IR. **The join prints how many rows it compared; a join that compared none while IP rows name a wave or a tip sha is a FAIL** (closure condition 1, L2/F2). Every acceptance record per wave present, naming its Wave Plan and ruling. - **The IP state words**: `mc17 check` prints each IP row's state word against the vocabulary `Draft`, `Verified`, `Approved`, `Landed-on-branch`, `Landed`, `Rework`, `Reverted`, `Stale`; a word outside it, or a `Rework` or `Reverted` cell naming no record, is a FAIL naming the row (Definition closure condition 1, as amended under IP-MC17-006). A plan in `Rework` is unlanded for closure condition 1 until its re-execution lands. - **Deferred acts past due**: the same `mc17 rulings` run prints every `deferred:` item of a repair ruling with its state, and an item reading `done record {n}` is done only where record n of the ledger it was handed carries no FAIL verdict and a body line reading `Discharges: {act}` in the deferred list's own words; **an item marked `PAST DUE` is a FAIL naming the act, the date and the authority** (Profile 5.2). The list ends at the first blank line followed by a line that is no item, where the authority's words go on; a blank line followed by an item is skipped, and a line that is no item inside the list reads `UNREAD` with its line and fails the register, because an act written there is counted nowhere (M-MC171-16). A Repair Move's own sweep is `mc17 ledger --repair --defect --sha `, and a repair whose reproduction record or RESOLVED record is absent FAILS naming it; a closed parent's ledger carries the DEFECT and the RESOLVED appends, and the repair collection's ledger the rest. - **The proven criterion**: `mc17 accept --spec --tp --results --manifest --ledger ` (Definition Section 10, *The proven criterion*; IP-MC17-017). **A criterion whose covering tests have not all run green is a FAIL naming it** - incomplete where a covering test stands deferred, unproven where none ran, red where one came back false - because a criterion proven only by a deferred or budget-shaped test is the hollow criterion Mission YardQ M1 shipped. Each such FAIL goes onto the Move Acceptance record with the criterion, its unrun cases, and every deviation entry that names the criterion, and the record carries the visible product delta per landed Implementation Plan, checked against those deviations; a shipped narrowing no deviation names is itself a finding. The narrowing of a criterion is put to its owner by name at acceptance, never accepted in silence. A criterion that `mc17 accept` prints `ok` as `accepted with resolved defect {n}` passes this check: a covering test came back red, defect record `{n}` names it, and a later record that opens `RESOLVED {n}` carries the own words of the Business Owner or the Technical Owner with his speaker line; the Move Acceptance record names each such criterion on a line of its own, `Accepted with resolved defect {n}: {criterion}, {case}, resolved at record {m}`, adding `no covering case ran green` where the line of `mc17 accept` says so, so the failure stays on the record. - **The ruled readings**: `mc17 readings --manifest --ledger --check`. **Each row the check does not read as reconciled is a FAIL naming the row and what fails** (Profile rule 1.9): a row that reads `reconciled: pending` stands open, and a reconciliation the check refuses names the test it fails. The Move Acceptance record carries each such FAIL, and the closure act refuses while one stands. - **The evidence join**: `mc17 evidence `, which reads the collection's own Manifest by its title for `review.blocking-severity-floor` and names an entry below the floor as advisory (Definition Section 10, *The review record* and the independent act beside it; IP-MC17-007, IP-MC17-011 L8). The verb is `evidence` and `reviews` answers as its alias, said once here for a reader who meets the old name in an older caller. The join reads every review AND every record declaring `producedBy: independent`, because a review is one shape of the independent act and a measurement is another. **An evidence asset no record cites, a citation resolving to no asset, a record declaring `producedBy: independent` while naming no `evidenceAsset`, a `producedBy` outside `independent|recorder`, a declared repair that repairs nothing, and a structured work-order item standing `open` are each a FAIL naming it**; a review recorded in the note form before the kind existed passes with its dispositions named as the reader's. **A record already written is repaired by a LATER record whose text opens `RESOLVED {n}`, which DECLARES `repairs: [n]` and carries the evidence asset itself**, and the join reads the citation there: a record already written gains no field beyond the dispatch of a work-order entry (Definition, *The review record*, L17), and a correction is a new record (IP-MC17-011 settlement 1, narrowed by the review of 2026-08-25). The join reads `repairs` on a record of any other opening as no repair, and a record opening `CORRECTION` as the correction it is. The declaration is the whole of the recognition, because a body that merely mentions a record number would excuse the very record a citation is owed from. Where a record in debt is mentioned by a later record carrying evidence, the join names that record as the one positioned to declare the repair, and discharges nothing. The join's header names what it compared, the number of records declaring an independent act included, and a ledger where that figure is zero is told so on the face of its PASS: a Mission written before this rule passes because it declared nothing, and the reader is owed that in the words of the verdict. The join's machine verdict is recorded in this Move Acceptance record, which is the one answer per Mission a product gate consumes. A citation of another Mission's REVIEW or VERIFICATION, its scope not this Mission's, is printed as a note and fails nothing: the report of a commissioned measurement lives in the measuring Mission's collection by closure condition 3, and the citation resolves there. - **The Rulings register**: `mc17 rulings --ledger `. **Any incomplete entry is a FAIL naming it and its empty field, and so is a malformed `### R{n}` heading, because a ruling that vanishes in silence is the register lying**: the aggregate gate is the last thing between the work and a merge word, and an unimplemented or unverifiable ruling surfaces here or it surfaces when the authority asks (Definition Section 1, *The Rulings register*; IP-MC17-004 AC-2). A Mission with no register is recorded as owing one and is not failed on that alone. - **Every test case owned**: `mc17 orphans --tp --ips [--wave ]`. Each orphan the tool names is a FAIL (Definition Section 3, *Every test case carries an owner*; L5/F3). The IP verification fails it first; this sweep repeats it at the aggregate because the union changes with every plan added. - **The integration record, per ruled wave whose members have all landed**: `mc17 ledger --wave WAVE-PLAN-{SCOPE}-{SEQ} --tip `, the tip being the sha the wave's last stage record names. **A wave with no `verification` record opening `Integration tip: {sha}` at that tip is a FAIL naming the tip expected** (Definition Section 5, *A wave's final stage is a verification at the merging tip*; L3/F4). Prose that names the tip is no record; the form is the line. - **Standing defect records**: `mc17 ledger ` lists every record of kind `defect` (and every `note` opening `DEFECT`, the pre-kind form) that neither its own verdict `PASS` closes nor a later record opening `RESOLVED {n}` names, with its disposition, and lists each closed one with the rule that closed it. **Read its `SKIPPED` lines too**: a `RESOLVED` the sweep did not read as a resolution (beyond a record's opening line, after a semicolon, as a range, in a form outside `RESOLVED 141, 142 and 143`) is named there with its record and line, and a defect that stays standing beside a SKIPPED line naming it is a record to write again in the lawful form, never a defect to argue past (IP-MC17-012 AC-6). **The disposition vocabulary is `repair here | repair in {Mission} | accept`** (Definition Section 10), stated here so the form is learned from the page; Seventeen-18's runner learned it from an immutable record and the sweep's complaint. **Every one is listed in this record with its disposition**, and a defect record stating no disposition is a FAIL naming it (Definition Section 10, *The defect record*; L1/F5). A standing defect with disposition `repair in {Mission}` or `accept` does not fail the sweep: it rides on the face of the closure record. - **The branch history, where the Mission's branch still stands**: `mc17 history --branch --base --repo `. A commit the stage records cannot account for is a FAIL naming the sha (Profile 8.1; IP-MC17-003 Part 3). A branch already merged and equal to the trunk has nothing to account for, and the record says so. - **The governed landing, over the Move's range on the trunk**: `mc17 landing --repo --range .. --ips --manifest `. **A landing that names a plan of record no ruled Wave Plan names is a FAIL (unplanned), and a fix whose plan declares neither a Repair Move (`Move type: Repair`) nor a Revision Mission (`Supersedes`) is a FAIL (undeclared repair)** (Profile, L14; IP-MC17-018). The audit reads every ruled Wave Plan the tracked table and the notes beside it name, a superseded one and one ruled before Wave Settings existed among them, and judges the plans of record alone, so the plan id a lock commit names is judged for nothing. **A commit that names no plan is a release: the audit lists it with its sha, its parent count and its committer, and fails nothing on it, and this record carries each release as a named deviation.** The audit also names each merge the hosting service made and each commit pushed outside any merge; it cannot tell a release from an administrator's bypass, which has one parent too, so the Business Owner judges each one this record names. A merge that an accepted record naming no Wave Plan names on its `Landing:` line passes as a landing made before the rule, and where the ledger declared nothing of the acceptance rule the audit says so in one line and passes the merge of a plan no ruled Wave Plan names. **Over the same range and record set, `mc17 unlanded --repo --range .. --ips --ledger ` names each plan no landing names, net of reverts, and each is a FAIL naming it (unlanded)**; a plan whose Status opens with `Withdrawn`, `Superseded` or `Deferred` owes none, and the verb reads a landing as a commit naming the plan, never as what the commit changed (R-LANDING, since 0.1.50). A plan whose accepted record lands it by an amendment record the ledger holds counts as landed, and the verb names that record. The audit reads what reached the trunk whatever branch the work was built on, which is why it sits here: the wave lock binds only its own `mission/*` branch (IP-MC17-003), and this reads the trunk itself. `gh pr merge --admin` overrides a required check with the owner's key and leaves no fingerprint in git history, so the override itself is not read; the landing it let through IS named here where it reached the trunk, and the override's prevention is the owner's over the repository's configuration (L14 part three). - **The doctrine read, over the three documents the Manifest pins**: `mc17 doctrine --guide --definition --profile --json`. A figure `old` or `unrecognised` is a finding naming the document, the figure, the verb's detail and the methodology's Technical Owner, whose repair is an amendment under Section 12 carried by an Implementation Plan in the methodology's Mission; a figure `ahead` (the passage reads at a version newer than this plugin) or `unreadable` is an unresolved determination naming the plugin copy or the passage. **It fails nothing in this Mission**, because where the running code and any prose about it disagree, the code is the fact and the prose the defect (Definition, *Law and the code that enforces it*; Profile L16; IP-MC17-020). The finding stands in the Move Acceptance record so the closure act and the authority read it. - **The three pinned documents, amended in place** (Definition Section 12 as amended 2026-08-23): a moved hash is the finding the second bullet of this step defines, never a failure; the record carries both figures and the pin line. Mission KnowledgeDomain records the 2026-08-23 move against itself deliberately. - **The Wave Plan(s)** where waves ran: ruled, verified, the executed order equal to the ruled order per the acceptance records. - **`mc17 check` on the Manifest**, whole, because its 24 rows, the naming checks and the landed-IP join are the mechanical floor of this sweep. It exits 1 on any row it prints as `FAIL` or `READ FAILURE` (since 0.1.49): the exit tells the runner a row stands to be judged, and each is judged by the rows of this list. - **The documents a change of text owes**: `mc17 check {manifest_asset_id} --ledger {ledger_asset_id} --documents`, over every document the tracked table names and every document a note beside the table names. **Each stale entry it prints is a FAIL naming the entry and the live-state write that removes it**: an approval entry at a binding other than the one its document carries now, the write printed beside it; an entry marked in place as superseded prints as a note and fails nothing. **Each verification owed it prints is a FAIL naming the document and the verifier run it owes**: a document of the six classes whose last verification record read a binding other than the one it carries now, or that no verification record names. **Each landed plan the acceptance join prints as FAIL is a FAIL naming the plan and its report**: a row that reads `Landed` with no standing report, a newest report no execution acceptance record names, a latest record that refuses the landing, a landing by an amendment record the ledger does not hold, and a report whose field reads `pending` or names another record than the latest one that names the report. **Each landed plan the Wave Plan join prints as FAIL is a FAIL naming the plan.** That join reads the Wave Plan the plan's accepted record names, and fails the plan where that Wave Plan is unruled, leaves the plan out, or has no `verification` record at PASS opening `Integration tip:`; an accepted record that names no Wave Plan records a landing made before the rule and passes with one line. A ledger the joins read as one that declared nothing of the acceptance rule passes both, and this record says so in the joins' words. ## Step 2 - The closure conditions, read for readiness Read the Manifest's numbered closure conditions and, for each, say from the records whether it is satisfiable today, satisfied already, or blocked and by what. Condition 7's closure approval is the one act this skill never anticipates: it reports the condition as the closure act's own. ## Step 3 - The verdict and the record PASS where every artifact stands verified and approved as the conditions require and nothing in the sweep contradicts a record; FAIL otherwise, with every gap named and the repair route beside it. Append one record with `mc17 append {ledger_asset_id} --record `, the record written to a file first: kind `verification`, `refs` leading with the Manifest and then every artifact swept, a document of another Mission named in the body and in no ref, evidence carrying the command outputs verbatim, the body opening with the sentence a Business Owner acts on: what stands ready, what does not, and what closing now would mean. **This record is the Move Acceptance record closure condition 2 reads.** ## Rules this skill cannot check - Whether the Move as built is the Move as declared: the BO's, reading the acceptance evidence. - Whether to close: the BO's act, through `mc-close-mission-v17`, never through this record.