Remove MAD / eMAD terminology from all user-facing copy

- index.html: 'eMAD Host' -> 'Modular Agent Host' on platform card
- pluggable-agents.html: rewrite eMAD language as 'modular agent'; rename display package names to google-workspace-agent / microsoft-365-agent
- agent-platform.html: swap 'A single MAD fronts' -> 'A single service fronts' in Development Cache; display name on card slug is 'modular-agent-host'

Repo URL rmdevpro/emad-host remains in the install snippet as a factual pointer until the repo itself is renamed.

Author: rmdevpro

index.html

@@ -252,7 +252,7 @@ <h3>Blueprint Agentic Workbench</h3>
       <a class="os" href="open-source/agent-platform.html">
         <span class="k">Platform</span>
         <h3>Agent Platform</h3>
-        <p>Context Broker for durable conversational memory. eMAD Host for hot-pluggable agent orchestration. Run one or both.</p>
+        <p>Context Broker for durable conversational memory. Modular Agent Host for hot-pluggable agent orchestration. Run one or both.</p>
         <div class="tech">Python · LangGraph · Postgres · Neo4j</div>
       </a>
       <a class="os" href="open-source/pluggable-agents.html">

open-source/agent-platform.html

@@ -88,7 +88,7 @@ <h3>Context Broker</h3>
         <p>The memory layer.</p>
       </a>
       <a class="package-card" href="#modular-agent-host">
-        <div class="head"><span>emad-host</span><span class="v">Beta</span></div>
+        <div class="head"><span>modular-agent-host</span><span class="v">Beta</span></div>
         <h3>Modular Agent Host</h3>
         <p>The runtime.</p>
       </a>
@@ -274,7 +274,7 @@ <h2>Development Cache</h2>
       <p>A unified external-dependency cache — one wall between your agentic ecosystem and the public package ecosystem. Transparent proxies for PyPI, NPM, and Docker images mean every build, every container, every agent runtime pulls through a cache you control, not the open internet.</p>
 
       <h3>Three Proxies, One Surface</h3>
-      <p>A single MAD fronts three caching backends: <b>devpi</b> for PyPI, <b>Verdaccio</b> for NPM, and a private <b>Docker Registry 2.0</b> for images. Agents and CI pipelines configure a couple of environment variables — <code>PIP_INDEX_URL</code>, <code>NPM_CONFIG_REGISTRY</code>, and the Docker daemon's <code>insecure-registries</code> — and all dependency traffic flows through the cache, invisibly.</p>
+      <p>A single service fronts three caching backends: <b>devpi</b> for PyPI, <b>Verdaccio</b> for NPM, and a private <b>Docker Registry 2.0</b> for images. Agents and CI pipelines configure a couple of environment variables — <code>PIP_INDEX_URL</code>, <code>NPM_CONFIG_REGISTRY</code>, and the Docker daemon's <code>insecure-registries</code> — and all dependency traffic flows through the cache, invisibly.</p>
 
       <h3>Offline-Capable Builds</h3>
       <p>Once a package is cached, subsequent builds don't need the internet at all. Pre-warming tools seed the caches from a <code>requirements.txt</code> or a <code>package.json</code>, so a new host, a fresh container, or a disconnected environment comes online already holding everything it needs. This is the supply-chain wall — fast, repeatable, auditable.</p>
@@ -369,8 +369,8 @@ <h2>Run it yourself.</h2>
 <span class="cmd">cd</span> context-broker &amp;&amp; <span class="cmd">docker compose up</span> -d
 
 <span class="comment"># Modular Agent Host</span>
-<span class="cmd">pip install</span> emad-host
-<span class="cmd">emad-host</span> --config config.yaml</div>
+<span class="cmd">git clone</span> https://github.com/rmdevpro/emad-host.git
+<span class="cmd">cd</span> emad-host &amp;&amp; <span class="cmd">docker compose up</span> -d</div>
       <p>Full documentation in each repository. Additional services ship as they reach beta.</p>
     </div>
   </div>

