Skip to content

Machinery Standardisation — Moving to Industry Standards

Date: 2026-04-27

Summary

Liflode's engineering infrastructure has been standardised to industry conventions so contractors can onboard instantly without learning bespoke systems. This follows ADR-134, which establishes that machinery (repos, ticketing, PRs, roles, processes) uses standard IT/PM conventions — no Liflode-specific flavour.

What Changed

GitHub Organisation Standards

  • .github org defaults repo created (Curious-Owl11/.github)
  • PR template with Linear issue linking
  • Issue templates (bug, feature, chore) with Linear-first workflow
  • Contributor Covenant 2.1 Code of Conduct
  • CONTRIBUTING.md with branch naming, Conventional Commits, PR process
  • SECURITY.md with disclosure policy (security@liflode.com, 48h SLA)
  • Dependabot configured (daily security, weekly version updates)

Documentation Portal

  • docs.liflode.com launched (MkDocs Material, protected by Cloudflare Access)
  • Contractor onboarding guide
  • Architecture overview with ADR index
  • Service reference pages
  • Runbooks (restic backup restore, incident response)
  • Conventions reference (branch naming, Conventional Commits, PR rules)

Linear Taxonomy

  • Migrated from custom label-based taxonomy to Linear native fields
  • State types: unstarted, started, completed, canceled (standard)
  • Blocked issues use Linear Blocked state (not wait:* labels)
  • In Review state signals Rachel's attention queue

Backup Infrastructure

  • Restic configured for C: drive + Docker volumes → Cloudflare R2
  • Restore runbook documented and tested

References