docs: roll out maa_exec activation without forking the network

[MicBun]

Gives operators a safe, repeatable procedure for activating the maa_exec route (Modular Agent Addresses) on a running network, and pins kwil-db to the main that ships the activation gate.

What this does

• docs/maa-rollout.md — the coordinated rollout runbook. The rollout is two-phase by construction: Phase 1 upgrades the fleet with a hash-neutral binary (the maa_activation_height parameter is invisible to consensus while unset, so a mixed-version fleet cannot fork); Phase 2 schedules activation on-chain with the stock kwild consensus propose resolution — the only consensus-visible event. The runbook covers the load-bearing ordering rule (never propose while old binaries run — they cannot decode the parameter name), measuring the real block rate to map a lead time to an activation height, the single-validator shortcut, re-scheduling, the straggler story (old binaries halt cleanly on header validation instead of forking), and why there is no binary rollback past the activation height.
• kwil-db pin bump to v0.10.3-0.20260611144500-9fab49f49c4a (both modules) — picks up the activation parameter, the mempool + PreTx gates, and the 3-validator rollout rehearsal:
  • chore: hold maa_exec until a network-scheduled activation height kwil-db#1710
  • test: rehearse the maa activation rollout on a real network kwil-db#1711
• Cross-link from docs/modular-agent-addresses.md to the runbook.

[coderabbitai]

Warning

Review limit reached

@MicBun, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 7 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: e4ea2cf9-da84-40f0-a194-cd6de0c98500

📥 Commits

Reviewing files that changed from the base of the PR and between 5972db5 and f197d43.

⛔ Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

📒 Files selected for processing (3)

• docs/maa-rollout.md
• docs/modular-agent-addresses.md
• go.mod

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/maa-rollout

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[holdex]

Time Submission Status

Member	#	Time	Running Total	Status	Last Update
MicBun			2h	✅ Submitted	Jun 11, 2026, 2:52 PM

---

Submit or update total time with:

@holdex pr submit-time 2h

Add time on top of previous submission with:

@holdex pr add-time 1h30m

See available commands to help comply with our Guidelines.

[MicBun]

@holdex pr submit-time 2h