Methodology

mureo’s core thesis is that ad operations should be strategy-driven, not metric-driven — and that the strategy layer requires a structured, inspectable body of methodology, not taste.

This section is that corpus. Each page is evergreen reference material, not time-stamped commentary. Entries land as the diagnostic knowledge base accumulates enough signal to codify a rule.

Entries

• Sample-size rules — the thresholds below which a metric shift is day-to-day noise, not a signal worth acting on. Used by every /daily-check and /rescue workflow to decide between “act” and “monitor.”

What this is not

Methodology is not blog. The blog records specific incidents, experiments, and commentary; methodology records the canonical framework those incidents are evaluated against. If a blog post’s argument depends on a methodology rule, that rule gets codified here rather than inlined into every post.

Relationship to the OSS code

Every methodology rule on this site has a corresponding implementation in the OSS codebase at github.com/logly/mureo. Each page links to the specific module it describes. Methodology is the why and when; the code is the what.