Represent the source payload in a form designed for constrained transport. The public layer describes the role of this stage, not the mechanism that produces the reduction.
What HDTP is
A research architecture built around reduction, transit and exact reconstruction.
The public HDTP record describes a three-part system: transform source data into a constrained transit representation, move that representation through a limited communication path, then reconstruct the original payload at the destination. The stronger mechanics that determine whether the architecture can satisfy its intended performance are not part of the public disclosure layer.
→
Carry the resulting representation through an available low-capacity communication path using a protocol designed around constrained conditions.
→
Reconstruct the original payload and verify integrity. Exact reconstruction is an explicit design requirement that must be demonstrated under controlled technical review.
Canonical framing
HDTP is not presented here as a proven violation of information theory, a production network, or a universally validated transport protocol. It is presented as a documented, IP-sensitive protocol architecture whose strongest technical claims require access to the reserved mechanism layer and reproducible evaluation.
Why the problem matters
When communication capacity becomes the constraint.
The research target is not ordinary broadband transfer. It is the class of situations where the available communication path is materially smaller, slower or less reliable than the payload a system would ideally move.
Edge / IoT
Constrained devices
Low-power sensors and edge systems often operate under strict bandwidth, energy and connectivity limits. HDTP asks whether representation and reconstruction can be redesigned around those limits.
Resilience
Degraded infrastructure
When primary infrastructure is partially unavailable, the useful question may become how much information can be preserved and reconstructed over whatever capacity remains.
Research
Representation vs. transport
HDTP separates the representation problem from the physical channel problem and treats reconstruction integrity as a first-class requirement rather than an afterthought.
Scientific boundary
“Beyond-Shannon” is a hypothesis to test, not a public conclusion.
Legacy HDTP materials used language such as “beyond-Shannon reduction” and “bit-perfect through any narrow channel.” Those phrases capture the ambition of the research, but the canonical site should distinguish ambition from demonstrated result.
What is strong and real now
- A documented protocol architecture and research framing exist.
- The three-stage reduction → transit → reconstruction model is consistently present in the source corpus.
- IP-sensitive technical material is intentionally held outside the public layer.
- Provenance and formation records are part of the controlled-review path.
What must be proven independently
- The actual reduction achieved on defined datasets and payload types.
- All information, side-state and reconstruction assumptions required by the system.
- Whether exact reconstruction holds across controlled test conditions.
- Channel overhead, latency, energy cost, error tolerance and scaling behavior.
- Novelty, prior art, patentability and freedom-to-operate.
Information-theory discipline
Any claim that appears to exceed conventional compression limits must account for all transmitted information, shared state, prior knowledge, model state and reconstruction assumptions. That accounting belongs in a rigorous technical review, not in a public marketing headline.
Maturity
Architecture is established. Validation remains asset-specific.
Layer
Current canonical status
Reviewer question
Research problem
Documented constrained-channel problem framing and architecture.
Is the problem definition technically coherent?
Protocol architecture
Three-stage reduction / transit / reconstruction structure is documented.
Can the reserved mechanics instantiate the architecture as specified?
Technical core
Reserved / IP-sensitive; not disclosed at re-implementation depth.
Does controlled review substantiate the mechanism?
Performance
No independent public benchmark is treated as canonical proof.
What does reproducible testing show?
IP status
Candidate technical/IP material requiring professional review.
Novelty, inventorship, claim scope, prior art and FTO?
Disclosure architecture
Review depth increases without making the public page a data room.
Public
Orientation
Problem class, architecture, maturity, intended applications, boundaries and what would need to be validated.
PublicControlled
Technical substantiation
Selected architecture documents, provenance, formal assumptions and reviewer material needed to understand the mechanism.
Controlled reviewRestricted
Mechanism / IP
Mechanism-level details, implementation-sensitive logic and claim material whose disclosure could affect protectability or copying risk.
NDA / restrictedPhase 3
Independent validation
Reproducible technical testing, information-theoretic review, IP/legal analysis and domain-specific feasibility assessment.
Independent reviewNo disclosure percentages are canonical.
Legacy pages used multiple percentage splits for public/restricted/reserved material. Those numbers were inconsistent and are not used in the rebuilt architecture. Disclosure is determined by review need, security/IP sensitivity and diligence stage.
Portfolio relationship
Research can connect to the portfolio without becoming dependent on it.
HDTP has conceptual relationships to other MZN work, but those relationships should not be used as proof of technical validity.
Research
BioCode
Biological information-transfer ideas are part of the inspiration layer. BioCode is not evidence that HDTP works; each research family requires its own review.
Security
ZOE / ISBP
HDTP shares concerns about trust boundaries and structural security with the security portfolio, while remaining a distinct protocol-research asset.
Convergence
Phase 3
If validated and strategically relevant, HDTP could become one selectable capability in future integrated systems. Integration is optional, not a prerequisite for standalone review.
Independent review questions
What a serious reviewer should try to establish.
01
Formal accounting
What information, shared state and assumptions are required from source to reconstruction?
02
Reproducibility
Can a qualified reviewer reproduce exact reconstruction under controlled test conditions?
03
Performance envelope
What reduction, overhead, latency, error tolerance and scaling behavior appear across defined workloads?
04
Novelty / IP
Which parts are genuinely novel once prior art and claim scope are examined professionally?