Skip to content

feat(standards): stop claiming that plan structure is verified by fixtures - #19

Merged
MrScripty merged 6 commits into
mainfrom
docs/planning-verification-line
Nov 14, 2026
Merged

MrScripty merged 6 commits into
mainfrom
docs/planning-verification-line

Conversation

@MrScripty

Copy link
Copy Markdown
Owner

Summary

With the plan-format checks gone, two sentences still said they exist. This corrects both through the Engine's standards-authoring workflow.

  • workflows/planning.md, metadata line: Verification: Active-plan structure fixtures and objective-level acceptance review. becomes Verification: Objective-level acceptance review.
  • evaluation/standards-effectiveness/verification-guide.md: "plan records" is dropped from the list of what the checkpoint checks.

Two commits:

  1. The review record, docs/audits/planning-verification-line-review-2026-11-13.md. The Engine takes its review evidence from the committed revision it starts from, so the record is committed first.
  2. The Engine's own commit (author "Standards Engine", as for earlier standards changes), produced by propose, resolve, review and apply.

Effect on application agents

None. The Planning module's approval for application delivery is renewed in the same change, so it is still delivered with the label current and not changed-since-review. No policy unit's text changes.

Left as it is

  • workflows/planning.md line 293 permits plan-structure checks. That is still true, so it is unchanged.
  • docs/decisions/standards-library-information-architecture.md mentions the checks as history.

Verification

On this commit: twelve package suites (700 tests), the Engine suite (688 tests) and verify.py --complete (22 of 22 suites) pass, and the working tree is clean.

Stack

Third of three; contains the commits from the first two. Review the last two commits. This one is separate so it can be accepted or rejected on its own. Merge with a merge commit: the review record cites a commit hash.

🤖 Generated with Claude Code

MrScripty and others added 6 commits November 13, 2026 18:39
release-maintenance-policy/metadata-closure validated a hand-typed list of
12 module paths. The whole-corpus check canonical-corpus-metadata/
canonical-corpus already validates all 74 canonical modules through the same
call, so the listed check could not fail for a reason the corpus check does
not also report. A mutation test confirmed it: 48 metadata defects across the
12 listed modules failed both checks with the same diagnostic each time.

The retirement was made by the Engine's maintain_evidence operation (preview,
then apply), not by hand. Retiring the only check emptied the suite, so the
Engine also removed the suite, its registry entry and its enforcement-suite
node in the policy-impact catalogue. No relationship named the node or the
suite, so none changed.

Fifty-five sibling checks were retired earlier; this one was held back because
the node catalogue digest is part of every coverage requirement. Removing the
node changes all 53 requirement IDs and turns the 16 current certificates
stale. The owner has accepted that; the certificates are left in place and
reissued in a later commit, each after review.

docs/audits/metadata-closure-retirement-2026-11-13.md is the review record
supplied to the operation.

Suites 24 -> 23, checks 67 -> 66, catalogue nodes 122 -> 121, certificates
current/stale 16/8 -> 0/24.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
The owner has decided that the plan template is a guide and that the layout
of a plan is not something to verify. The 19 plan_contract checks in suite
planning-consolidation ran a layout validator on 19 sample plans and nothing
else: no check ran it on a real plan, and run by hand it rejects 25 of the 28
plans under docs/plans. The checks worked as written, but what they checked is
not a requirement, so they are removed rather than repaired.

The removal was made by the Engine's maintain_evidence operation (preview,
then apply), not by hand. Retiring the suite removed its 19 checks, its
registry entry, its enforcement-suite node in the policy-impact catalogue and
the four relationships that named the suite as consumer and evidence owner
(from workflow.planning.active-plan-fields, workflow.planning.lifecycle-
authority, topic.architecture.composed-design-admission and
workflow.commit.per-commit-boundary). No other relationship named the suite,
so no evidence owner was replaced. Each of the four units keeps its template,
prompt, documentation and normative consumers.

The validator code and the sample plans follow in the next two commits; the
samples go last because the validator's unit test reads them.
templates/PLAN-TEMPLATE.md is kept.

Every certificate is already stale after the metadata-check retirement. Two
of them cite the retired suite file as evidence; a stale certificate is
ignored on load, so they stay in place until they are reissued.

docs/audits/plan-format-check-removal-2026-11-13.md is the review record
supplied to the operation.

Suites 23 -> 22, checks 66 -> 47, catalogue nodes 121 -> 120, policy-impact
relationships 356 -> 352.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
The plan_contract check kind validated the layout of a plan document. Its
only suite, planning-consolidation, was retired in the previous commit after
the owner decided the plan template is a guide rather than something to
verify, so the validator has no caller left.

Remove the check implementation, its registration in the check parser, its
unit test (3 tests) and its row in the README's check-kind table. A suite that
still declares a plan_contract check now fails with CONFIG.UNKNOWN_CHECK,
like any other unsupported kind.

Nothing else used the validator. The sample plans its unit test read are
retired through the Engine in the next commit. templates/PLAN-TEMPLATE.md is
unchanged.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
The 19 files under evaluation/standards-effectiveness/fixtures/plans/ were
the inputs of the plan_contract checks and of the validator's unit test. Both
are gone, so nothing reads the samples any more.

The files were removed by the Engine's maintain_evidence operation (preview,
then apply) with retire_inputs, not by hand. The operation refuses an input a
retained suite still uses; none did. No suite, catalogue node, relationship
or certificate changes.

This is a separate commit from the suite retirement so that the validator's
unit test never ran without the samples it read.

docs/audits/plan-format-check-removal-2026-11-13.md is the review record
supplied to the operation.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…orrection

With the plan-format checks gone, two sentences still say they exist: the
Verification metadata line of workflows/planning.md and the verification
guide's list of what the checkpoint checks. Both can only be corrected
through the Engine's standards-authoring workflow, which takes its review
evidence from the committed revision it starts from.

This record is that evidence. It states the exact one-line change to each
file, what was checked about the candidate (one changed line per file, no
changed policy unit, no reader of the wording, the application label with
and without re-approval) and what the review does not cover. Committing it
first lets the next commit, made by the Engine, cite it.

The correction is kept apart from the check removal so the owner can accept
or reject it on its own.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…cture is verified by fixtures

The plan-format checks, their validator and their sample plans were removed after the owner decided the plan template is a guide rather than something to verify. Two statements still say those checks exist: the Planning workflow's Verification metadata line and the verification guide's list of what the checkpoint checks. This change removes only the untrue part of each. No policy unit text, heading, relationship or routing rule changes. The Planning workflow is re-approved for application delivery because the one metadata line is its only difference from the content approved before; without that approval it would be delivered labelled changed-since-review.
@coderabbitai

coderabbitai Bot commented Nov 14, 2026

Copy link
Copy Markdown

Important

  • Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 119410c9-beeb-47d1-9fa2-6bb5c720c3e9
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@MrScripty
MrScripty merged commit ab1ee8a into main Nov 14, 2026
2 checks passed
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.

1 participant