Four features share one engine and one register — three of them (FTR-28, FTR-30, FTR-32) grouped together in their own Research category below; FTR-29 stays under Legal, since it's specifically the casework-tied layer and that's the more useful home for a legal-project operator browsing the catalog. FTR-28 is the engine itself: the RS track, the Research Register, the prompt structure, the multi-platform submission, and the polish methodology — installable alone for a project that just needs single-question research done properly, now with all prompts and masters landing in one consistent research\research_prompts\ folder rather than a topic-relative one, and the generated prompt presented directly in the conversation for easy copying rather than left to be opened from disk. FTR-29 layers a legal-specific LR track on top of FTR-28 for casework research tied to a Master Case File — install it only alongside FTR-28, and only for legal projects; note LR items deliberately keep their own, different storage rule (tied to the matter's own folder) rather than adopting FTR-28's consolidated location, since legal casework is naturally organized by matter. FTR-30 layers chain orchestration on top of FTR-28 for research that isn't one question but a dependency-linked set of them — install it only alongside FTR-28, and it works with either the RS or LR track depending on whether FTR-29 is also present. FTR-32 adds a third execution mechanism rather than a new track or a new orchestration layer: instead of the operator manually running Deep Research on each platform (FTR-28) or manually pacing a dependency chain of those manual runs (FTR-30), FTR-32 hands Cowork a single kickoff covering a whole batch — parallel or chained — and lets Cowork self-sequence, reporting per-item as results land. Same register, same RS/LR ID scheme, same four-stage tracking shape underneath all four; what differs feature to feature is who's doing the work and how many platforms are involved, not how the item is tracked. None of the four duplicate each other's mechanics: FTR-29, FTR-30, and FTR-32 each explicitly point back to FTR-28 rather than restating its prompt structure or polish steps. FTR-33 (Paste-Driven Provenance Archive) is a related but separate family — see its own file's "Relationship to FTR-32" section for exactly how it differs (paste-driven, human-retrieved, no Cowork involvement) from this research family's Cowork-driven mode.