Gate QA · Package-Shaped Gate · Proposed → your act decides
P-PH000-AC007-GATE001 Cycle 2

Accept the P-STD-008 WDL standard

One decision is in front of you: whether to merge the gate package that lands the program's workspace-development-lifecycle spine. Cycle 1 was recycled; everything it asked for was absorbed into this one package. Work the checklist, then record your act.

Activity
P-PH000-AC007 — accept P-STD-008
Date
2026-07-09
Gate package
PR #444
Control ledger
Issue #337
Remediation task
TK010 · #455
What actually counts as acceptance

Reply merge on PR #444. The merge event, plus an acceptance-ledger comment on control-ledger #337, together form the durable proof trail (P-STD-008-CLAUSE-005I).

The checkboxes below are a working aid only — nothing is saved, and ticking them records nothing. The recorded act is your reply and the ledger comment, not this page's state.

1
The journey here
How this package reached cycle 2
R1
2026-07-08
CHECK002 · Round 1
Accept
Delegated adversarial review of the TK003–TK008 set. Three non-gating P3 findings.
C1
2026-07-09
GATE001 · Cycle 1
Recycle
HDO judged the spine incomplete: no HDO endgame (GAP-001). A drift sweep surfaced seven more gaps.
T
1 task · S1–S9
TK010 remediation
Absorbed
All eight gaps fixed in one task on this branch — no new gates, no new carriers (A-002).
R2
2026-07-09
CHECK002 · Round 2
Recycle → fixed
Full-scope Codex review. Five findings: F01–F04 fixed in-package, F05 raised as a variance.
▸
now
GATE001 · Cycle 2
You are here
This QA surface. Work the checklist and record your act on PR #444.
✓
on accept
Merge
If approved
Lands P-STD-008 v1.1.0 (accepted) on main and closes AC007.

AC007's purpose is to accept P-STD-008 — the program's workspace-development-lifecycle spine — into the standards register: the shared control-node vocabulary (gate / checkpoint / exception / handoff), the merge-anchored proof-of-disposition model, and the pre-commissioning (CHECK000) discipline everything downstream inherits.

Cycle 1 was not a CHECK002 failure. The machine review passed. The HDO recycled it because the standard defined control nodes and proof rules but went silent on the HDO endgame — what happens between a gate-package PR's submission and the merge. No QA procedure, no human-facing confirmation surface, no recorded-act semantics. A same-day HITL/AFK feedback comment on #337 and a repo-wide drift sweep surfaced six further gaps. The HDO directed all of it into one remediation task.

What cycle 2 now presents: the amended gate-proof clauses (CLAUSE-005D/G/H/I), a package-shaped-gate endgame procedure in the WDL guideline, a normalized HITL/AFK criterion, a GitHub-issue-integrated phase-plan template, a now-normative single-remediation-task default, three hygiene fixes — and, satisfying the very rule it introduces, this QA confirmation surface itself.

2
Effect of the merge
What merging does — and deliberately does not do
Merging does 6
  • Lands P-STD-008 v1.1.0 (accepted status) on main, with the CLAUSE-005D/G/H/I gate-proof amendments.
  • Lands guideline_program_wdl.md v1.3.0 (endgame procedure, normalized HITL/AFK, §V checkpoint-minimum flexibility), guideline_workspace_plan.md v2.5.0 (single-remediation-task norm, GH-issue owner rule), and template_workspace_plan_phase.md v2.5.0 (GH-issue integration, Parent Issue / Plan File split).
  • Removes the deprecated template_html-proposal-approval-view.html from the active templates path and points §VIII at the archive only.
  • Corrects the stale AC009 seed and the sps_P-PROGRAM.md P-RES-004 wording that drifted onto this branch.
  • Closes AC007 on an approving disposition — nothing deferred to a new gate or carrier (A-002).
  • Unblocks work gated on GATE001, including AC009's WDL-conformant seed authoring against an accepted baseline.
Intentionally does not 5
  • Adopt the dual-file JSON+HTML construction for this or any QA surface — that measured-adoption lane is reserved for #184's successor (A-004).
  • Mint any new gate or checkpoint to carry the absorbed gaps; everything routes through this one PR.
  • Add an informative note to CLAUSE-004E for Q-001 (whether one is needed after the §IV/§V rewrite) — CHECK002 round 2 assessed it and judged none necessary, so no note is added (see §4 residue).
  • Touch PM board projection state or repair non-terminal status rows (round-1 finding F03).
  • Re-litigate the §IV/§V HITL/AFK drafting choice beyond the single uniform execution-path criterion.
