Tech Brief Orchestrator

Technical Brief Orchestrator: The Master System Architect (V2)

This skill coordinates hyper-depth technical audits. It is optimized for Educational Deep-Dives, moving beyond factual lists into causal, step-by-step explanations of infrastructure.

1. THE "EDUCATIONAL MASTER" MANDATE

The goal is a document that a Lead Partner can use to understand the technology from first principles.

• The Causality Rule: Every technical component must be explained through its inputs, its mathematical transformation, and its specific clinical output.
• The "How it Works" Step-by-Step: Every section MUST include a numbered walkthrough of the data journey.
• Mental Model Anchoring: Use the "Complexity Explanation" blocks to ground abstract math in physical analogies.

2. THE ORCHESTRATION WORKFLOW

2.1 Phase 1: Mechanics Harvesting

For every pillar, the Orchestrator MUST identify the Functional Steps:

1. Search for "How [Component X] works step by step."
2. Extract the specific mathematical transformations (e.g., "Encoder projects to 32k dimensions, then ReLU gating...").
3. Store these in raw_findings/tech/mechanics_[pillar_name].md.

2.2 Phase 2: Specialized Process Teardowns

Activate sub-agents with the instruction to write a Functional Anatomy of their pillar:

1. Superposition Auditor: Explain the "Superposition Problem" as a geometric data-jumble.
2. SAE-Rad Factory: Detail the "Disentanglement Assembly Line."
3. Causal Probe Specialist: Detail the "Counterfactual Verification Loop."
4. LookOut Trajectory Analyst: Detail the "Path Forecasting Logic."
5. Mecha Infrastructure Expert: Detail the "Footprint Optimization Process."

2.3 Phase 3: Recursive Deepening

Scan for any "Then a miracle occurs" jumps in logic. If a process step is missing (e.g., "How does the feature get its name?"), reissue searches to find the specific primitive.

2.4 Phase 4: Master Assembly (The Learning Doc)

Assemble master_technical_brief.md as a cohesive Technical Guidebook.

End of Technical Brief Orchestrator Skill.