open-source/pluggable-agents.html

@@ -60,15 +60,15 @@
     <div class="kicker">§ Agents · Open source</div>
     <h1>Pluggable Agents.</h1>
     <p class="tagline">Drop-in agents for the services your business already runs on.</p>
-    <p class="sub">Every eMAD (ephemeral Modular Agent Daemon) is a Python package that plugs into an eMAD Host. Install it, the Host picks it up, and agents get new capabilities — no downtime, no monolithic redeploy. Two agents are currently published.</p>
+    <p class="sub">Every agent here is a Python package that plugs into the Modular Agent Host. Install it, the Host picks it up, and agents get new capabilities — no downtime, no monolithic redeploy. Two agents are currently published.</p>
     <div class="two-package">
       <div class="package-card">
-        <div class="head"><span>google-workspace-emad</span><span class="v">v0.2</span></div>
+        <div class="head"><span>google-workspace-agent</span><span class="v">v0.2</span></div>
         <h3>Google Workspace</h3>
         <p>Gmail · Drive · Docs · Sheets · Slides · Calendar. 30+ tools.</p>
       </div>
       <div class="package-card">
-        <div class="head"><span>microsoft-365-emad</span><span class="v">v0.2</span></div>
+        <div class="head"><span>microsoft-365-agent</span><span class="v">v0.2</span></div>
         <h3>Microsoft 365</h3>
         <p>Outlook · Calendar · OneDrive. 15+ tools via Microsoft Graph.</p>
       </div>
@@ -81,7 +81,7 @@ <h3>Microsoft 365</h3>
     <div class="lbl">§ 01 · Google Workspace</div>
     <div>
       <h2>Full Google Workspace, agent-accessible.</h2>
-      <p>Gmail, Drive, Docs, Sheets, Slides, and Calendar — all callable by agents via a single registered eMAD. Service-account authentication with domain-wide delegation means agents act on behalf of real users, safely.</p>
+      <p>Gmail, Drive, Docs, Sheets, Slides, and Calendar — all callable by agents via a single registered modular agent. Service-account authentication with domain-wide delegation means agents act on behalf of real users, safely.</p>
 
       <h3>Capabilities</h3>
       <div class="caps-grid">
@@ -135,9 +135,9 @@ <h2>Install and the host picks it up.</h2>
     <div class="lbl">§ 04 · Install</div>
     <div>
       <h2>Run them yourself.</h2>
-      <div class="code"><span class="comment"># Requires eMAD Host already running</span>
-<span class="cmd">pip install</span> google-workspace-emad
-<span class="cmd">pip install</span> microsoft-365-emad
+      <div class="code"><span class="comment"># Requires Modular Agent Host already running</span>
+<span class="cmd">pip install</span> google-workspace-agent
+<span class="cmd">pip install</span> microsoft-365-agent
 
 <span class="comment"># Restart not required — host discovers on install</span></div>
       <p>Documentation for each agent lives in its repository.</p>
@@ -148,7 +148,7 @@ <h2>Run them yourself.</h2>
     <div class="lbl">§ 05 · Build your own</div>
     <div>
       <h2>Agents for your stack, too.</h2>
-      <p>If you need an agent for <b>Slack, Jira, SharePoint, Salesforce, ServiceNow</b>, or your internal APIs — we build those as standard engagements. The eMAD pattern makes it straightforward. The typical agent ships in a week or two depending on API complexity.</p>
+      <p>If you need an agent for <b>Slack, Jira, SharePoint, Salesforce, ServiceNow</b>, or your internal APIs — we build those as standard engagements. The modular-agent pattern makes it straightforward. The typical agent ships in a week or two depending on API complexity.</p>
       <p style="margin-top:1rem"><a class="link" href="../index.html#contact" style="color:var(--accent); border-bottom:1px solid var(--accent); padding-bottom:2px; font-weight:500;">Talk to us →</a></p>
     </div>
   </div>