RADLAB LLC Agent Fleet Memory Federation Rollout (Onboarding)

RADLAB LLC Agent Fleet Memory Federation Rollout (Onboarding)

1. 01

   Provision the Bourdon runtime on agency-controlled infrastructure

   Complete the self-hosted runtime setup or spin up Hosted Managed at $12 USD per seat per month. Self-host keeps client memory inside infrastructure the agency already governs, which matters when a client asks where their context lives.

2. 02

   Create per-agent tokens and assign trust tiers in the Bourdon admin

   Issue a distinct token for each agent in the client fleet (Claude, Codex, Cursor, Copilot, Devin, Gemini, Hermes, GitLab) rather than one shared credential. Trust tiers let you restrict which agents can write to the federated store versus read only.

3. 03

   Point each agent's MCP config at the running Bourdon server

   Install the matching adapter or edit the MCP configuration for each tool. Do this one agent at a time and confirm the connection before moving to the next, so a broken adapter is isolated rather than masking the whole fleet.

4. 04

   Seed the per-tenant knowledge graph with client business context

   Load core context, FAQs, and SOPs into the tenant graph. This is the same configuration the $1,800 Starter Memory Setup covers at 16 hours of effort, so scope the seeding work before the retainer starts.

5. 05

   Run a cross-agent recognition test

   Write a memory entry from one agent and verify a second agent recognizes it within the client's actual workflow. Recognition-first recall should surface the fact immediately while details hydrate in the background; if recall stalls, the federation link is misconfigured.

6. 06

   Confirm tenant isolation before any second client is added

   Hosted Managed includes per-tenant isolation. Verify that a query from client A's agent returns nothing from client B's graph, and record the test result in the delivery file as evidence for the client.

7. 07

   Document the handoff and set the review cadence

   Deliver a handoff guide covering token rotation, trust-tier changes, and adapter updates. Schedule a monthly review of the memory graph so stale client context gets pruned rather than compounding across the retainer.