Change management and secure development

Change workflow

• Every change is version-controlled with a description of intent; no direct edits to running production code.
• Type checking, linting and automated tests run before a change is released.
• Database changes are applied as reviewed, versioned migrations — never as ad-hoc statements.
• Releases can be rolled back to a previous known-good version.

Secure development practices

• All user input is validated server-side with schema validation, not only in the browser.
• Database access uses parameterised queries; no string-concatenated SQL.
• Secrets live in the managed secret store and are read only by server-side code.
• Production source maps and internal technical routes are disabled so build internals are not published.

Dependencies

Third-party packages are scanned for known vulnerabilities. High and critical findings are upgraded promptly; anything that cannot be upgraded is documented with a compensating control.

Separation of environments

Preview and production run as separate deployments with separate credentials. Production personal data is not copied into preview.