# Safety and Operations

## Scope

This document defines minimum software and bench controls before any energetic or flight test.

## Software Controls

1. State-machine guards must be active.
2. Deployment commands must be acknowledged and logged.
3. Pyro channels must only fire from explicit allowed states.
4. Telemetry stream must be validated before arming.

## Pre-Flight Checklist

1. Physical setup:
   - Verify wiring against pin map.
   - Confirm continuity on all pyro channels.
   - Verify recovery hardware mechanical freedom.
2. Avionics checks:
   - Confirm barometer offset complete.
   - Confirm IMU outputs stable when static.
   - Confirm battery level above mission threshold.
3. Comms checks:
   - Confirm command round-trip (PING and state command).
   - Confirm dashboard packet-rate and stale-status behavior.
4. Actuator checks (inert/isolated):
   - Reaction wheel command direction and stop command.
   - Rogallo command sequence test.
   - CanSat release timing test.

## Abort Conditions

Do not proceed if any of the following are true:

- Sensor initialization fails.
- Continuity reports unexpected state.
- Battery undervoltage or unstable rail.
- Uncommanded actuator movement.
- Telemetry stale/disconnected during critical phase.

## Bench Test Policy

- Use inert loads for all pyro logic tests.
- Perform dry-run mission script before every firmware release.
- Require at least two-person verification for arm/launch decisions.

## Post-Flight Review

1. Retrieve logs and replay timeline.
2. Verify expected state transitions.
3. Compare deployment timing against expected thresholds.
4. Record anomalies and corrective actions before next mission.