3
The QA items
Confirmation checklist — 11 claims, each traceable to a commit

Every claim below is verifiable in this package. Tick a card when you've satisfied yourself of it — expand How to verify for the exact commit and file to open. This is a working aid; the recorded act is still your reply on PR #444.

Working through the checklist 0 / 11 confirmed
A Cycle-1 RECYCLE gaps — closed

The eight gaps the cycle-1 recycle raised, each remediated in-package by TK010. One claim per gap.

M-01GAP-001 · HDO endgame
The CLAUSE-005 family and the WDL guideline now define the HDO endgame: a required QA surface, an HDO QA procedure, and recorded-act semantics.
80200df3 c43c313a standard_P-STD-008 · §CLAUSE-005G/H/I guideline_program_wdl · §VI
How to verify
In 80200df3, open the standard and find the three new bullet subclauses inserted directly after CLAUSE-005F, before the informative research note. In c43c313a, open the guideline and find the new 7-step "Package-shaped gate endgame" list after the PR-body boundary bullets.
M-02GAP-002 · proof path
CLAUSE-005D no longer hard-requires a full GDPP/GDR for every gate; package-shaped gates get a conformant lighter proof path — so this cycle-2 merge conforms to the standard it accepts rather than varying from it on day one.
80200df3 standard_P-STD-008 · §CLAUSE-005D · §CLAUSE-004A
How to verify
Diff 80200df3: confirm CLAUSE-005D now reads "gate proof appropriate to the gate's disposition semantics… package-shaped gates… the gate-package PR plus the QA confirmation surface… and the recorded HDO act…", and that CLAUSE-004A now points to CLAUSE-005D instead of hard-coding GDPP/GDR.
M-03GAP-003 · HITL/AFK
§IV now applies one uniform execution-path criterion instead of two competing HITL tests; §V register-declares CHECK001 ownership (AFK default unless declared HITL) rather than hard-coding it; and — in the v1.3.0 amendment — §V's approved pattern now parenthesizes both (CHECK001) and (CHECK002) and states the normative minimum: CHECK000 plus a terminal gate is mandated, while CHECK001/CHECK002 and any further checkpoints are plan-declared checkpoint-class instances that exist only when the frozen register declares them.
3bf08900 b87c1c51 guideline_program_wdl · §IV · §V
How to verify
Diff 3bf08900: §IV table and fill-rule bullets rewritten around "a human's attendance or decision sits in its execution path"; §V table's CHECK001 row changed from "Checkpoint, HITL" to "Checkpoint, register-declarable (AFK default unless declared HITL)". Then diff b87c1c51 (v1.3.0): §V's pattern line now reads CHECK000 → TK### … → (CHECK001) → (CHECK002) → GATE001, and its intro paragraph states the mandated minimum is CHECK000 (CLAUSE-006) plus a terminal gate, with CHECK001/CHECK002 as plan-declared instances — the §V rows being operating profiles for nodes that exist, "not a mandate that each node exists".
M-04GAP-004 · phase template
The phase-plan template (now v2.5.0) carries parent_issue frontmatter, a GitHub Parent Issue field, and an Issue row in the Links Register; its Activity Snapshot register — first reworked under 94e7878d — now splits the single Reference column into two dedicated columns, Parent Issue and Plan File, so each activity row carries both its parent-issue URL and its plan path rather than one combined cell.
94e7878d b87c1c51 template_workspace_plan_phase
How to verify
Diff 94e7878d for the original GH-issue integration: the parent_issue: frontmatter key, the "GitHub Parent Issue" line, the Activity-table rework, and the "Issue | Phase parent issue" Links-Register row. Then diff b87c1c51 (v2.5.0): the Activity Snapshot header changes from … | Owner | Reference | to … | Owner | Parent Issue | Plan File |, and the AC001 example row carries the parent-issue URL and the plan path in separate cells.
M-05GAP-005 · one-task norm
§VII now normatively states the single-remediation-task default — mint exactly one; multiple requires explicit HDO approval recorded in the gate disposition or control ledger — replacing ambiguous singular wording.
94e7878d guideline_workspace_plan · §VII
How to verify
Diff 94e7878d on the plan guideline: confirm the §VII recycle paragraph now reads "By default, mint exactly one remediation task after the gate row… Multiple remediation tasks at one gate require explicit HDO approval…".
M-06GAP-006 · deprecated template
The deprecated template_html-proposal-approval-view.html no longer exists at the active templates path; only the pre-existing archived copy remains, and §VIII points at it.
f9b4928e guideline_workspace_proposal · §VIII …archive/deprecated/template_html-proposal-approval-view.html
How to verify
Diff f9b4928e: confirm the file-deletion hunk for the active-path template (templates/consultant/workspace/template_html-proposal-approval-view.html), and that §VIII's deprecated-surfaces bullet now reads archive/deprecated/template_html-proposal-approval-view.html with the duplicate archived-content row removed. The active-path pill is intentionally absent — that file no longer exists; only the archived copy is navigable.
M-07GAP-007 · AC009 seed
The AC009 commissioning-seed no longer says P-STD-008 "is itself draft"; it now states P-STD-008 is accepted via GATE001 and that the prior acceptance-collision caveat is obsolete.
surfacedd196796c fixedf9b4928e draft_P-PH000-AC009_commissioning-seed · line 44
How to verify
The condition was carried onto this branch by the S1 main-refresh merge (d196796c, which pulled in origin/main PR #451). Diff f9b4928e: confirm the one-line change to "P-STD-008 is accepted via P-PH000-AC007-GATE001… the prior acceptance-collision caveat is obsolete."
M-08GAP-008 · stale SPS row
sps_P-PROGRAM.md's P-RES-004 row no longer reads "(Reserved)" / "pending TK009"; it reflects TK009's delivered brief/report links.
f9b4928e sps_P-PROGRAM · P-RES-004 changelog_sps_P-PROGRAM · v0.16.1
How to verify
Diff f9b4928e: confirm the P-RES-004 row title drops "(Reserved)" and the brief/report path cells drop "(pending TK009)"; confirm the matching v0.16.1 changelog row.
B Package integrity & the one variance you're accepting

Three claims about the package itself: it dogfoods the rule it introduces, it carries an honest machine-review verdict, and it asks you to accept exactly one explicit variance.

M-09Self-referential
This file is itself the human-facing QA confirmation surface that CLAUSE-005G now requires: single-file, self-contained HTML, committed inside the gate package, enumerating what happened / merge effects / claims matrix / open residue / approval semantics.
d6e783af this file (proposal/view_…qa-confirmation.html) — no self-referential pill
How to verify
You are reading it. Check it against CLAUSE-005G's five enumerated requirements — see the self-conformance statement in the provenance drawer at the foot of this page. This file was introduced in d6e783af (the P-PH000-AC007-TK010: S6… entry in PR #444's commit list); later amendments to it appear as their own entries in the same PR's commit list.
M-10CHECK002 round 2 · REV002
A full current-surface gate-package review (not delta-scoped) by Codex CLI / gpt-5.5 / xhigh returned RECYCLE with five findings. F01–F04 are remediated in-package by the TK010 S9 commit; F05 is dispositioned as an explicit HDO variance (row M-11). This is not a passing verdict — RECYCLE with in-package remediation is the honest state; final acceptance is yours.
15199a77 …CHECK002-REV002_reviewer-codex.md
How to verify
Read the raw review at analysis/raw/P-PH000-AC007-CHECK002-REV002_reviewer-codex.md (commit 15199a77): verdict RECYCLE, five findings, full gate-package scope stated in its own header. All five are remediated in-package by the subsequent TK010 S9 commit in PR #444's commit list, except F05, dispositioned as the M-11 variance.
M-11⚠ Variance — a real decision
This QA surface uses the unregistered view_ filename stem (the P-STD-004 prefix registry has no stem for CLAUSE-005G surfaces). Ticking this accepts the variance for this artifact only; stem registration is routed as a follow-on P-STD-004 amendment.
n/a — no commit standard_P-STD-004 · prefix registry
How to verify
Confirm standard_P-STD-004_file-naming-and-directory-convention.md's prefix table has no registered stem for CLAUSE-005G QA confirmation surfaces, and that this file's name (view_P-PH000-AC007-GATE001_qa-confirmation.html) uses the view_ precedent. Ticking this accepts the variance for this artifact only — it does not register the stem program-wide.
4
What stays open
Open residue — honestly listed
Resolved
Q-001 — does CLAUSE-004E need an informative note after the §IV/§V HITL/AFK rewrite?Judged unnecessary per the TK010 S4 conformance check. CHECK002 round 2 (REV002) has now happened: its request packet carried Q-001 as an explicit exclusion ("challenge that disposition only if you find a concrete conflict") and the reviewer raised nothing. No informative-note edit is required, and none is made.
HDO-accepted
CHECK002-REV001-F02 (round 1, P3) — provisional-posture consistency note for P-STD-004/P-STD-005 references in draft CLAUSE-004H.Accepted, no remediation required (round-1 verdict). Largely moot now that P-STD-008 carries accepted status rather than draft.
HDO-accepted
CHECK002-REV001-F03 (round 1, P3) — board projection confirmation/repair for non-terminal status rows.Accepted, no remediation required before GATE001. Board-side, not file-based — recorded as follow-up hygiene outside this PR package's scope.
HDO-accepted
#184 dual-file JSON+HTML measured-adoption lane.Explicitly out of scope (A-004). This package's single-file HTML QA surface claims no template authority over that lane and does not front-run its instrumented experiment.
Remediated
CHECK002 round 2 (REV002) verdict — see checklist row M-10.Full gate-package review by Codex CLI / gpt-5.5 / xhigh. RECYCLE, 5 findings. F01–F04 remediated in-package by the TK010 S9 commit; F05 dispositioned as the M-11 variance. Evidence: …REV002_reviewer-codex.md.
Open
P-STD-004 prefix registry has no registered filename stem for CLAUSE-005G QA confirmation surfaces (this file uses the view_ precedent).Not absorbed into this package. Carried as the explicit M-11 variance/acceptance condition. Confirming M-11 accepts it for this artifact; stem registration is routed as a follow-on P-STD-004 amendment. Registry: standard_P-STD-004.
5
Approval semantics
Your decision — and what each disposition means
✓merge
Accept-and-close — closes AC007, nothing deferred (A-002).
recycle
Same gate ID; one more remediation task by default (§VII).
hold
Pause disposition; state the blocking condition.
kill
Stop the activity; state the reason.

