Safety

Safety Philosophy

How Kerfio thinks about safety, defaults, and user confirmation.

4 min readsafety

Safety Philosophy

Kerfio controls a real CNC machine. Every movement can be dangerous.

Kerfio must always prefer:

text
stop
warn
confirm
validate
block unsafe action

over risky automation.

Always Visible Safety Information

The app shell or active CNC section should always show:

  • machine connection
  • machine state
  • current X/Y/Z
  • pause/stop
  • alarm state

Actions Requiring Confirmation

The following actions must not happen silently:

  • start job
  • resume job
  • machine movement from canvas
  • set work zero
  • home machine
  • unlock machine
  • soft reset
  • probe cycle
  • run macro with motion
  • send raw G-code
  • turn spindle/laser on
  • run Kerf toolpath
  • dry trace
  • apply machine profile changes that affect motion

Blocked Actions

Kerfio should block action when:

  • machine is disconnected
  • machine is alarmed
  • job is already running
  • target is out of bounds
  • toolpath validation failed
  • calibration is required but missing
  • confirmation is missing
  • machine profile is invalid