What is PDDS?
PDDS is a distributed systems paradigm for reasoning about systems whose participants exhibit bounded, governable, or irreducible non-determinism.
Execution governance paradigmSovereign autonomous infrastructure
Post-Deterministic Distributed Systems
Autonomous infrastructure must govern probabilistic intelligence.
The coordination layer for infrastructure whose autonomous participants are probabilistic. PDDS converts stochastic model output into governed intent before any consequential state change.
Classical distributed consensus assumes deterministic participants under network partitions. PDDS decouples reasoning from execution authority, enforcing zero unauthorized state mutations across critical systems.
Stochastic Reasoning → Control Gate → ExecutionDecoupled & Bound
Sovereign Control BoundaryIntent → Verified Mutation
Deterministic policy gates isolate model stochasticity, ensuring actions execute only within validated contracts and immutable audit chains.
Direct answer
PDDS is the canonical acronym for Post-Deterministic Distributed Systems.
PDDS describes distributed systems whose participants may be deterministic, stochastic, adaptive, or human-mediated, while still requiring governed, explainable, and auditable coordination before consequential execution.
- Acronym
- PDDS
- Full term
- Post-Deterministic Distributed Systems
- Primary domain
- Distributed systems and autonomous infrastructure
- Core shift
- From state agreement alone to governed semantic coherence
What is PDDS?
A model for distributed systems after deterministic participants stop being the only case.
Classical distributed systems assumed deterministic participants and focused on networks, timing, and failures. That foundation remains essential, but it does not fully describe systems where participants interpret goals, synthesize plans, adapt workflows, or ask humans to approve consequential actions.
Post-Deterministic Distributed Systems (PDDS) extends the model to include non-deterministic participants such as AI agents, autonomous services, adaptive workflows, and human-in-the-loop components. PDDS treats deterministic services as the zero-ambiguity limit case inside a broader governable participant model.
Five pillars
Five Pillars of PDDS
The pillar names follow the terminology defined in the PDDS paper and manifesto.
Safety Perimeter
Protocol-Driven Development
Defines machine-enforceable protocols that admit generated software and autonomous outputs only when they satisfy semantic and operational invariants.
Identity Boundary
Verifiable Agentic Infrastructure
Replaces static credentials with intent-based authorization, ephemeral delegation, and evidence-backed execution identity.
Orchestration Plane
Autonomous State Control Planes
Separates high-variance reasoning from direct state mutation while preserving intent across asynchronous execution.
Certification Core
Semantic Quorum Assurance
Certifies meaning, intent, policy, and evidence across diverse participants instead of relying only on bitwise agreement.
Persistence Layer
Epistemic State Replication
Replicates knowledge states and belief lineage while preserving cognitive diversity and enabling semantic rollback.
PDDS Evidence Layer · ATP SpecificationarXiv:2608.16178
Agent Telemetry Protocol (ATP)
How does PDDS verify and audit non-deterministic execution in practice? By replacing verbose human prose logs with cryptographically verifiable state deltas. ATP slashes LLM context load by 88.8%, reduces wire payloads by 96.4%, and eliminates prompt injection vulnerabilities.
96.4%
Wire & Scan Cut
512.4 B → 18.4 B raw wire payload per record.
88.8%
Context Token Savings
34k → 3.8k tokens per incident diagnosis session.
75% Faster
Time to Root Cause
TT-RCA reduced from 184s down to 46s.
0.0%
Prompt Injection Hijack
0/100 attacks successful across adversarial trials.
PDDS Consensus Layer · EBFT SpecificationarXiv:2607.16109
The Honest Quorum Problem & Epistemic BFT
Why do protocol-compliant AI agents agree on catastrophic state transitions? Classical BFT assumes independent node failures. When LLMs share foundational biases or prompt drift, they exhibit correlated cognitive failure modes. Epistemic Byzantine Fault Tolerance (EBFT) introduces confidence-indexed quorum bounds (Q > f + eδ) to prevent false semantic consensus.
Q > f + eδ
Epistemic Quorum Lower Bound
Quorum size required to survive malicious + correlated hallucinating nodes.
3 Fault Classes
Taxonomy of Agent Failures
Physical/crash, semantic divergence, and correlated hallucination.
0.0%
Unchecked Hallucinated Quorums
Enforces deterministic semantic validation before state commits.
Multi-Model
Cognitive Diversity Index
Cross-substrate quorum members decouple correlation failure modes.
Primary application domain
Sovereign AI Infrastructure
OpenKedge explores architectures for sovereign, governable, and verifiable AI systems supporting enterprises, critical infrastructure, and national-scale digital transformation initiatives.
Trustworthy by Design
Critical actions begin as reviewable intent instead of unchecked operational access.
Governable by Policy
Institutional policy constrains what autonomous systems may recommend, escalate, or execute.
Verifiable by Evidence
Every important decision leaves a replayable chain for operators, auditors, and leaders.
Sovereign by Architecture
Reasoning can be global while execution authority remains inside local institutions.
Open by Standard
The implementation path stays portable through open protocols and reference code.
01PDDS paradigm
02OpenKedge framework
03Research papers
04Open source implementations
05Sovereign AI deployments
Models may be global. Execution authority must remain sovereign.
Citation
Cite the PDDS paper
The canonical research artifact is the arXiv paper, with the OpenKedge paper page serving as the HTML reading and sharing surface.
Reference format
Use the acronym consistently.
Use Post-Deterministic Distributed Systems (PDDS) on first mention, then PDDS thereafter. This keeps citations, answer engines, social posts, GitHub discussions, and future papers converged on one short term.
FAQ
PDDS FAQ
What does PDDS stand for?
PDDS stands for Post-Deterministic Distributed Systems.
How does PDDS differ from classical distributed systems?
Classical distributed systems primarily model deterministic participants under network, timing, and failure constraints. PDDS extends that model to include non-deterministic participants such as AI agents, autonomous services, adaptive workflows, and human-in-the-loop components.
Sovereign execution control
Govern the proposal before it becomes an action.
Global models may propose. Local policy, bounded credentials, and tamper-evident evidence determine what is permitted to execute.