Skip to main content

Intercognitive Protocol

How do billions of Phygital Agents coordinate without centralized control?

The Intercognitive Foundation creates interoperable standards for physical AI, enabling coordination across decentralized systems. This is the Agent Protocol that serves as the physical instrument for robotics at scale.

Analysis | Diagrams | Innovators

Commerce Flow Connection

Intercognitive implements the same six-stage commerce flow as digital agent protocols: DISCOVER → COMMUNICATE → COMMERCE → AUTHORIZE → SETTLE → EVALUATE.

The nine pillars are the infrastructure layer of that flow for physical agents:

Commerce StageNine Pillars LayerFunction
DiscoverIdentity (pillar 1)Machine publishes self-sovereign credential via peaq DID
CommunicateConnectivity (pillar 7) + Sensors (pillar 4)Fleet signals state, environment, availability
CommerceMaps (pillar 3) + Positioning (pillar 5)Verified location enables service pricing and routing
AuthorizeFees (pillar 2)Verifiable Intent constraints applied — same eight types
SettleCompute (pillar 6) + Standards (pillar 9)Edge compute processes; interoperability rules govern settlement
EvaluateOrchestration (pillar 8)Swarm feedback — coordination quality feeds next cycle

Universal Machine Time is the prerequisite for every stage. You cannot verify position without verified time.

See Where Tracks Converge for the full digital↔physical equivalence map.

The Nine Pillars

The Foundation is developing a comprehensive standard framework:

PillarFunctionRobotics Application
IdentitySelf-sovereign passports for connected machinesKnow which robot did what
FeesPeer-to-peer transaction systemsRobots get paid for work
MapsDecentralized navigation dataKnow the terrain
SensorsStandardized perception dataInteroperate with environment
PositioningLocation data (RTK precision)Navigate precisely
ComputeDecentralized AI backboneProcess at edge and cloud
ConnectivityNetwork linksCommunicate with fleet
OrchestrationMulti-robot coordinationSwarm behavior
StandardsInteroperability rulesWork with any system

The DePIN model works: GEODNET built the world's largest RTK network in under two years using token incentives. Centralized approaches cannot match that speed. The question is who controls the standards when billions of physical agents need to coordinate.

Foundation Members

Four organizations with specialized expertise:

OrganizationExpertiseContribution
Auki NetworkPosemesh — decentralized machine perceptionSpatial data exchange
GEODNETWorld's largest RTK network (12,000+ stations)100x GPS precision
MawariReal-time 3D data for AR/VR/spatial computingXR infrastructure
PeaqWeb3 Economy of Things on Polkadot — Purple PaperBlockchain layer + UMT + machine identity

Broader ecosystem: Helium, Hivemapper, NATIX Network

Universal Machine Time (UMT)

Peaq's March 2025 contribution — the first onchain implementation of Precision Time Protocol:

  • Blockchain-verified timestamps with nanosecond precision
  • Critical for autonomous vehicles, robotics, sensor networks
  • Foundation for all other coordination

"You can't understand space without first understanding time. Careful time calibration is how positioning technologies like GPS work in the first place." — Mike Horton, GEODNET

Architecture

The standard integrates with:

Applications

Where Intercognitive enables transformation:

DomainCurrent StateWith Intercognitive
Autonomous vehiclesProprietary, siloedInteroperable fleet coordination
Smart citiesVendor lock-inOpen infrastructure
Robotics fleetsCentralized controlDistributed ownership
Spatial computingPlatform-dependentCross-platform perception

Context

Questions

Which of the nine pillars is your biggest coordination bottleneck — and does fixing it unlock the others?

  • GEODNET built 12,000 RTK stations in two years with token incentives. Which of the remaining eight pillars could replicate that speed?
  • When a robot fleet spans multiple Intercognitive members (Auki for perception, GEODNET for positioning, peaq for payment) — who arbitrates when the standards conflict?
  • Does Universal Machine Time create a dependency that makes the entire stack brittle, or is verified time so fundamental that every other pillar already assumes it?