Technology

Coordinative Transactional Processing (CTP)

A patented approach that protects data by fragmenting it and separating responsibility across three independent modules. No single location contains the original data — reassembly happens only during a controlled restoral using a restoration-only key.

● Fragmentation: Module A splits pieces so no module holds the whole.
● Codesets: Transactional transport is validated with fresh codes (7 codes per transaction).
● Restoral-only A Code: The sole link back to original data — used only in controlled restoration.

Explore Products Request a Demo

Covered by U.S. Patent 9,405,927 · Architecture documented in SDX-TP-003 · $5,000 Independent Security Evaluation

C Chains lock with radiant keyhole — CTP fragmentation visualization

The Core Mechanism

Codesets: Transactional Currency That Makes Every Exchange Unique

Codesets are not merely administrative tokens; they are part of the transactional architecture. Each protected operation uses a fresh codeset to validate and coordinate the exchange while supporting separation of the information required for reconstruction.

Codes per transaction

100

Free evaluation codesets

Reused or replayable codes

8+ yrs

Independent evaluation award

Step-by-Step

How CTP Works — Simplified Walkthrough

Three physically separated modules communicate only through validated codeset exchanges. No module alone holds enough to reconstruct protected data.

Module A
Access

⇔

Module B
Base

⇔

Module C
Control

Codesets flow both directions — COK-BOK confirmations required at every transaction

Module A (Access): Fragments data, encrypts the B portion with keys only A holds, and sends to B.

Module B (Base): Stores the encrypted B portion, generates dynamic linking codes, and syncs with C.

Module C (Control): Holds linking keys including the A Code and validates via codeset exchange.

Verification chain: A ⇔ B ⇔ C with codesets; B returns BOK, C returns COK — ensuring sync at every step.

Restoral: Full data is only reassembled in a controlled restore when A+B are combined under C's keys and the A Code.

Architecture

Fragmented Data Protection — Why Separation Matters

CTP's core advantage is physical and logical separation. Each protected item is separated across components so that compromise of a single module does not, by itself, provide the information and authority required for reconstruction.

🔀

Module A — Access

Fragments data, keeps the A portion, encrypts the B portion, and initiates the transaction chain.

🗄️

Module B — Base

Stores the encrypted B portion and generates dynamic linking codes for C validation.

🔑

Module C — Control

Holds linking keys including the A Code — the sole path to reassembly, never exposed to B.

🧩

Fragmented Security

No single module is intended to provide complete Reconstruction Authority. The evaluation framework specifically tests whether compromise can be converted into Unauthorized Reconstruction.

🧠 Why This Design Is Unique — and Ingenious

No single point of compromise.

A handles fragmentation, B storage, C validation — each useless alone.

The A Code is invisible to B.

It participates in the controlled path back to original information and is intentionally separated from the protected-data store.

Rolling codesets add dynamism.

Fresh codesets make transactions distinct and are designed to prevent codeset reuse and straightforward replay.

Restoration-only dependency.

Operational access remains separate from the authority required for controlled reconstruction.

Why It Works

Key Benefits of CTP Architecture

True Compartmentalization

Data split across modules eliminates centralized risk.

Transport Validation

Rolling codesets ensure every exchange is synchronized and verifiable.

Controlled Restoration

The A Code is the sole path to reassembly — only in explicit restores.

Reduced Attack Surface

Breaching A, B, or C alone yields nothing useful.

Compliance-Ready

Every codeset operation generates an immutable audit entry.

No System Replacement

CTP layers on top of your existing database. Zero disruption.

$5,000

$5,000 Independent Security Evaluation

The published evaluation asks one defining question: can Protected Information be reconstructed outside the authorization model established by Structural Protection? A qualifying result requires reproducible Unauthorized Reconstruction under the published conditions.

Review the $5,000 Challenge →