The gate act for a package-shaped gate is your recorded disposition as a durable platform record (P-STD-008-CLAUSE-005I): a reply on PR #444, and/or a ledger comment on #337. After an approving disposition, the merge event plus the acceptance-ledger comment form the durable proof trail, bound to the PR and to this QA surface.

A second recycle would depart from the HDO's 2026-07-09 "absorb everything, no new carriers" direction (A-002) and needs explicit new instruction to do so.
Provenance & self-conformance

This artifact

  • Path: artifacts/tasks/P/workspace/PH000/AC007/proposal/view_P-PH000-AC007-GATE001_qa-confirmation.html
  • Gate package: PR #444 · Control ledger: #337 · Remediation: TK010 · #455
  • Construction: single-file, self-contained HTML · zero external requests · strict house CSP

Primary references

  • analysis/analysis_P-PH000-AC007-GATE001_cycle1-recycle-decision-architecture.md — cycle-1 gap register and decision architecture.
  • analysis/analysis_P-PH000-AC007-CHECK002_gate001-cycle2-package-review-request.md + analysis/raw/P-PH000-AC007-CHECK002-REV002_reviewer-codex.md — REV002 request, verdict, disposition.
  • plan_P-PH000-AC007.md — TK010 register row and GATE001 recycle re-entry block.

Self-conformance statement (P-STD-008-CLAUSE-005G)

This file is a single-file, self-contained HTML artifact with zero external requests, committed inside gate-package PR #444. It enumerates: what happened in the activity including the cycle-1 recycle (§1); what the merge changes and intentionally does not change (§2); a matrix from claim to PR/commit evidence, verification step, and HDO confirmation, covering every register gap (§3); open residue (§4); and the approval semantics defining the accepting act (§5) — the five requirements CLAUSE-005G lists, satisfied by the first artifact minted under it.