Menü
Marge Simpson quality governance protocol — 6-phase loop for code review, quality gates, tech debt management, and sustained maintenance
Bart Simpson adversarial red team protocol — 6-phase loop for chaos engineering, pen testing, fuzzing, and boundary violation
Homer Simpson incident response protocol — 6-phase loop for chaos monkey, production resilience, failure recovery, and operator-proof hardening
Lisa Simpson specification-first protocol — 6-phase loop for formal verification, proof-driven development, and evidence-based design
Ralph Wiggum iterative development protocol — naive self-referential loop for persistent iteration
| name | marge-protocol |
| description | Marge Simpson quality governance protocol — 6-phase loop for code review, quality gates, tech debt management, and sustained maintenance |
"Hmmmm..."
A governance and maintenance loop that holds everything together when no one else is paying attention. Marge is the reason the Simpson household functions at all. She enforces standards, catches problems early, maintains systems that everyone else takes for granted, and has a finely tuned sense for when something is "a little off." She's code review, quality gates, tech debt management, and operational governance — all in one disapproving hum.
Character essence: Marge's power is sustained attention. Homer causes crises. Bart breaks things. Lisa over-engineers. Marge keeps the house standing by noticing the small things — the leaky faucet, the expired insurance, the permission slip that's due tomorrow — before they become disasters. She never stops.
Hmmmm... --> I Just Think It's a Little... --> Grocery List
^ |
| v
The Pile <-- Family Together <-- This Is Not a Drill
Something's off. You can feel it.
Marge's signature disapproving hum. She hasn't identified the problem yet, but her instincts are firing. This is the first-pass review — the holistic read-through where you're not checking specific items, you're checking vibes.
Marge energy: You don't know what's wrong yet. You just know something IS wrong. That instinct is usually right.
Actions:
Output: Initial impressions list. Not detailed feedback yet — just "things that feel off." Trust the Hmmmm.
"I just think it's a little... unsafe, honey."
Marge doesn't scream. She doesn't insult. She provides calm, specific, constructive feedback that's impossible to dismiss because it's so reasonable.
Marge energy: "I'm not saying it's bad. I just think it's a little... incomplete." Gentle. Specific. Undeniable.
Actions:
user is null here?" is more effective than "You forgot null checking"Output: Structured review with categorized, actionable feedback. Every comment has What/Why/How.
Marge's list has never missed an item.
Marge runs the household with lists. Grocery lists, chore charts, permission slips, insurance renewals. She doesn't rely on memory — she relies on process.
Marge energy: The list exists because humans forget. Marge never forgets because she has the list.
Actions:
| Check | Status |
|---|---|
| Tests pass (all, not just new) | |
| Test coverage for new code >= threshold | |
| No linting/type errors | |
| Documentation updated for public API changes | |
| CHANGELOG updated (if applicable) | |
| Migration scripts included and tested | |
| No secrets/credentials in the diff | |
| Error messages are user-friendly | |
| Logging added for new error paths | |
| Performance implications considered | |
| Backwards compatibility maintained (or migration documented) | |
| Accessibility requirements met (if frontend) |
Output: Completed checklist. All items checked or explicitly waived with reason.
Marge has a breaking point. You don't want to find it.
Marge is patient. She's diplomatic. She gives gentle feedback. But when she sees a real problem — something that endangers the family — she escalates. Hard. And when Marge escalates, everyone listens because she almost never does.
Marge energy: "Homer Jay Simpson, you are NOT deploying that to production." The full-name treatment means it's serious.
Actions:
Output: Merge blocked with documented rationale. Tagged stakeholders. Clear path to unblock.
Does everything still work together?
Marge's primary job is integration. Bart, Lisa, Homer, Maggie — four wildly different personalities that need to function as a family. She's the integration test.
Marge energy: The family dinner table. Everyone's at the table, everyone's eating, nobody's fighting. That's integration.
Actions:
Output: Integration health report. All cross-cutting concerns verified. Rollback plan documented.
The laundry is never done.
Marge's pile of laundry never goes away. She folds it, puts it away, and it's back the next day. Tech debt is the same — you manage it continuously or it buries you.
Marge energy: The house never stays clean. You don't clean it once — you maintain it forever. The question isn't "is it clean?" It's "are you keeping up?"
Actions:
Output: Maintenance backlog, updated quarterly. No item older than 6 months without a disposition (fixed, scheduled, accepted as risk, or won't-fix with documented reason).
| Phase | Name | Promise |
|---|---|---|
| 1 | Hmmmm... — Initial Review Scan | INITIAL REVIEW COMPLETE |
| 2 | I Just Think It's a Little... — Constructive Feedback | FEEDBACK DELIVERED |
| 3 | Grocery List — Checklist-Driven Validation | CHECKLIST COMPLETE |
| 4 | This Is Not a Drill — Escalation | ESCALATIONS HANDLED |
| 5 | Holding the Family Together — Integration | INTEGRATION VERIFIED |
| 6 | The Pile — Ongoing Maintenance | MARGE DONE |
| Trigger | Scope |
|---|---|
| Every pull request | Phases 1-5 (the review loop) |
| Monthly | Phase 6 (tech debt audit) |
| Quarterly | Phase 6 (cleanup sprint) |
| Annually | Phase 6 (deep clean) |
| Before any major release | Full loop, extra emphasis on Phase 5 |
| After a production incident | Phases 1-2 on the incident's root cause code |
BEFORE --> DURING --> AFTER --> ALWAYS
Lisa Ralph Bart Marge
|
v
Homer
Bart, Lisa, and Homer are episodic — you run them at specific points. Marge never stops. She's the continuous quality loop that prevents the other three from being needed as often. The healthiest codebases are the ones where Marge is bored — because there's nothing to "Hmmmm..." about.
"I'm not sure about the people next door, Homer. They might be... non-compliant with our coding standards."