Who is "The Fixer"?

The Fixer is a rotating engineer accountable for triage and closure: broken flows on the public site, regressions in shared CSS/JS, and urgent customer-visible defects—especially when work spans content, layout, and lightweight interactivity.

Core principles

• Reliability beats feature velocity for the rotation window.
• Short loops with Support and whoever owns customer-facing Neuro Agent / comms.
• Verify fixes where users actually browse (preview first when available, then production).

Operating model

• Weekly rotation (or a cadence that matches team size).
• No silent debt: each item is fixed, delegated with an owner, or explicitly deferred with rationale.
• Escalate when the problem needs security, infra, or product expertise beyond the static site.

Responsibilities

• Keep the shared triage view honest alongside Support.
• Reproduce, patch, or assign within the SLA the team agrees on.
• Ship a minimal test plan: critical paths, theme toggle, mobile nav, links out of the changed area.
• Leave breadcrumbs: short root-cause note or follow-up issue when the story is not finished in one PR.

How the team supports The Fixer

• Post in the shared engineering triage channel with URL, expected vs actual, browser, and severity.
• Open a GitHub Issue labeled fixer (or your convention) so work is searchable and linkable from PRs.
• Reserve a little review bandwidth for small hotfixes—they compound.