Methods index

Operations, written as methods.

Four connected areas guide this publication. Notes make assumptions explicit and separate proposed checks from observed results.

Area 01

Release Engineering

Methods treat a release as a sequence of explicit decisions. The artifact, configuration, application readiness, useful request path and rollback conditions are documented together.

  • Artifact identity
  • Readiness checks
  • Release switches
  • Rollback boundaries

Area 02

Scheduled Automation

Notes examine timer semantics, execution identity, durable checkpoints, overlap and bounded retries. A scheduler starts a job; the application remains responsible for a repeatable unit of work.

  • systemd timers
  • Idempotent jobs
  • Checkpoints
  • Execution limits

Area 03

Recovery Methods

Procedures record the backup inputs, isolated restore environment, validation questions, decision points and cleanup. A successful copy operation is distinguished from restored application behavior.

  • Restore evidence
  • Runbook branches
  • Stop conditions
  • Recovery budgets

Area 04

Configuration & Signals

Configuration changes receive the same review as executable code. Signals are selected for the decisions they enable, with attention to failed observations, cardinality and alert ownership.

  • Configuration review
  • Credential boundaries
  • Actionable alerts
  • Incident evidence