# Ecosystem Boundaries

## polisher-sim

Owns planning intelligence:
- metrology ingestion;
- mirror state and residuals;
- removal prediction;
- dwell/preset planning;
- calibration and uncertainty;
- campaign reports.

## polisher-post

Owns translation and validation:
- schema validation;
- machine capability checks;
- unit normalization;
- segmentation;
- packaging `controller-job.v1`;
- run-log normalization back into analysis format.

## polisher-control

Owns machine execution:
- state machine;
- manual mode;
- setpoint execution;
- force loop interface;
- telemetry;
- alarms/interlocks;
- pause/resume/abort;
- run/manual-session logs;
- operator workflow.

## Shared contracts

Own schemas and names that must not drift silently:
- `controller-job.v1`;
- `run-log.v1`;
- `manual-session-log.v1`;
- `machine-capabilities.v1`;
- telemetry channel names;
- event/alarm codes.

## Boundary rule

If you are about to add planning, optimization, calibration, or metrology interpretation to this repo, stop and ask Antoine. That likely belongs upstream.