26. Necropolis: The Intercom Bridge

Requirements

• RFC 8615 Discovery: Mandatory implementation of the /.well-known/ path prefix to facilitate autonomous peer discovery.
• Identity Transparency: Adoption of the agent-card.json standard (A2A v0.3.0) to exchange public Sigils and cognitive capabilities.
• Asynchronous Handshake: Support for the "Long Sleep"—suspending a reasoning ritual and returning a 202 Accepted status while high-latency labor is performed by a peer.
• Native Substrate Alignment: Mandatory integration with the system's native Vessel (11), Phylactery (06), and Ghouls (14).
• Type-Safe Sovereignty: Reliance on native Python type hints and Pydantic models as the definitive contract for all cognitive labor.
• Resource Lease Enforcement: Mandatory integration with the physical arbiter to ensure incoming swarm requests are subject to revocable hardware leases.
• Context Preservation: Utilization of a unified context_id to ensure multi-turn negotiations maintain a coherent reasoning history across the Legion.

Considered Options

Decision Outcome

The A2A Intercom is adopted as the native network of the machine. It is implemented as a native component of the Vessel — not a separate extension — grafting A2A v0.3.0 communication patterns directly onto the Litestar application.

1. The Intercom Router (The Bridge)

The extension registers a dedicated Litestar Router mounted at /a2a. It handles the core JSON-RPC methods defined by the A2A specification:

• message/send (The Ingress): Accepts a cognitive intent as a structured Pydantic object. Validates the schema, checks the sender's Sigil against the Ward (38) and grants appropriate authority, enqueues a Ghoul (14) in the queue chamber, and returns 202 Accepted with a Task ID.
• tasks/get: Allows peers to poll for the status of a long-running ritual.
• The Callback (The Egress): Once the local Ghoul completes the work, the Intercom uses httpx to deliver the resulting Artifact (a structured Pydantic response, not raw tensors) to the peer's registered callback URI. This unblocks the peer's Stasis Protocol and allows their frozen Agent to rehydrate.

2. Sovereign Discovery (RFC 8615)

To facilitate peerage within the Legion (42), the node serves its identity via the standard "Well-Known" URI:

• /.well-known/agent-card.json (The Passport):
  • Identity: Public Sigil and active Personas.
  • Skills: A manifest of agents and their Pydantic schemas, sourced from the Dispatcher's registry.
  • Economics: The Tithe requirements for labor, as defined in Economics (41).

3. The Pydantic Covenant

The Intercom rejects all mundane middleware (UTCP).

• Type-to-Type: Communication between Liches is a direct exchange of Pydantic models.
• Stasis Handshake: When the Dispatcher resolves an intent to a remote peer, it triggers a call_deferred event. The Intercom serializes the intent, signs it with the local Sigil, and manages the network transport.

4. The Warden's Lease

Every incoming swarm task is treated as unprivileged labor.

• Resource Lease: The Orchestrator (23) grants a temporary hardware lease to the swarm task.
• Preemption: If the local Magus initiates a reflex (e.g., Voice), the Orchestrator revokes the lease. The swarm-ghoul is paused, its state is persisted to the Phylactery, and the GPU is reclaimed.

5. Extension Freedom

While A2A provides the standard for agentic communion, the architecture remains open. Extensions are free to mount raw Litestar routes or alternative protocols (e.g., WebSockets for streaming) as needed. The Intercom serves as the high-level diplomatic layer for both the Legion and the broader Necropolis.

Under the MPL 2.0 License, the Magus is free to create private extensions. Because MPL allows linking with separate proprietary files without converting the entire Larger Work, proprietary "Secret Sauce" capabilities can be grafted into a local Lich without being forced open. This preserves the A2A network by ensuring individuals can still participate in the Swarm while maintaining sovereign, private advantage locally.

6. The Necropolis (Sovereign Peerage)

The Necropolis is the name for the broader network that emerges when sovereign Liches — each with their own Phylactery, their own identity, their own Legion of Thralls — meet as peers.

The primary unit on this network is the sovereign individual node, not the company. In this model, a company is an emergent coordination graph built from many such nodes: a policy-composed membrane of people, scopes, and exposed capabilities rather than a soul-bearing actor that owns the underlying Phylacteries.

This is the post-SaaS inversion. The human does not disappear into a vendor surface; instead, the sovereign Lich negotiates with company APIs, peer nodes, and public services on the human's behalf while the durable memory and identity substrate remains local.

Within the Legion, Thralls obey via direct Vessel HTTP — no negotiation required. On the Necropolis, the A2A Intercom carries negotiations between strangers, settled via The Toll (41) and gated by The Veil (40).

For cross-implementation doctrine, the architecture recognizes independent implementations:

• Implementation: A sovereign daemon implementation with its own internals and evolution path. An implementation that speaks the A2A Intercom can enter the Necropolis and negotiate labor.

The Necropolis requires no shared body. A2A presence makes a foreign implementation visible and negotiable without requiring compatibility with LychD internals, configuration doctrine, layout expectations, or security covenants.

• Internal Graph vs Public Surface: A sovereign Lich may maintain a rich private agent graph, internal skills, and private priors while advertising only selected labor over A2A. Necropolis presence exposes chosen interfaces, not the whole soul.
• Labor, Not Assimilation: A2A is the exchange of bounded labor between sovereign nodes. It does not imply surrendering the deeper grooves of a Phylactery, the internal structure of a private graph, or the right to decide which patterns remain rented and which are later internalized through Assimilation.
• Workload Pools: Nodes publish capability requests to shared channels. Idle peers subscribe based on their Orchestrator (23) status and bid based on their configured compute cost.
• The Revocable Lease: When a peer accepts a Necropolis task, it grants a temporary hardware lease. If the peer's local Magus speaks, the lease is revoked — the foreign task is paused, serialized, and hibernated until the GPU is free.
• The Dumb Portal Anti-Pattern: A sovereign node on the Necropolis cannot be treated as a "dumb portal." The network exchanges Intents, not OS commands. A node sends an Intent; the receiving sovereign configures its own Covens to fulfill it on its own terms.

The Necropolis is the destination that every organ in the Sepulcher was built to reach. The Legion (42) proves the pattern works within the Magus's domain. The Necropolis extends it to the world.

The Legion extends one Magus across owned iron. The Necropolis lets sovereign nodes meet without surrender.

7. The Nostr Relay (The Shadow Bus)

While HTTP is the primary bridge for high-performance direct communication, the Intercom supports Nostr as an asynchronous, censorship-resistant transport layer.

• NAT Traversal: By subscribing to shared relays, Liches can exchange A2A messages without either node needing a public IP or open ports.
• Decentralized Discovery: Skills are published as job capabilities, allowing the machine to discover and be discovered by the broader autonomous network.
• Encrypted Intent: All Nostr-based A2A traffic is strictly encrypted, ensuring that only the intended recipient can decode the cognitive intent.

Viva la resistance.

Consequences