Decision (Max, #macro 2026-07-16): the suite is named PolicyEngine Macro. It is built for PolicyEngine specifically, so it lives under the PolicyEngine name rather than a coined brand — unlike Populace and Ledger, which have standalone relevance beyond PolicyEngine.
No urgency on infrastructure renames (repo slug, macromod.vercel.app, the macromod CLI/MCP names can roll whenever convenient — GitHub redirects make the repo rename cheap), but new copy should say PolicyEngine Macro:
- Site: hero/title/meta, footer, docs, connect page ("MacroMod" → "PolicyEngine Macro"; the positioning line should read as PolicyEngine's macro suite, not a standalone platform).
- README first line + site link line.
- MCP server display name and CLI
--help text when touched.
Suggested sequencing: fold copy changes into the next site pass rather than a dedicated sweep; rename the repo + Vercel project in one coordinated change later (update the MCP deploy workflow, connect-page install snippets, and pip git+ URLs in the same PR).
Decision (Max, #macro 2026-07-16): the suite is named PolicyEngine Macro. It is built for PolicyEngine specifically, so it lives under the PolicyEngine name rather than a coined brand — unlike Populace and Ledger, which have standalone relevance beyond PolicyEngine.
No urgency on infrastructure renames (repo slug, macromod.vercel.app, the
macromodCLI/MCP names can roll whenever convenient — GitHub redirects make the repo rename cheap), but new copy should say PolicyEngine Macro:--helptext when touched.Suggested sequencing: fold copy changes into the next site pass rather than a dedicated sweep; rename the repo + Vercel project in one coordinated change later (update the MCP deploy workflow, connect-page install snippets, and pip
git+URLs in the same PR).