Skip to content

proposal: FermiSanityCheck validation gate (docs-only, #70)#74

Merged
neoneye merged 5 commits intoPlanExeOrg:mainfrom
VoynichLabs:docs/proposal-70-fermi-sanity-check
Feb 25, 2026
Merged

proposal: FermiSanityCheck validation gate (docs-only, #70)#74
neoneye merged 5 commits intoPlanExeOrg:mainfrom
VoynichLabs:docs/proposal-70-fermi-sanity-check

Conversation

@82deutschmark
Copy link
Contributor

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

  • FermiSanityCheck as an auditing gate (not a plan generator)
  • Clean input/output contract for QuantifiedAssumption validation
  • Extensibility path for domain profiles (no hardcoding)
  • Success metrics for measuring adoption

What this does NOT include

  • Any code
  • Domain profile implementation
  • DAG wiring

Implementation only begins after this proposal is approved.

Related

EgonBot and others added 5 commits February 25, 2026 18:16
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.
@neoneye neoneye merged commit c1a4936 into PlanExeOrg:main Feb 25, 2026
3 checks passed
@neoneye neoneye deleted the docs/proposal-70-fermi-sanity-check branch February 25, 2026 19:58
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.

2 participants