intake_triage · supabase_json

Oro Docs MCP intake_triage

intake_triage artifact · for Oro Docs MCP · status draft

Planning Surface

Use this to decide what happens next.

Status

draft

decision

notes

No user clarification is required to produce the planning artifact set.

status

ready_for_requirements

Agent Handoff

Start Here

intake_triage artifact · for Oro Docs MCP · status draft

Completion Evidence

No explicit evidence field yet. Require tests, screenshots, linked PRs, or reviewed outputs before marking complete.

Decision

notes: No user clarification is required to produce the planning artifact set.
status: ready_for_requirements

Structured Payload

Machine-readable source fields

triage

urgency

normal

build mode

artifact_first

complexity

medium

classification

internal_tool

ux spec required

false

research required

false

ux spec rationale

This is an MCP/tooling project with no visual product surface. The user-facing contract is the MCP tool schema and command behavior, captured in REQUIREMENTS and ARCHITECTURE instead of UX_SPEC.

architecture required

true

decomposition required

true

exec approval required before build

true

project

oro-docs-mcp

name

Oro Documentation MCP

client id

redkey

intent ref

docs/projects/oro-docs-mcp/artifacts/INTENT.json

decision

notes

No user clarification is required to produce the planning artifact set.

status

ready_for_requirements

known inputs

id	path	type	notes
INPUT-001	C:/Users/jstnk/Downloads/cc/projects/documentation	local_repo	Oro documentation source repo, Sphinx/reStructuredText, public docs published at https://doc.oroinc.com/.
INPUT-002	Hedera documentation MCP	existing_pattern	Desired interaction pattern: search tool plus read-only docs filesystem query tool.

artifact type

INTAKE_TRIAGE

schema version

1.0

blocking questions

No items captured.

source observations

The Oro documentation repository contains index.rst and top-level sections including api, backend, bundles, cloud, community, developer, frontend, and user.
The corpus is mostly .rst files with many images and code examples.
README states the documentation source is CC-BY-NC-SA 4.0 and published at https://doc.oroinc.com/.
The root index.rst uses a Sphinx toctree glob over */index.

non blocking questions

id	default	question
OQ-TRIAGE-001	Include both local paths and best-effort public URLs.	Should search results include generated public URLs for the `master` docs path or only local paths?
OQ-TRIAGE-002	Include code examples, but rank prose docs higher for conceptual queries.	Should code examples be searched by default?