Base 0 as generative origin
In Plexadi's architecture, Base 0 is not an empty binary zero. It is a sealed state in which information is neutralised until an authorised engine brings it back.
Technology portfolio
New ways to represent information, move it between systems, and reconstruct what matters at the destination.
Explore the enterprise pilotA public overview of the technology concepts. Technical disclosures, claims, and implementation details are reserved for confidential discussions.
Video explainer · 2:54
Why legacy codecs reach their limits with 8K, volumetric video and AR — and how reversible symbolic structures offer a different path.
Concept explainer. Performance statements are inventor-reported and not independently verified.
Architecture deep-dive
An operational view of each pillar — how information flows, what changes compared with conventional systems, and where it applies. Claims, formulas and implementation details stay confidential.
P4 moves exact bytes across channels where ordinary networking is unavailable. P4-S goes further: it conveys meaning and references so the receiving side can find the resources it needs and assemble the result locally.
The sender expresses what the destination needs: the entity, its relationships and the resources it depends on.
Semantic references travel instead of the whole finished object. Exact-byte content can use P4's binary-primary path with a visual fallback.
The receiver identifies resources it already holds locally or can retrieve from a trusted collection.
The result is assembled at the destination, including nested dependencies, without generative guessing.
Conventional delivery
P4 / P4-S approach
Where it applies
Conceptual description of patent-pending technology directions. Benefits are potential and require implementation testing and independent validation; no patent grant is asserted.
P9 · Base 0 · Concept overview
A high-level view of the mathematical foundation behind P9 and how it connects storage, security and reconstruction across the P-series.
In Plexadi's architecture, Base 0 is not an empty binary zero. It is a sealed state in which information is neutralised until an authorised engine brings it back.
Instead of moving full payloads across vulnerable networks, a compact deterministic seed is sent and the receiver's local base-12 engine rebuilds the content where and when it is needed.
A linear parser or AI scanner that tries to flatten the multi-dimensional structure is designed to see only uniform, high-entropy noise rather than readable data.
Colour and visual data are mapped through percentage-based RGB aligned with duodecimal structures, avoiding the overhead of 24-bit hexadecimal colour spaces.
Concept description only. Protocol sequences, codebook and implementation details remain confidential, and security and reconstruction properties are inventor-reported design goals, not independently verified results.
P7 · B12PPP · Concept overview
How B12PPP aims to remove data at rest as a target and make traffic in transit hard to intercept, replay or manipulate.
Files are not kept on disk as readable static objects. They are distilled into compact mathematical seeds, so a breached disk or cloud bucket is designed to hold no raw data to steal or encrypt for ransom.
B12PPP is designed to remove the Key Management Server as a single point of failure. Key coordinates are masked inside ordinary-looking semantic traffic instead of being held in one attractive target.
Content is rebuilt locally in memory only when an authorised process requests it, and returns to its sealed state when it is closed.
Unauthorised probing of the sealed geometry is designed to drive the attacking process into deterministic failure states rather than towards readable data.
The semantic language used between endpoints rotates automatically, by default every 60 seconds and adjustable to the customer's policy, so captured traffic quickly loses context.
Handshakes and files are split into 40 to 90 parts of unequal percentage sizes that together make up 100%. No single part is intended to carry enough information to reconstruct the whole.
An attacker who captures a single handshake part may hold only around 1% of the whole. Because every part has a dynamic size, there is no fixed boundary showing where one handshake ends and the next begins. To know which parts belong together, an attacker would also need to convert each part back through the correct bases in the correct order, which the design aims to make close to impossible.
Endpoints monitor timing. An unexpected delay of around 4 ms is treated as a possible interception, and the session rotates to an earlier semantic language or is terminated.
Static binary files and handshakes pass through several transformation layers, including base-12 and symbolic glyph representations, before travelling across the network as base-12 strings. The specific layers, bases and their order remain confidential.
Architecture description only. Conversion bases, intermediate encodings, codebooks and algorithms remain confidential and are shared only under NDA. All properties are inventor-reported design goals under development, not independently verified security results.
Plexenc research · Test report v1.2 · 10 August 2026
Plexadi’s supplied report compares a synthetic 8K UHD clip with a real NASA “Moving Water” 8K DCI clip. These are reported results, not independently reproduced tests or a NASA endorsement.
7680 × 4320 · 60 fps · 180 frames · 3.00 s
489 B
Reported semantic stream, video + audio
H.264 reference generated with x264, medium preset.
8192 × 4096 · 23.976 fps · 71 frames · 2.96 s
445 B
Reported semantic stream, video + audio
H.264 reference is the original NASA-source MP4, not re-encoded.
The report states byte-perfect recovery of the transmitted semantic descriptions in both tests. It explicitly does not claim pixel-perfect or byte-identical recovery of the original media. Video and audio reconstruction depend on an AI receiver; source-image quality was not established by these byte counts.
Raw-video sizes are equivalent uncompressed RGB footprints, not files transmitted by Plexenc. Semantic-stream sizes exclude the AI receiver and other reconstruction resources. These results concern Plexenc semantic media research, not proof of P4-Binary-Visual Transport’s deterministic original-byte transport or the security of P7-GlyphLock.
PDF · 4 pages · Source code and benchmark data available under NDA
SE 2630818-9
PRV received:2026-11-11 · 51submitted claims
SE 2630817-1
PRV received:2026-11-10 · 11submitted claims
PRV received:2026-11-11 · 6submitted claims
Confirmed from the supplied PRV acknowledgements of receipt. Receipt confirms submission, not patent grant or an earlier priority date.
Featured architecture · P4-S
Instead of only sending an entire finished object, P4-S explores conveying meaning and references so a receiving system can retrieve relevant resources and assemble a result.
Direct payload delivery alone does not organize the external resources, context, and dependencies needed to reconstruct complex digital entities.
Use semantic information to identify relevant resources and support reconstruction across local or distributed environments.
Resource reuse, context-aware assembly, and a resource collection that can evolve without redesigning the entire architecture.
What the destination needs
Assembled at the destination
Media assets and their dependencies can be spread across different systems.
A receiving system could assemble an asset from addressable resources rather than treating every delivery as an isolated payload.
P4-S is a distinct architecture, not a base-12-only system. It is described independently of any particular numerical representation, geometry, interpretation technology, or storage medium. These examples illustrate possible applications, not deployed products or measured performance.
P4 is the earlier deterministic binary-visual transport work. P4-S is newer work developed to address gaps in that earlier work, while presenting a distinct semantic routing and reconstruction architecture. This development history does not imply a formal legal continuation or replacement of P4.
Related technology directions
Other concepts in the Plexadi portfolio address the infrastructure beneath digital systems. They are separate technology directions, not assumed dependencies of P4-S.
P4 · DETERMINISTIC TRANSPORT
P5 · CONTAINERS & SYNCHRONIZATION
P6 · STORAGE & INTEGRITY
P7 · COMMUNICATION SECURITY
P8-BC12 / BASE C12 · COMPUTING
P9 · FOUNDATIONS
SECURE EXCHANGE
Ask the technology
An AI assistant that answers only from Plexadi's published pages. Anything confidential is reserved for the NDA process.
AI answers may be incomplete. They are based on public information only and are not technical, legal or investment advice.
For CTOs, CISOs, enterprise architects and strategic partners. Tell us who you are and what you want to evaluate. Detailed materials are shared under a mutual non-disclosure agreement — patent documents themselves are not published.
Discuss the use case, integration requirements, and validation needed for your environment. Detailed materials can be considered under a mutual non-disclosure agreement.
Research results are attributed to the supplied report; no independent verification or patent-grant status is asserted.