16 lines
1.5 KiB
Markdown
16 lines
1.5 KiB
Markdown
|
# Research-Backed Engineering
|
||
|
|
|
||
|
|
Use this profile when implementation correctness depends on current external APIs, standards, advisories, provider behavior, or versioned specifications.
|
||
|
|
|
||
|
|
```text
|
||
|
|
MiniMax M3 research lead (active root, sole writer, built-in live web search)
|
||
|
|
├── Luna source researcher (MCP, read-only, built-in live web search)
|
||
|
|
└── Claude Sonnet 5 source auditor (MCP, read-only, built-in live web search)
|
||
|
|
```
|
||
|
|
|
||
|
|
Independent research can run in parallel while the root maps the repository, but an authoritative dated dossier is a real dependency before root-owned implementation. The auditor independently re-fetches pivotal sources and checks both the dossier and change. Exact models, live-search grants, contracts, goal/turn lifecycle, and sole-writer boundary are mechanical. Source authority and implementation ordering are instruction-driven and evaluated.
|
||
|
|
|
||
|
|
Cost and latency are high. Conflicting or unavailable primary sources produce a blocked or reduced-confidence result. Operators may clone the profile and grant a registered Firecrawl-like Tool MCP server only to the researcher; no deployment-specific server is bundled.
|
||
|
|
|
||
|
|
Researcher and auditor are persistent supervised Unix app-server workers. The root controls both; the auditor may steer, interrupt, pause, continue, detach, or return the researcher for a source correction while acceptance remains with normal lineage authority. Pending input remains durable, and transport suspension retains terminal history, the dated dossier, trace, and partial source evidence.
|