Skip to content

📝 docs: plan: map each check to an owner and a level, as COR-104 - #429

Merged
pascalandy merged 3 commits into
mainfrom
docs/cor-104-verification-map
Nov 3, 2026
Merged

pascalandy merged 3 commits into
mainfrom
docs/cor-104-verification-map

Conversation

@pascalandy

@pascalandy pascalandy commented Nov 2, 2026 •

Copy link
Copy Markdown
Owner

Pascal wanted to know where the line sits between Nicely's core, the extension template, and one extension such as video-convert, and how to push the most verification into the core and the template. COR-103 placed each check, but nothing mapped the whole loop: code, checks and CI, prose and skills, then QA and UAT, for each owner. The six trial rounds also showed that their score stopped measuring: builds scored 36 of 36 while real defects sat outside the cases.

This pull request writes that map as D068, which extends D067 without moving its line, and plans it as COR-104 with 10 cards. The core and the template get each practice first. Video-convert adopts the loop last, through #427.

  • D068 maps each owner and level to its mechanism, says how a correction moves up a level and across owners, and replaces the trial score with three measures: the prose-only rules of each rule index, a Corrections table with Level and Owner in docs/qa/ledger.md, and real use by video-convert
  • When an extension finds a correction that belongs to the core or the template, its agent opens an issue here and records a linked limit
  • Each extension keeps its own publication code. The core and the template give the checks, helpers, fixtures, forms, and skill lines
  • The TLC runner moves into the kit. Each extension keeps its model and its mapping
  • architecture.md gets a short Verification section. Its "other folders" list moves to its own file, unchanged, because the file was at 9,943 of 10,000 bytes
  • The glossary defines a verification level apart from a code-map layer
  • The queue is COR-102, then COR-104. just next still serves COR-102-T1

No card is implemented here. The evidence is in pascalandy/nicely-research#23, which merges first so that the links resolve.

How it was made: scouts and analyses on 237 correction commits, two prototypes (an SDK analyzer that reaches an extension at its pinned version, and the TLC runner in the kit with a model of the finish gate), then an arena of two plans. A blind judge scored the base 23 and the other 20. Five ideas were grafted from the other plan.

Proof: just check passes at cc560495. The review fixes change only the COR-104 file; go -C tools test ./cmd/plan and just limits pass on them, and just signoff runs on the final head.

Reviewed with codex-loop: 2 rounds with gpt-6-astra on high. Sol verdict: approved

by Opus-5.5 via Claude Code

…r own file

architecture.md holds 9,943 bytes, and just limits caps a growing file
at 10,000. The list of the folders outside the code map now has its own
file, with no change of its text, so that the next commit can add a
section. architecture.md links the new file in place of the list.
D068 extends D067 with the owner and level map of the verification
loop: core, the template, and each extension, at the levels of code,
checks, prose, then QA and UAT. It says how a correction moves up a
level and across owners, and it replaces the score of the 36 trial
cases with three measures: the prose-only rules of each rule index,
the level and owner of each correction in the ledger, and the real use
of the loop by video-convert.

architecture.md gets a short section that links D067 and D068, and
the glossary defines a verification level apart from a layer.

COR-104 holds ten cards, core and template first, then video-convert,
which adopts the loop as #427 asks. It follows COR-102 in the queue.
The evidence is in nicely-research, under synthesis/verification-map.
@coderabbitai

coderabbitai Bot commented Nov 2, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Repository UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 64f03536-93ee-4158-9ad3-b64861a1e4e6

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

… history of old records

Video-convert updates to a Nicely release, but D043 releases an item only
when it ships. The last merge of T1 to T9 now releases a minor version,
as this plan asks. An extension with Markdown build records starts a new
build when it updates and keeps them as history.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@pascalandy
pascalandy merged commit 4c5cc71 into main Nov 3, 2026
3 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