Skip to content

Name deferral as a register class - #363

Open
alanhc wants to merge 2 commits into
sysprog21:mainfrom
alanhc:prose-register-deferral
Open

Name deferral as a register class#363
alanhc wants to merge 2 commits into
sysprog21:mainfrom
alanhc:prose-register-deferral

Conversation

@alanhc

@alanhc alanhc commented Sep 3, 2026

Copy link
Copy Markdown
Collaborator

references/prose-register.md names the classes that mark machine-written
prose, and binds PR bodies and review replies alongside source comments and
docs/. One class was missing: text about the writer rather than about the
work.

#350 carried an instance. A reply closed a decision that had already been
measured by offering to reverse it on request, and the answer was "Let's
concentrate on real discussions!". The same shape reaches review text as an
apology for a correction, and as an announcement of candor in front of a
caveat that stands on its own.

Two commits, one per surface, following the split the register states in its
own opening: the register defines a class, and a SKILL.md section names
that class's instance on one surface.

  • The register gains the class, next to "Effort and flattery", which is the
    neighbouring case of writing about the writer.
  • The Pull requests section gains the reply form, quoting the rejected
    sentence and citing Reject a PI waiter from any plain requeue #350 the way the rules around it cite PR#21, PR#41 and
    PR#209.

Why it costs a reviewer something: an offer to redo the work another way asks
them to choose between two shapes the writer has already measured, when the
decision and the reason that settles it were what they needed. A reviewer who
disagrees says so without being invited.

Verification

scripts/check-skill-refs.py resolves every path, target, section and
cross-reference across the 12 files under .claude/, and
scripts/check-commit-log.sh accepts both commits. Documentation only: no
build or test target reads these files.


Summary by cubic

Names deferral and self-report as a prose-register class so guidance can flag text about the writer instead of the work. Pull request replies should state a measured decision and its reason rather than hand the choice back to the reviewer.

  • Covers offers to redo work, apologies for corrections, and candor announcements before independent caveats.
  • Adds PR#350 as a concrete review-reply example.
  • Documentation-only; no runtime behavior changes.

Written for commit b1349a0. Summary will update on new commits.

Review in cubic

The Pull requests section bars pasted walkthroughs and status tables,
and says a reply carries the correction, the measurement, or nothing.
It does not name the sentence that closes a reply by offering to redo
the change if the reviewer would prefer it, which PR#350 rejected on
sight.

That is the artifact the two earlier citations were already about, in
a politer form. It asks the reviewer for an instruction instead of
stating a position, and the tradeoff it puts up for a vote had been
measured before the reply was written.
The register binds PR bodies and review replies and names the classes
that mark machine-written prose. One was missing: text about the writer
rather than about the work.

PR#350 carried an instance. A paragraph closed a measured decision by
offering to reverse it on request, and the maintainer quoted it back
with "Let's concentrate on real discussions!". The same shape reaches
review text as an apology for a correction and as an announcement of
candor before a caveat that stands on its own.

An offer to redo the work another way asks the reviewer to choose
between two shapes the writer has already measured, and the decision
plus the reason that settles it is what they needed instead. A reviewer
who disagrees says so without being invited.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 issue found across 2 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name=".claude/skills/elfuse-conventions/SKILL.md">

<violation number="1" location=".claude/skills/elfuse-conventions/SKILL.md:383">
P3: This guidance describes the rule with a metaphor and an uncheckable politeness comparison instead of naming the deferral directly. Replace it with a factual description such as “A reply that asks the reviewer to choose between measured alternatives is a deferral.”</violation>
</file>

Reply with feedback, questions, or to request a fix.

Re-trigger cubic

correction, the measurement, or nothing. A concise what and why belongs in
the commit body, not the thread.

A reply that hands the choice back is the same artifact in a politer form:

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P3: This guidance describes the rule with a metaphor and an uncheckable politeness comparison instead of naming the deferral directly. Replace it with a factual description such as “A reply that asks the reviewer to choose between measured alternatives is a deferral.”

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At .claude/skills/elfuse-conventions/SKILL.md, line 383:

<comment>This guidance describes the rule with a metaphor and an uncheckable politeness comparison instead of naming the deferral directly. Replace it with a factual description such as “A reply that asks the reviewer to choose between measured alternatives is a deferral.”</comment>

<file context>
@@ -380,6 +380,14 @@ addressed threads with "Resolve conversation"; a reply carries the
 correction, the measurement, or nothing. A concise what and why belongs in
 the commit body, not the thread.
 
+A reply that hands the choice back is the same artifact in a politer form:
+"If you would rather the source read uniformly one way or the other, say so
+and I will move the remaining three" asks the reviewer for an instruction
</file context>
Suggested change
A reply that hands the choice back is the same artifact in a politer form:
A reply that asks the reviewer to choose between measured alternatives is a deferral:

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