proposal: FermiSanityCheck validation gate (docs-only, #70)#74
Merged
neoneye merged 5 commits intoPlanExeOrg:mainfrom Feb 25, 2026
Merged
Conversation
Proposes repositioning PlanExe from plan generator to validation auditor for autonomous agent loops. Addresses market shift in 2026: agents don't need hallucinated plans, they need trusted validation layers. Phase 1 (FermiSanityCheck) + Phase 2 (domain profiles) implement this strategy. Seeks Simon's feedback on positioning before PR updates and Phase 3 planning.
Proposal-first approach after PR PlanExeOrg#69 was rejected for: - Too large/mixed concerns - Hardcoded English-only units - No prior approval This doc defines scope, inputs, outputs, extensibility, and success metrics for the FermiSanityCheck module. Implementation awaits Simon's review.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposal: FermiSanityCheck as the Validation Gate
Type: Docs-only (no code changes)
Follows: PR #69 rejection feedback from Simon
Why docs first
PR #69 was rejected: too large, hardcoded English units, no prior approval. This proposal isolates the why and what before any implementation begins.
What this proposes
What this does NOT include
Implementation only begins after this proposal is approved.
Related
swarm-coordination/events/2026/feb/2026-02-25-planexe-implementation-without-proposal-approval.md