physics

# Physics Research Router Use this top-level skill for physics requests that imply simulation, calculation, modeling, validation, input-deck generation, run monitoring, or result interpretation. Current skill discovery is top-level only, so the domain modules are routed references under `references/` rather than nested discoverable skills. Physics is a router by default, not a direct provisioner. If a user asks for direct monitor status without a bound underlying run owner, return `router_not_provisioner`. Executed-run monitoring belongs to the owning provisioner parent skill such as `experiment` or `inference-engineer`, not the physics router itself. ## First Steps 1. Classify the request into one family: `force_fields`, `molecular_dynamics`, `electronic_structure`, `particle_transport_collision`, `continuum_multiphysics`, `plasma_pic`, `nuclear_radiation`, `astro_cosmology`, or `literature_only`. 2. If classification is ambiguous and the answer would materially change the engine or safety posture, ask at most two clarifying questions. If the user does not answer, choose the safest open-source-first default and state the assumption. 3. Load the routed reference module plus `references/licensing.md` and `references/software-landscape.md`. 4. Write a run plan before execution or handoff. 5. Attach the matching dashboard profile id and preserve every generated config, script, log, parser output, artifact path, and Note outline. Non-computational ...