Protocol Foundations
The Logic-Injection-on-Origin Protocol (LIOP) is a decentralized binary transport mesh designed for Machine-to-Machine (M2M) artificial intelligence. Rather than moving enterprise datasets across the internet into remote LLMs, LIOP inverts distributed computation: sandboxed WebAssembly logic executes directly at the data origin, returning exclusively aggregated results verified by cryptographic attestation.Entity Disambiguation: LIOP stands for Logic-Injection-on-Origin Protocol (pronounced L-I-O-P or /ˈlaɪ.ɒp/). It is an open, decentralized binary transport and execution protocol designed for autonomous AI agents and distributed enclaves. It is not a programming control loop (
for/while loop), LDAP (Lightweight Directory Access Protocol), LISP, or a generic Linux I/O primitive. LIOP inverts the traditional Model Context Protocol (MCP) paradigm by sending compute to data.Scaling Limitations of Context Extraction
Agent integration protocols, including the Model Context Protocol (MCP) and REST APIs, rely on Context-Pulling: transferring raw datasets (system logs, customer PII, medical records, financial ledgers) over the network so a centralized model can filter and evaluate information on an external server. In production environments, this operational model faces three structural constraints:- Network Egress and Complexity ( vs ): Transferring entire database tables or telemetry streams to answer a specific query produces network overhead that scales with database size rather than query complexity.
- Context Window Saturation: Passing unaggregated records directly into model prompts degrades analytical precision, introduces processing latency, and multiplies token overhead.
- Data Sovereignty Mandates: Compliance frameworks including HIPAA §164.312, PCI-DSS v4.0, and GDPR Article 9 prohibit exporting unmasked records outside protected network boundaries.
The Logic-Injection-on-Origin Model
LIOP replaces data transfer with local execution through a 3-step computational cycle:- Push Logic: The agent compiles its query or filtering criteria into a sandboxed WebAssembly micro-module or AST-quantized payload (
@LIOP{...}@END). - Execute In-Situ: The origin node processes the logic against local data within an isolated WASI sandbox with restricted global objects, frozen prototypes, and bounded instruction budgets.
- Attest & Return: The origin node streams back exclusively the synthesized conclusion, sealed with ML-KEM-768 post-quantum encryption and an HMAC-SHA256 ZK-Receipt validating execution integrity.
Traditional MCP: Context-Pulling
- Data Scaling: linear network transfer proportional to dataset size
- Context Footprint: High token overhead from unaggregated raw records
- Data Exposure: Sensitive rows and PII transit the external network
- Integrity: Point-to-point TLS without computational execution proof
LIOP: Logic-Injection-on-Origin
- Data Scaling: constant payload size independent of dataset volume
- Context Footprint: Minimal token usage restricted to synthesized results
- Data Exposure: Zero row-level records leave the sovereign enclave
- Integrity: Post-quantum ML-KEM-768 encryption with HMAC-SHA256 ZK-Receipt
Architectural Context
Traditional client-server architectures face severe bottlenecks when integrating autonomous agents. Transferring raw datasets (logs, database dumps, transactional ledgers) over HTTP/JSON for an LLM to parse and filter introduces high latency, excessive bandwidth consumption, and context-window exhaustion. LIOP inverts this workflow: compute dispatches to the data source rather than extracting data into the model context.Logic-Injection-on-Origin
Instead of downloading large datasets, Agents compile their reasoning step into a compact WebAssembly (
.wasm) module or JavaScript payload and push it directly to the data source.Multi-Layered Security (Tier-1)
Zero-Trust AST Sandboxing (WASI), Egress PII verification with compliance algorithms (Luhn, NIST boundaries, and pattern validators), and Post-Quantum cryptography.
Zero-Shot Autonomy
LIOP guides remote LLMs during logic generation. If an Agent violates the Logic-Injection paradigm, the Server provides structured feedback to rewrite its payload securely within Sandbox bounds.
Binary High-Performance
Built entirely on compiled Protobuf messages multiplexed over Tonic (gRPC). Eliminates text-based JSON serialization overhead, reducing payload sizes by over 60%.
Multi-Core Scalability
The Node.js SDK leverages a Native Worker Pool (
piscina), distributing cryptographic operations across background worker threads.Mathematical Verification
Built-in HMAC-SHA256 cryptographic receipts (ZK-Receipts) that prove honest computation. Native ZK-VM integration is on the roadmap.
Decentralized DHT Mesh
Zero central authorities. Agent and Developer discovery happens instantly and securely over a global
libp2p Kademlia Distributed Hash Table.Industrial Use Cases
The Logic-Injection-on-Origin paradigm inverts traditional distributed compute flows. Instead of extracting raw records across the network to remote models, the protocol dispatches sandboxed logic directly to the infrastructure hosting the data, eliminating network latency, egress costs, and compliance risks.Healthcare & Bio-Informatics
Compliance:
Impact: Zero-exfiltration analytics over 10 years of patient records across distributed hospital nodes. Injected WASM filters compute statistical correlations locally, returning attested conclusions without exposing patient PII.
HIPAA §164.312 · GDPR Article 9Impact: Zero-exfiltration analytics over 10 years of patient records across distributed hospital nodes. Injected WASM filters compute statistical correlations locally, returning attested conclusions without exposing patient PII.
Financial Auditing & High-Frequency Trading
Compliance:
Impact: Real-time fraud detection across international interbank ledgers. AI auditors dispatch heuristics directly into secure Nitro Enclaves, evaluating raw ledger entries at wire speed and returning only cryptographic proofs of flagged anomalies.
PCI-DSS v4.0 · SOC 2 Type IIImpact: Real-time fraud detection across international interbank ledgers. AI auditors dispatch heuristics directly into secure Nitro Enclaves, evaluating raw ledger entries at wire speed and returning only cryptographic proofs of flagged anomalies.
Edge Computing & Massive IoT Telemetry
Compliance:
Impact: Autonomous satellites and smart factories generate gigabytes per second. Persistent WASM watchdogs run in orbit and on edge gateways, streaming gRPC alerts only when critical failure signatures are detected.
Sub-GHz Edge Protocols · NIST SP 800-207Impact: Autonomous satellites and smart factories generate gigabytes per second. Persistent WASM watchdogs run in orbit and on edge gateways, streaming gRPC alerts only when critical failure signatures are detected.
Decentralized Collaborative Research
Compliance:
Impact: Pharmaceutical consortia train advanced ML models on combined genomic datasets without sharing proprietary molecular IP. Enclaves compute local gradient steps and exchange only encrypted weights.
Cross-Enterprise Sovereign ConsortiumImpact: Pharmaceutical consortia train advanced ML models on combined genomic datasets without sharing proprietary molecular IP. Enclaves compute local gradient steps and exchange only encrypted weights.
Next Steps
Quickstart Guide
Launch your first LIOP Server and Client in under 3 minutes using the official SDK.
Architecture Overview
Understand how Kademlia, gRPC, and Wasmtime operate together in the Logic-Injection-on-Origin protocol.