Skip to content

P0008 (accept + execute): validator-deliverable convention in release-validation-gate#169

Merged
klappy merged 1 commit intomainfrom
claude/p0008-validator-dolcheo-ledger
May 5, 2026
Merged

P0008 (accept + execute): validator-deliverable convention in release-validation-gate#169
klappy merged 1 commit intomainfrom
claude/p0008-validator-dolcheo-ledger

Conversation

@klappy
Copy link
Copy Markdown
Owner

@klappy klappy commented May 5, 2026

What this PR does

Combined acceptance + execution of promotion P0008 — codifies the validator's deliverable shape for the release-validation-gate workflow.

Acceptance (1 file)

  • docs/promotions/P0008-pr-validator-dolcheo-ledger-as-deliverable.md
    • promotion_status: proposedaccepted
    • Tags array "proposed""accepted"
    • Status section header → accepted (2026-05-05)
    • Review Notes filled

Execution (1 file, +42 lines)

  • canon/constraints/release-validation-gate.md — new section before ## Related Canon:
    • ## Validator Deliverable Convention — The PR-NN Fresh-Validator Ledger
    • Two-artifact requirement: DOLCHEO ledger at canon/encodings/pr-NN-fresh-validator-ledger.md + companion handoff at canon/handoffs/pr-NN-fresh-validator-review.md
    • DOLCHEO section ordering specified (D, O, L, C, H, O-open) with what each captures
    • Constraints (C) MUST be paired with permanent or v+1 revisit candidate — silent acceptance is the named failure mode
    • Receipts cite PTXprint PR Add Anti-Cache Lying constraint and content-addressed storage implementation #30 v1.3 telemetry as the worked example

Why this is third in the queue

The release-validation-gate runs on every load-bearing PR — including the 7 still-queued promotion PRs in this sweep. Codifying the validator deliverable shape now means those subsequent PRs (or the next fresh-validator dispatch) have canon to point at, rather than re-deriving the format under time pressure.

Position in the 8-proposal sweep

# ID Status
1 P0009 PR #167
2 P0001 PR #168
3 P0008 this PR
4 P0007 next — DoD as 5–7 agent-observable behaviors
5-8 P0006, P0003, P0004, P0005 queued

DoD

  • Proposal frontmatter promotion_status flipped to accepted
  • Review Notes block filled
  • Canon edit text matches P0008 §"Proposed Language" verbatim
  • Insertion point matches P0008 §"Section" (append, before Related Canon)
  • No other canon docs touched

Note

Medium Risk
Medium risk because it adds a new, enforced-by-convention deliverable requirement for fresh-validator reviews, which may change release-validation-gate workflows and reviewer expectations. Changes are documentation/canon-only with no runtime code impact.

Overview
Accepts and executes promotion P0008 to standardize fresh-validator outputs under release-validation-gate.

Updates canon/constraints/release-validation-gate.md with a new Validator Deliverable Convention that requires two repo-committed artifacts for each fresh-context validator review: a DOLCHEO-structured ledger at canon/encodings/pr-NN-fresh-validator-ledger.md (with mandated D/O/L/C/H/O-open sections, including explicit permanent vs v+1 revisit candidate constraint labeling) and a companion prose review at canon/handoffs/pr-NN-fresh-validator-review.md.

Promotes docs/promotions/P0008-pr-validator-dolcheo-ledger-as-deliverable.md from proposed to accepted, updating metadata and filling the review notes with the acceptance decision/date.

Reviewed by Cursor Bugbot for commit 802421e. Bugbot is set up for automated code reviews on this repo. Configure here.

…-validation-gate

Acceptance:
- Flip docs/promotions/P0008 promotion_status: proposed -> accepted
- Update tags array ("proposed" -> "accepted")
- Fill Review Notes with operator decision (klappy, 2026-05-05)

Execution:
- canon/constraints/release-validation-gate.md: append new section
  "## Validator Deliverable Convention — The PR-NN Fresh-Validator Ledger"
  before "## Related Canon"
- Codifies that fresh-session validators MUST produce two artifacts
  (DOLCHEO ledger + companion handoff doc) committed to the repo
- Codifies that accepted-as-constraint deviations MUST be paired with
  permanent or v+1-revisit-candidate framing — silent acceptance is
  the named failure mode

Third of 8 stuck proposals being walked through. Previous: P0009 (PR #167),
P0001 (PR #168). Next: P0007 (DoD as agent-observable behaviors).
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 5, 2026

Canon Quality — oddkit_audit

No dead klappy:// references or legacy link patterns found in writings/. 39 files scanned.

Spec: klappy://docs/oddkit/specs/oddkit-audit · Workflow: .github/workflows/canon-quality.yml · Run: #40

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants