Blog · methodology, evidence, experiments

Writing from the project.

Long-form notes on ad-ops methodology, security posture, and what we've learned running mureo against real accounts. Evidence-based and data-forward; no hype, no lists of five tips.

    • architecture
    • knowledge
    • federation

    Insight federation: how mureo borrows practitioner know-how without leaking it

    mureo 0.9.19 ships `mureo_consult_advisor`, a federated retrieval surface that lets diagnostic agents pull practitioner know-how from external advisor servers without anyone shipping their corpus out. This post explains the v0.9.18 design that leaked and the v0.9.19 retrieval pattern that does not.

    • architecture
    • plugin-architecture
    • positioning

    mureo as a control plane: the plugin architecture in 0.9.x

    mureo 0.9 ships in ten releases that together rebuild the framework as a pluggable control plane: a stable Capability+Protocol ABI, entry-points discovery, an ABI stability promise, configure-UI web extensions, and a safety layer that wraps every third-party plugin tool. This post walks the architecture and explains why this shape matters once the official ad-platform MCPs ship.

    • evaluation
    • demo
    • workflows

    Try mureo without an ad account: anatomy of `mureo demo init`

    mureo 0.8.0 ships four synthetic scenarios that let an evaluator run the agent end-to-end without OAuth, an XLSX bundle, or even a real ad account. This post unpacks what each scenario is designed to surface and why a synthetic dataset is the right shape for evaluating ad-ops AI.

    • open-source
    • governance
    • positioning

    Open source ad ops: an Apache 2.0 commitment

    Why mureo is open source under Apache 2.0, what stays on the operator's machine, what the project will not do, and what that means for agencies and in-house teams evaluating long-term risk.

    • workflows
    • methodology

    Anatomy of /daily-check

    What mureo does when an operator types a single three-word command: four-platform data pull, strategy binding, anomaly detection, and a single correlated report — with a walkthrough of the manual equivalent.

    • workflows
    • deployment
    • multi-tenancy
    • docker

    Running mureo as a sidecar container

    When the local pip install is not the right fit — CI runs, agency multi-tenancy, non–Claude Code MCP clients — the new Dockerfile gives mureo a sidecar shape without giving up the local-first credential posture.

    • strategy
    • methodology
    • positioning

    Strategy-driven vs metric-driven optimization

    Why metric optimization alone misallocates spend, what lives in STRATEGY.md, and a worked example where two accounts with identical numbers require opposite actions.

    • security
    • threat-model
    • methodology

    The threat model of AI agents touching ad accounts

    Where ad-ops AI agents can be exploited — prompt injection, credential exfiltration, unbounded mutations — and the four mechanisms mureo uses to contain the blast radius.

    • methodology
    • anomaly-detection
    • anti-pattern

    How AI agents misdiagnose CPA spikes

    Why naive threshold alerts on ad cost-per-acquisition fail at the point they are most needed — and the three mechanisms mureo uses to fire only on signal.

New posts land weekly. Subscribe via RSS.