rubbing-research-orchestratorlisted

# Rubbing Research Orchestrator Manage research state and routing. Do not perform OCR, image restoration, source interpretation, or historical fact generation inside this Skill. Current contract identity: `rubbing-research-orchestrator` version `1.4.0`. Current route and record-event Schema version: `1.3`. Preserve the immutable 1.1/Skill-1.2.3 and 1.2/Skill-1.3.0 Schema files only for historical validation; documents written under them keep validating unchanged. The additive `question-plan-v1` contract is advisory and provider-neutral. It does not change route 1.3, select a third-party Skill, admit evidence, or authorize historical publication. The router accepts ReflectionMemo schema `1.0` or `1.1` from current `research-hypothesis-reflection` `1.2.0` and, for read-only historical routing compatibility, `1.1.0` and `1.0.0`. Every version must bind the same case ID and the exact current ResearchCase bytes, and must prove that the input was not overwritten. Reject every unknown or missing Reflection Skill version. A memo bound to the case before reflection is stale after an updated case is emitted and must not be reused against that updated case. ## Plan the question profile Before assembling a workflow, classify what the question actually requires: ```bash python3 scripts/orchestrate.py plan-question \ --question "What differs between two precisely located carrier readings?" \ --profile carrier-comparison \ --output work/question-plan.json ``` Profiles are `car