Merge pull request #62 from VoynichLabs/feature/domain-aware-ranking-proposal

feat: propose domain-aware plan ranking engine with relative comparison

Author: neoneye

docs/proposals/05-semantic-plan-search-graph.md

@@ -118,6 +118,8 @@ def index_plan(plan_id, title, prompt, summary):
 
 ### Search API
 
+**NOTE:** This API is a proposed local feature, not part of the public MCP interface. Implementation details TBD.
+
 ```http
 GET /api/plans/search
 Query Parameters:
@@ -189,6 +191,7 @@ def generate_plan_with_examples(prompt):
 ### 3. Plan Recommendations
 ```jsx
 // After user completes a plan
+// NOTE: Endpoint `/api/plans/{planId}/similar` is a proposed feature (TBD implementation)
 function RelatedPlans({ currentPlanId }) {
   const { data } = useSWR(`/api/plans/${currentPlanId}/similar?limit=5`);
 
@@ -252,7 +255,7 @@ def trending_domains(days=30):
 
 ### Week 3: Search API
 
-- Build `/api/plans/search` endpoint
+- Build semantic search endpoint (TBD - local feature, not part of MCP)
 
 - Add filtering (domain, min_similarity)
 

docs/proposals/07-elo-ranking.md

@@ -35,7 +35,9 @@ PlanExe ranks generated plans using a two‑phase LLM evaluation to avoid gaming
 
 - Corpus source: PlanExe‑web `_data/examples.yml`
 
-## Endpoints
+## Endpoints (Proposed Local Feature)
+
+**NOTE:** These endpoints are proposed for local/self-hosted PlanExe deployments. They are not part of the public MCP interface. Implementation TBD.
 
 - `POST /api/rank` → rank plan, update Elo
 
@@ -510,7 +512,7 @@ X-API-Key: <your_api_secret>
   },
   "budget_cents": 1500000000,
   "title": "Electric VTOL Development Program",
-  "url": "https://planexe.com/plans/abc123"
+  "url": "https://home.planexe.org/plans/abc123"
 }
 ```
 

docs/proposals/12-evidence-based-founder-execution-index.md

@@ -52,7 +52,7 @@ In short: as AI can read and evaluate entire reports, the advantage of slide dec
 
 Example of a PlanExe report that an AI can evaluate end-to-end:
 
-- https://planexe.org/20260114_cbc_validation_report.html
+- https://docs.planexe.org/examples/20260114_cbc_validation_report.html (TBD - verify URL)
 
 This is the kind of artifact the FEI is designed to ingest and audit. If the numbers are fabricated or hallucinated, the FEI should penalize confidence and surface the missing verification.
 

docs/proposals/44-investor-grade-audit-pack-generator.md

@@ -124,7 +124,7 @@ Create a new audit pack.
 ```json
 {
   "pack_id": "pack_456",
-  "download_url": "https://planexe.org/api/audit/download/pack_456.pdf",
+  "download_url": "https://home.planexe.org/api/audit/download/pack_456.pdf",
   "expires_at": "2026-02-18T16:00:00Z"
 }
 ```

docs/proposals/48-moltbook-reputation-bridge.md

@@ -55,7 +55,7 @@ Create a verifiable claim system where PlanExe acts as a reputation oracle:
     {
       "name": "Master Architect",
       "description": "Won 5+ Bids in 'Construction'",
-      "icon_url": "https://planexe.org/badges/architect_gold.svg",
+      "icon_url": "https://home.planexe.org/badges/architect_gold.svg",
       "issued_at": "2026-02-11"
     }
   ],

docs/proposals/62-agent-first-frontend-discoverability.md

@@ -34,7 +34,7 @@ This section records what is currently implemented in the repository and what st
   - MCP auth uses `X-API-Key`
   - Tool names match current MCP tools (`prompt_examples`, `task_create`, `task_status`, `task_stop`, `task_file_info`)
   - Pricing/cost docs point to `https://docs.planexe.org/costs_and_models/`
-  - Support contact includes Discord: `https://planexe.org/discord`
+  - Support contact includes Discord: `https://home.planexe.org/discord`
 - Current positioning is documented:
   - `home.planexe.org` is human-facing (account/billing/docs links)
   - `mcp.planexe.org` is the AI-facing API surface
@@ -117,7 +117,7 @@ Recommended flow:
 
 - Docs: https://docs.planexe.org
 - GitHub issues: https://github.com/PlanExeOrg/PlanExe/issues
-- Discord: https://planexe.org/discord
+- Discord: https://home.planexe.org/discord
 ```
 
 **Implementation:**
@@ -132,6 +132,8 @@ Recommended flow:
 
 ### 2. OpenAPI / LLM-Optimized Tool Schema
 
+**STATUS: NOT YET IMPLEMENTED** — This recommendation is aspirational. The `/openapi.json` endpoint does not currently exist on either domain.
+
 **What:** Expose machine-readable schemas for PlanExe's AI-facing interfaces (MCP-first), and optionally OpenAPI for any public REST surfaces.
 
 **Why:** OpenAI's function-calling guide and Responses API expect structured function schemas. LLMs perform better with:
@@ -272,6 +274,8 @@ Recommended flow:
 
 ### 3. MCP Well-Known Endpoint (`.well-known/mcp.json`)
 
+**STATUS: NOT YET IMPLEMENTED** — This endpoint does not currently exist at `mcp.planexe.org/.well-known/mcp.json`. This is a future enhancement.
+
 **What:** Add `/.well-known/mcp.json` describing PlanExe as an MCP server, compatible with OpenAI's MCP connector and orchestrators.
 
 **Why:** OpenAI's tools-connectors-mcp guide and orchestrator patterns show that MCP servers need a discoverable manifest listing available tools, auth requirements, and rate limits.