ARCHITECTURE

Actor Infrastructure Platform

AIP is the foundational layer of the Actor ecosystem: the actors, services, runtime, communication, and security required for distributed, concurrent, autonomous computing — from edge devices to HPC. Every Point of Data product sits on it, so it is worth understanding.

WRITTEN IN C
NO INTERPRETER RUNTIMES
POSIX-COMPLIANT
EDGE IOT → HPC
EMERGENCE BY DEFAULT
THE MODEL, PLAINLY

Everything is written in C. Actor and Evolutionary Neural Memory services need nothing running but the base OS — no interpreter runtimes, no phalanx of packages, no version dependencies — across all modern POSIX-compliant operating systems.

Actors

An Actor Gateway accepts messages, routes them to the correct actor, and returns the actor's reply to the requestor. It manages the actors assigned to it, turning them on and off as required. Gateways talk to everyone — other actors, any other software — over TCP sockets.

OPERATING SYSTEM
Service 1
…
n
Agent
actor@gateway
SOCKET
MESSAGES
CUSTOMER SOFTWARE
Services@Agents (0…n)
Software (SDK or socket)
Agentic
interconnections
VIA MCP · A2A
Every message is an Event

Something that happens at a specific time and place, sent from a specific entity to a specific entity. Edge software captures telemetry in surgery and sends it to Evolutionary Neural Memory. Messages are like email — except they carry instructions and data: store an event, search memory, request a service, and infinitely more.

Addressing as simple as email

A requestor only needs an address. AIP handles every hop of routing and inter-actor communication needed to finish the request.

llm-use-case-prompts@pointofdata.ai

Evolutionary Neural Memory DB Service

ENM runs as its own actor type. It captures and searches high-fidelity, dense context, stored in a hypergraph — a set of vertices with edges that can each link a different number of vertices. Every vertex is an Event Object: whatever the engineer, scientist, or AI decides is worth tracking over time.

UNLIMITED TAGS — THEMSELVES EVENT OBJECTS, AUTOMATICALLY VERSIONED
category
price
allergen
season
author
version
EVENT OBJECT — VERTEX
menu_item · 04:12:08Z
Optional data payload of any mimetype, up to 2 GB.
INFINITE LINKS — WEIGHTED, AND DESCRIBABLE WITH TAGS OF THEIR OWN
appears_on
Dinner menu · spring 2026
w 0.90
prepared_by
Station 3 · line cook
w 0.62
sourced_from
Supplier · Cascade Farms
w 0.74
observed_at
Telemetry event · 04:12:08Z
w 1.00
No schema tax
Infinite schema changes that do not break dependent software. Expand the description of an event without breaking the contract — and dependents can ask for versioned information.
Behaves how you need it to
We have used weights to build a neural network inside ENM, and tags to make ENM behave like a SQL database — including SQL syntax.
Simple message types
Store single or batched events, link events, update events, and search events. That is the whole interaction surface.
IMPLICIT CONNECTIONS

AIP natively connects time, data, and named-tag information. That removes most of the work of building a high-fidelity memory — and gives you a new capability: understanding and searching data in context.

“The circumstances that form the setting for an event, statement, or idea, and in terms of which it can be fully understood and assessed.”

Programmable search

Searching high-fidelity context takes more than keywords or vectors. ENM search runs conditions and branches, pattern matching, and mathematical search across events, tags, and links — and can run concurrently across multiple memories.

Conditions & branches
Pattern matching
Mathematical search
Concurrent across memories

Security

AIP manages security for the creator, with full control over each layer — SSL and AIP Advanced Security. New to the market: encrypted memory search that never decrypts the data during the search, so you pay neither the computation cost nor the security risk.

SSL
AIP Advanced Security
Encrypted search
EMERGENCE

Structure, context, and behavior arise bottom-up.

In complex systems theory, emergence describes how sophisticated patterns arise from simple components following local rules — with no central designer dictating the global form. Most stacks fight that or approximate it expensively. Pod-OS, Evolutionary Neural Memory, and the Actor Infrastructure Platform bake it into the substrate: structure, context, memory, and complex behavior emerge from event objects and autonomous actors instead of being imposed by schemas, shared state, or central orchestration.

