decomp · supabase_json
Oro Docs MCP decomp
[object Object]
Agent Handoff
Start Here
[object Object]Completion Evidence
No explicit evidence field yet. Require tests, screenshots, linked PRs, or reviewed outputs before marking complete.
Artifact Shape
- handoff: notes: object, ready_for_plan: boolean
- modules: 9 items
- project: id: string, name: string, client_id: string, source_artifacts: object
- summary: strategy: string, critical_path: object
- artifact type: DECOMP
- schema version: 1.0
Structured Payload
Machine-readable source fields
handoff
notes
- Do not include UX implementation tasks.
- M-02 and M-06 should be reviewed carefully because they define and verify the filesystem safety boundary.
- Complete scope includes hosted MCP, MCP cards, semantic/hybrid search, and source-corpus support, not just a minimal docs-only MCP.
ready for plan
true
modules
| id | goal | name | status | acceptance | depends on |
|---|---|---|---|---|---|
| M-00 | Confirm package location, source repo paths, Projects database target, Node/MCP baseline, and exact implementation boundaries. | Substrate Confirmation | draft | - Substrate audit records package path, docs source path, app source path, Projects database target, runtime, and MCP config target. - No MCP implementation code is written in M-00. | |
| M-01 | Create the MCP package, implement RST-aware documentation indexing, and expose docs-first search_oro. | Docs Indexer and Search Tool | draft | - Index builds from the local Oro docs checkout.
- search_oro returns ranked docs results for representative Oro queries.
- Tests cover heading extraction, snippets, URL mapping, and missing-index behavior. | - M-00 |
| M-02 | Implement query_docs_filesystem_oro with safe allowlisted commands and root confinement. | Read-Only Docs Filesystem Tool | draft | - Allowed commands can list, search, and read docs. - Traversal, absolute-path, write, shell, process-control, and network attempts are rejected. - Output truncation is deterministic. | - M-01 |
| M-03 | Add optional embeddings and hybrid retrieval while preserving keyword-only fallback. | Semantic and Hybrid Search | draft | - Embedding refresh can be run explicitly when credentials are configured. - Hybrid search returns sensible results and falls back to keyword search when embeddings are unavailable. - Search mode can be selected as keyword, semantic, or hybrid. | - M-02 |
| M-04 | Index selected Oro application source files as a separate, filterable corpus. | Oro Application Source Corpus | draft | - Source results are clearly labeled and filterable. - Generated/vendor/cache/secret-prone paths are excluded. - Docs results remain the default for documentation questions. | - M-03 |
| M-05 | Create server-level and Oro capability MCP cards plus the browser-readable catalog content for mcp.bezeliq.ai. | MCP Cards and Browser Catalog | draft | - Cards validate as JSON.
- Cards describe hosted endpoint, tools, corpora, safety, ownership, refresh behavior, and examples.
- get_mcp_card or equivalent discovery route returns the cards.
- Root catalog content explains available MCPs, how to connect, and exposed tools for browser visitors.
- Registry/card metadata model targets the Projects database. | - M-04 |
| M-06 | Add quality, regression, and safety tests for the complete MCP. | Evaluation Harness | draft | - Representative Oro queries pass expected-source checks. - Filesystem safety tests pass. - Evaluation output is saved for review. | - M-05 |
| M-07 | Deploy the complete registry and Oro MCP endpoint behind https://mcp.bezeliq.ai/ and https://mcp.bezeliq.ai/oro. | Hosted Deployment | draft | - mcp.bezeliq.ai resolves to the browser-readable MCP catalog.
- mcp.bezeliq.ai/oro serves the Oro MCP endpoint or endpoint documentation based on client negotiation.
- Remote smoke tests can call search, filesystem query, and card tools.
- Deployment docs cover environment variables and refresh process. | - M-06 |
| M-08 | Wire the hosted MCP into the local Codex/Atlas environment and document usage. | Codex/Atlas Registration and Documentation | draft | - MCP config snippet points to https://mcp.bezeliq.ai/.
- Smoke tests confirm search_oro and query_docs_filesystem_oro work from an MCP client.
- README documents hosted usage, refresh, startup, corpus filters, embedding behavior, source path, MCP cards, and limitations. | - M-07 |
project
id
oro-docs-mcp
name
Oro Documentation MCP
client id
redkey
source artifacts
architecture
docs/projects/oro-docs-mcp/artifacts/ARCHITECTURE.json
requirements
docs/projects/oro-docs-mcp/artifacts/REQUIREMENTS.json
coherence review
docs/projects/oro-docs-mcp/artifacts/COHERENCE_REVIEW.json
summary
strategy
Deliver the full MCP in controlled slices: confirm substrate, build docs index/search, add safe filesystem inspection, add semantic/hybrid search, add application-source corpus, add MCP cards and browser catalog, evaluate, deploy to mcp.bezeliq.ai/oro under the registry root, then register with Codex/Atlas.
critical path
- M-00
- M-01
- M-02
- M-03
- M-04
- M-05
- M-06
- M-07
- M-08
artifact type
DECOMP
schema version
1.0