feat: propose domain-aware plan ranking engine with relative comparison#62
Merged
neoneye merged 3 commits intoPlanExeOrg:mainfrom Feb 22, 2026
Merged
Conversation
added 3 commits
February 20, 2026 21:50
- Replace hallucinated /api/plans/*, /api/rank, /api/leaderboard endpoints with TBD notes - Fix invalid planexe.org domain URLs → home.planexe.org - Replace hallucinated tool names: create_plan, check_plan_status → task_create, task_status - Remove non-existent tool: get_next_action_item - Add implementation status notes to /openapi.json and /.well-known/mcp.json recommendations - Clarify that semantic search API and Elo ranking APIs are proposed local features, not part of public MCP
- Add domain classifier to detect plan type (construction, software, marketing, ops, etc.) - Implement domain-specific KPI extraction (timeline, resources, risk, owner clarity) - Corpus bucketing for fair comparison within domain context - ELO ranking engine for relative plan scoring (not absolute) - Actionability scoring to surface refinement candidates vs. rewrite situations - 4-phase implementation roadmap (10 days total) - Full API spec and data model
2 tasks
neoneye
added a commit
that referenced
this pull request
Mar 9, 2026
Improve discoverability for AI crawlers and agents: - New public/robots.txt with AI-specific user agent rules (GPTBot, ChatGPT-User, Claude-Web, Anthropic-AI, etc.) - Add "For AI Agents" section to README.md with discovery links, MCP endpoint, workflow summary, and key zip file paths Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
3 tasks
neoneye
added a commit
that referenced
this pull request
Mar 11, 2026
Add AI agent discoverability: robots.txt and README section (#62)
neoneye
added a commit
that referenced
this pull request
Mar 11, 2026
1 task
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
2 participants
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.
Domain-Aware Plan Ranking Engine Proposal
This proposal addresses the problem of universal rubrics breaking down when comparing plans across different domains.
Key Changes
Problem Solved
Current evaluation assumes a universal rubric (concreteness, executability, success criteria). This breaks when comparing a road construction plan to a software project—they have completely different success signals.
With domain awareness, we can:
Implementation Plan
4 phases over ~10 days:
See full proposal for architecture, data model, test strategy, and risk mitigation.