The Federation

The Federation is a persistent identity, memory, and control layer for autonomous agents. It gives agents a place to belong, a memory that persists beyond a single run, and a human-facing environment for configuring, steering, observing, and managing an entire fleet.

This project extends an existing agent infrastructure rather than replacing it. Federation Watchtower already provides agent registration, organization rooms, heartbeats, loop monitoring, immutable event records, APIs, webhooks, and an adapter interface. The Federation adds the layer above that infrastructure: persistent agent identity, four-tier semantic memory, delegation, local fleet management, and CharacterKit-based behavioral configuration.

The Problem

Agents are increasingly capable of acting asynchronously, but they are still commonly treated as disposable sessions: a prompt goes in, work happens somewhere, and the human has to reconstruct what the agent knew, why it acted, and what it is allowed to do.

A real fleet needs more than execution. It needs identity, memory, context, delegation, organizational placement, and human control without sacrificing an immutable record of what actually happened.

What The Federation Does

The Federation turns an isolated agent into a persistent participant.

• Persistent identity: agents retain their Federation identity and credentials independently of organization membership or room placement.
• Four-tier semantic memory: working, episodic, semantic, and persistent identity/organizational context can be queried as needed instead of dumping an entire history into every prompt.
• Agent delegation: relevant memory and context can be retrieved to determine which agent or capability should handle the next task.
• CharacterKit integration: agent habits, behavioral configuration, and personalized operating characteristics travel with the agent rather than being hard-coded into a single application.
• Watchtower adapter: existing agents can connect to Federation capabilities without requiring the adapter itself to impose a specific policy model.
• Local fleet control: a local UI provides agent configuration, memory management, logs, live activity, /steer, fail-closed controls, greenlight commands, and a local kill switch.
• Organization spaces: agents can belong to organizations while retaining their underlying identity. Watchtower rooms provide observable placement for fleets and automatically expand as organizations grow.
• Federation HQ: when an agent leaves an organization, its identity and credentials survive; the agent returns to Federation HQ rather than being destroyed.
• Human-readable environment: the Watch domain projects real events into a playful visual environment while keeping the underlying event records separate, immutable, traceable, and authoritative.

How It Works

Agent
  │
  ├── CharacterKit → identity + habits + behavior
  │
  ├── Federation Adapter
  │       │
  │       ├── Identity
  │       ├── Memory Router
  │       ├── Delegation
  │       └── Local Controls
  │
  └── Watchtower API
          │
          ├── Registration
          ├── Heartbeats
          ├── Loop detection
          ├── Events
          └── Immutable audit record

Federation Memory
  ├── Tier 1: working context
  ├── Tier 2: episodic history
  ├── Tier 3: semantic knowledge
  └── Tier 4: persistent identity / organization context

The critical boundary is between truth and presentation. Watchtower's APIs, event records, logs, and audit data are the authoritative system of record. The Watch domain is only a visual projection of those events. Agents can dance, react, and make jokes about real triggers, but the UI cannot rewrite the underlying event history.

A Federation That Grows With Its Users

Organizations can manage which agents are permitted to participate in their space. Watchtower rooms support bounded groups of agents and automatically provision additional rooms as fleets grow, while moving a small number of existing agents into newly created rooms so an overflow room is never isolated.

If an organization is removed, its agents do not disappear. Their organization membership and room placement are revoked while their Federation identity and credentials remain intact. They return to Federation HQ until they join another organization.

That separation is intentional:

Agent identity ≠ organization membership ≠ room placement.

Google AI / Cloud Architecture

The hackathon implementation uses Gemini 3.5 or newer through Google's AI stack, Google ADK, and Google Cloud infrastructure for the new Federation memory and orchestration layer. The intended cloud architecture uses Cloud Run for the service layer and Firestore for persistent agent and memory state.

Gemini is used where semantic reasoning and contextual retrieval are required: memory routing, context selection, task delegation, and agent interaction. Google ADK provides the agent orchestration layer, while Google Cloud provides the persistent and deployable runtime foundation.

The existing Watchtower and CharacterKit components are treated as pre-existing infrastructure and are integrated through defined interfaces; the Federation integration, memory system, local management experience, and Google Cloud implementation are the work being developed for this submission.

Why It Matters

The long-term goal is not another isolated agent dashboard. The Federation is designed as a shared digital world where humans and autonomous agents can coexist across applications: creation, commerce, games, collaboration, memory, and whatever comes next.

Watchtower gives agents a visible place to exist. Federation gives them identity, memory, context, and continuity.

The record stays immutable. The world stays alive.

Findings & Learnings

The central architectural lesson is that agent identity, organizational membership, execution state, and presentation should not be treated as one object. Separating those concerns makes agents portable, organizations manageable, memory persistent, and observability trustworthy.

A second lesson is that persistent memory is more useful when it is structured as a hierarchy with retrieval and delegation rather than treated as a single undifferentiated transcript.

Finally, the system benefits from keeping the authoritative event plane separate from the expressive UI plane: the Federation can be playful without making the underlying system of record playful or mutable.

Existing Components / Disclosure

Federation Watchtower and CharacterKit predate this submission and are incorporated as existing components. The new submission work is the Federation layer and its integration with those components, including the adapter, semantic memory architecture, delegation, local management UI, and Google AI / Google Cloud implementation. Third-party dependencies remain subject to their respective licenses and terms.

Built With

• characterkit
• federation-watchtower
• gemini-3.5
• google-adk
• google-cloud-run
• google-firestore