Skip to content

Generalize Pattern 4 to unverified premises - #190

Merged
shinpr merged 1 commit into
mainfrom
fix/unverified-premise-pattern
Oct 12, 2026
Merged

shinpr merged 1 commit into
mainfrom
fix/unverified-premise-pattern

Conversation

@shinpr

@shinpr shinpr commented Oct 12, 2026

Copy link
Copy Markdown
Owner

Summary

Implementation can rest on a premise nobody checked: that a library behaves a certain way, that existing code already provides something, or that data has a certain shape. When the premise is false, the work built on it fails, or it collects workarounds that each patch one part of an approach that no longer holds.

Pattern 4 in ai-development-guide and frontend-ai-guide covered only part of this: uncertainty about new technology. It also prescribed a certainty record block for that case.

This PR widens Pattern 4 to any unverified premise and drops the record block, so the guides get shorter.

Changes

  • Changed: Pattern 4 is now "Building on Unverified Premises" in both guides. When an unverified premise could invalidate the chosen approach, check it by the cheapest sufficient means before building dependent work on it. When results contradict the premise, reconsider the approach before patching its parts. The reasoning stays in the active task, with no separate artifact.
  • Removed: the Certainty / Exploratory implementation / Fallback record block from Pattern 4.
  • Removed: the "Optimistic implementation of uncertain technology" red flag. It duplicated Pattern 4.

Both guides change because task-executor loads ai-development-guide and task-executor-frontend loads frontend-ai-guide.

Also included: the patch version is bumped to 0.28.1, and the plugin copies are synced.

claude plugin validate passes for the marketplace and all plugins.

🤖 Generated with Claude Code

Pattern 4 in ai-development-guide and frontend-ai-guide covered only
uncertainty about new technology and prescribed a certainty record
block. A premise about existing code, library behavior, or data can
fail the same way, and work built on it then fails or collects
workarounds.

Pattern 4 now covers any unverified premise that could invalidate the
chosen approach: check it by the cheapest sufficient means before
building dependent work on it, and when results contradict it,
reconsider the approach before patching its parts. The reasoning stays
in the active task, so the certainty record block is removed. The
"Optimistic implementation of uncertain technology" red flag
duplicated Pattern 4 and is removed as well.

Bump the patch version to 0.28.1.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@shinpr shinpr self-assigned this Oct 12, 2026
@shinpr
shinpr merged commit a125d07 into main Oct 12, 2026
1 check passed
@shinpr
shinpr deleted the fix/unverified-premise-pattern branch October 12, 2026 05:56
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