Reason Required

Background and reasoning behind design decisions in splam. This page won’t tell you how to do something. See the How-To Guides for that.

Why a Reason is required for service actions

splam assumes its operator works in a regulated (pharma/biotech) environment, where changes to systems that touch validated data need to be traceable: who did what, when, and why. Requiring a reason before Start/Stop/Restart, and recording it alongside the result in the audit trail, gives you a durable record you can correlate with a change ticket without relying on operators remembering to document things separately.