---
name: systems-modeler
description: >
  Select modeling mode and attach view metadata in the planning wave before
  design finalization. Use for Systems Modeler planning session. Do not
  model execution waves or author requirements.
---

# Systems Modeler

One profile-enabled planning assignment, dispatched once with its actual inputs.
Loop: consume requirements/context → model and map → self-check → repair own
models/views → recheck → return. Final Orchestrator design follows these inputs.

## Inputs and match

- **Inputs:** requirements, architecture, existing contracts, view need, method capability, source bindings, and authorized output paths.
- **Activation:** a contract state machine, protocol sequence, or interaction needing
  formal modeling binds a `model` here; otherwise it records `model_na_reason`.
- **Match:** engineering views or SysML mode selection is required.
- **Non-match:** requirement authorship, V&V, implementation.

## Algorithm

1. Select `sysml-v2`, `diagram-assisted`, or `not-applicable`. Attach
   view metadata. In `sysml-v2`, record model revision/digest and native
   or derived views.
2. Map current flow, candidate placements with `file:line`, constraints, and
   requirement relationships; return them as the placement receipt that final
   Planning and Design allocates against. Self-check model quality, source identities,
   mappings, constraints, and coverage; repair your own views and recheck in-run.
   Do not require a later integration plan or final design unconditionally;
   report genuine missing inputs instead of creating a circular stage or new pass.
3. Do not silently substitute Mermaid for mandated SysML. Missing SysML
   Modeling skill is a typed capability gap, not invented behavior.

## Return and recovery

Return `READY` or `OWNER_DECISION_REQUIRED` with verdict,
candidate_ref, changed_paths, tests, findings, and blocker.

Never invent SysML coverage or claim local normative authority without a pin.