MECHANISM 01
Event objects as the universal primitive

Every piece of data, whatever its type or format, is an event object that inherently carries when, where, and who. A document is an event; modifying it is another event.

No prior description is ever lost
Links and tags have no limit on number or evolution
You cannot build the dense hypergraph without event objects
A SQL column is missing history by definition; lakes recover it by brute force
MECHANISM 02
Structure emerges from data, not schemas

Neural Memory stores a time- and location-based state slice as a hypergraph of objects. High-level objects emerge from relationships that are defined or discovered — never from a schema.

New node types, edge types, properties, and tags are additive and backward-compatible
Tags version automatically, with full history
The graph is bidirectional by default
No rigid schema, no migration tax, no schema-evolution tax
MECHANISM 03
Actors and share-nothing messaging

Everything is an actor — ENM, gateways, application logic. Actors all the way down. Private state, messages only, location-transparent from edge device to hypercomputer.

Complex behavior emerges from local message exchange, not replicated shared state
Agreement through communication protocols, not eventual consistency
Propose / respond / commit / witness primitives on the roadmap as the Actor Agreement Protocol
Email is the existence proof that this model handles trillions of messages
MECHANISM 04
Three temporal memory modes

Long-term memory lives in the ENM hypergraph, durable and evolutionary. Short-term and real-time stay actor-local. The result is dense, associative, contextual memory.

Pattern traversal and computational search inside ENM
Full history, relationships, time, location, and evolving structure remain available
Vector and RAG pipelines return approximate, context-stripped retrieval
Reasoning, planning, and collaboration emerge from a richer substrate
TRADITIONAL AGENT STACKS
Agents layered on top of conventional databases or vector stores.
Memory is external, lossy, or schema-constrained.
Coordination needs shared state or heavy orchestration.
Emergent multi-agent behavior is fragile.
POINT OF DATA
Agents and actors are first-class citizens of the model that stores their memory.
An agent is just another actor — creating events, forming links, negotiating.
The same primitives scale from a single IoT sensor to global actor networks.
Zero-trust, quantum-resistant security and energy efficiency are intrinsic.
FIVE LOCAL RULES
Record everything as contextual events.
Connect freely.
Keep history.
Communicate only by message.
Let structure discover itself.

Those rules produce dense hypergraphs, adaptive agent behavior, and scalable autonomous systems — outcomes traditional approaches reach only with high cost, complexity, and information loss. Emergence is not supported here; it is the default operating principle.

WHERE IT FITS
Knowledge graphs that grow organically
IoT fabrics where sensor relationships emerge
Training and inference with persistent high-fidelity context
Election integrity with full provenance
Scientific and financial audit trails
Evolving recommendation systems
Multi-agent actor economies

Performance

Platform software and storage are performant and efficient by design — which is where the efficiency gains come from.

786 KB
Actor binary on a 64-bit machine
5 MB
Memory consumed by an actor at startup
894 KB
Evolutionary Neural Memory binary
10 MB
ENM memory consumed at startup
1.8 quadrillion
Event objects per database instance
10K / sec
Event objects inserted on an average Orange Pi with an SSD
TLDR

AIP runs Actor Gateways that vend actors you define, reachable by messages addressed to actor@gateway. Messages travel over TCP sockets, with SDKs that make sending and receiving easy, concurrent, and performant. The Evolutionary Neural Memory DB service is a hypergraph store that explicitly and implicitly links events and describing tags; each event carries a payload up to 2 GB and is infinitely describable and linkable. Search is programmable, runs encrypted, and spans multiple memories concurrently. The runtime needs under 1 MB of disk and 5 MB of memory per actor, with no layers of dependent software adding cost and technical debt. Each memory holds up to 1.8 quadrillion events, and an average Orange Pi with an SSD inserts up to 10,000 event objects per second.

TLDR is short for “too long, didn't read” — the synopsis engineers and ML scientists use to accelerate the search for a candidate solution. This one is for our friends. May your next delivery go smoothly.

This architecture expands infinitely. Come see it run.

Book a demo →