research: specify profiling and inference organ boundaries

[Jammy2211]

Summary

Defines how future profiling and inference organs can aggregate many project repositories while keeping measurement producers and scientific evidence project-owned. Specifies proposed registries/read contracts, domain comparison rules, freshness and partial-failure handling, cockpit integration, rollout and acceptance cases. Names and second real adopters remain implementation choices; no organ or exporter is created by this PR.

Includes a six-case trial of an additional role-routing checklist against the adopted terminology. Both conditions selected all six change targets correctly; the checklist conflated decision owner and repair repository in three fields despite correct action routes. Retain current routing without mandating the checklist. Frozen inputs, exact answers and grading are retained; the report discloses context-grading ambiguity and the single-pair/no-retrieval limitations.

Closes #444.

Scripts Changed

None. Research/design prose and fixed trial evidence only. No runtime routing, library APIs, project scripts, production schemas or repository categories change.

Test Plan

• Sphinx HTML build succeeds with zero warnings, including linked evidence downloads and the new specification.
• Seven specification citations resolve to pinned repository objects; current/proposed contracts distinguished.
• Trial input/response hashes, parsed JSON equality, score totals and download paths verified; 36 source-excerpt paragraphs checked against pinned objects.
• Frozen trial evidence unchanged by specification continuation; whitespace check passes.
• Earlier routing trial independently reviewed, findings corrected and re-review CLEAN. The later organ specification was checked by the author only; no further Fable review requested per user instruction.
• Scientific smoke: not applicable to prose and fixed evidence artifacts.
• New-head GitHub checks must pass before a separately authorized merge.

Human-authorized Heart RED override

The user replied "I authorize, continue" to the task-specific request to push the completed specification under a development-only override.

Exact current Heart reason: autofit_workspace: Smoke Tests failure on main.
Snapshot: 2026-10-01T20:02:44.036627+00:00; RED, score 80. Passed branch gates are listed above.

This permits development commit/push/PR update only. The documentation does not repair Heart; release remains blocked and neither merge nor CI bypass is authorized. Authorization is also recorded on issue #444 and in Mind active state and the first autonomy-log table.

Generated by the PyAutoLabs agent workflow.