◎ OS PUB Apache 2.0 ← All specifications

P260 — AIEP — Multi-AIEP Node Discovery and Federation Bootstrap

Publication Date: 2026-04-12 Status: Open Source Prior Art Disclosure Licence: Apache License 2.0 Author/Organisation: Phatfella Ltd Schema: AIEP_OS_SPEC_TEMPLATE v1.0.1 — https://aiep.dev/schemas/aiep-os-spec-template/v1.0.1

Field of the Invention

[0001] The disclosure relates to peer discovery and federation bootstrap mechanisms for distributed networks of AI systems.

[0002] More particularly, the disclosure concerns a multi-AIEP node discovery and federation bootstrap protocol, defining how individual AIEP deployment nodes locate, authenticate, and establish governed federation relationships with peer nodes to form a multi-node AIEP federation.

Framework Context

[0003] This invention operates within an Architected Instruction and Evidence Protocol (AIEP) environment as defined in United Kingdom patent application number GB2519711.2, filed 20 November 2025, the entire contents of which are incorporated herein by reference.

Summary of the Disclosure

[0004] A computer-implemented multi-AIEP node discovery and federation bootstrap protocol comprises: defining a NodeIdentityRecord for each AIEP deployment node containing: node_id (globally unique), node_public_key, operator_authority_id, deployment_jurisdiction, supported_protocol_versions, and federation_capability_flags; a DiscoveryMechanism supporting: (i) static seed lists of known peer nodes; (ii) DNS-based AIEP node discovery records; (iii) authorised federation registry lookups; authenticating discovered peers by verifying node_public_key signatures against a trusted NodeCertificateAuthority; executing a FederationHandshake comprising: protocol version negotiation, jurisdiction compatibility check, capability intersection computation, and mutual FederationConsent record generation; upon successful handshake, establishing a FederationLink record carrying: link_id, participating_node_ids, agreed_capabilities, jurisdiction_constraints, consent_timestamp, and link_status; recording all FederationLink records as immutable governance artefacts; and requiring explicit FederationLinkRevocation for any link termination, generating a signed RevocationRecord.

[0005] Federation links are consent-based and cannot be established unilaterally. Both nodes must produce FederationConsent records for a link to become ACTIVE.

[0006] The technical effect is modification of computing system behaviour by providing a governed, authenticated, consent-based node discovery and federation bootstrap mechanism enabling controlled inter-AIEP-node evidence and knowledge sharing.

Claims

[0007] A computer-implemented method for multi-AIEP node discovery and federation bootstrap comprising: maintaining NodeIdentityRecords; executing peer discovery via multiple mechanisms; authenticating peers against trusted certificate authorities; conducting FederationHandshakes with jurisdiction and capability negotiation; generating mutual FederationConsent records; establishing FederationLink records; and requiring signed RevocationRecords for link termination.

[0008] A system for multi-AIEP node discovery and federation bootstrap comprising one or more processors and a non-transitory computer-readable medium storing instructions to execute the method of claim 1.