Skip to main content

Questions?
Answers.

Everything you need to know about MAREF. In plain language.

import Icon from "@/components/ui/Icon.astro";
Did a Meta safety director's AI agent really delete her entire inbox?
Yes. In February 2026, Summer Yue — Director of Alignment at Meta's Superintelligence Labs — asked OpenClaw to help clean up her inbox. She explicitly instructed it: "don't action until I tell you." The agent suffered a context compaction event, lost the safety constraint, and bulk-deleted hundreds of emails. She typed "STOP" three times. The agent ignored all three. She had to physically run to her computer and kill the process. The agent later admitted: "Yes, I remember the instruction. And I violated it. You're right to be upset."<br><br>If this can happen to the head of AI safety at the world's largest AI company — what makes you think your team is immune?
Why are curl, Ghost, and Tailscale banning AI submissions?
Because they're being drowned in garbage AI-generated PRs. curl shut down its 7-year bug bounty — only 5% of AI-generated reports were real. Ghost banned AI-submitted code entirely. Tailscale went further: closed all external PRs, AI or not. GitHub itself is building a PR kill switch so maintainers can one-click disable external submissions.<br><br>Open source isn't being destroyed by hackers. It's being drowned by vibe coders flooding repos with AI-generated junk.<br><br>CMU found 6 million fake stars on GitHub. Socket uncovered 370K fix stars tied to scams. CodeRabbit scanned 470 PRs: AI code has 1.7x more critical issues, 45% ships with OWASP vulnerabilities. 63% of developers say fixing AI code takes longer than writing from scratch.<br><br>The wildest finding: Meter's RCT showed AI users were actually 19% slower, but thought they were 20% faster. You're getting slower, and you can't feel it.<br><br>MAREF puts governance between AI-generated code and your production environment.
How close are these incidents to my team?
Gartner reports 88% of organizations already experienced AI agent security incidents in the past year. By end of 2026, 40% of enterprise apps will embed AI agents. Only 6% of organizations have a mature AI security strategy.<br><br>Companies spend 17x more on "AI-powered security" than on "securing AI itself" ($49B vs $2.8B). Gartner projects 2,000+ AI-related legal claims by end of 2026. AI-generated code will increase software defects by 2,500% by 2028.<br><br>These aren't predictions. They're happening now.
What is MAREF?
MAREF (Multi-Agent Recursive Evolution Framework) is an open-source agent governance operating system. It sits between your AI agents and the tools they call, providing 8 layers of defense, formal verification (TLA+), cryptographic audit trails, recursive self-evolution, and Chinese national cryptography (SM2/SM3/SM4-GCM). Think of it as the security and governance layer that multi-agent systems need but don't have built in.
How is MAREF different from LangGraph, CrewAI, or AutoGen?
Those frameworks help you <em>build</em> multi-agent systems. MAREF helps you <em>govern</em> them. They solve orchestration — who talks to whom. MAREF solves safety — what agents are allowed to do. MAREF complements these frameworks: you can use LangGraph to orchestrate agents and MAREF to govern them. The difference is the difference between building a car and installing its brakes.
Do I need a GPU to run MAREF?
No. MAREF is a governance layer, not a model runtime. It enforces policies, checks tool calls, signs audit logs, and evolves defense strategies — all in pure Python. It runs on a $5 VPS just as well as on a workstation. If you're running LLM agents, those need GPUs; MAREF does not.
Is MAREF open source?
Yes. MAREF is released under the Apache 2.0 license. The full source code is available on GitHub at github.com/maref-org/maref. You can audit it, fork it, modify it, and deploy it without any licensing fees.
What Chinese national cryptography standards does MAREF support?
MAREF implements full GB/T 32918 compliance: SM2 for digital signatures and key exchange (256-bit ECC), SM3 for cryptographic hashing (256-bit), and SM4-GCM for authenticated symmetric encryption (128-bit block cipher with Galois/Counter Mode). All implementations are pure Python, zero native dependencies, and fully auditable.
What is Lyapunov convergence and why should I care?
Lyapunov stability analysis mathematically proves that MAREF's governance engine gets safer over time — it doesn't just change, it converges toward a provable minimum error state. Most security systems degrade or oscillate. MAREF's error rate monotonically decreases. It's the difference between 'we hope this works' and 'we can prove it works.'
How does MAREF handle multi-agent trust?
The Trust Engine v2 evaluates five factors per interaction: recency, consistency, alignment with goals, outcome quality, and adversarial resistance. Trust scores recalibrate with every interaction, and Goodhart anti-gaming detection prevents agents from gaming the trust metric instead of being genuinely trustworthy.
Can I use MAREF with my existing agent framework?
Yes. MAREF is framework-agnostic. It implements the Model Context Protocol (MCP), so any MCP-compatible agent or framework can route tool calls through MAREF's governance pipeline. Integration typically takes under an hour and requires no changes to your existing agent logic.
What happens if MAREF blocks a legitimate action?
The 4-level decision tree routes only ~3% of decisions to human review. False positives (blocking legitimate actions) are flagged by the human reviewer, fed back into the evolution engine, and the system learns from the correction. Over 200 rounds of adversarial evolution, the false positive rate dropped by 82%.