Skip to main content

ZPE-IMC Masthead

ZPE-IMC

CI PyPI Python License

What This Is

ZPE-IMC is a multimodal reference codec for the Zer0pa 20-bit word format. It packages 10 modality lanes behind one stream contract, but it does not import or orchestrate the standalone ZPE-* repos and should not be read as the family's production platform core.

Public package truth is now split cleanly. pip install zpe-multimodal closes the base Python package surface and the top-level text compatibility API. pip install "zpe-multimodal[native]" closes the public native-kernel install path by resolving zpe-imc-kernel from PyPI. The accepted runtime authority for IMC remains the March 7 Phase 6 native run-of-record; the older wave1.0 / total_words=844 demo remains frozen downstream compatibility history.

All current evidence is bounded to synthetic and reference inputs. No real-world production workload validation exists.

Readiness: staged, synthetic/reference evidence only. Public package surface available. Optional native extra available. Not the first buying surface.

Not claimed: production platform readiness, specialist-encoder parity, real-world workload validation, or that sibling ZPE-* repos literally run on IMC as runtime imports.

Part of the Zer0pa family. Sibling codec repos: ZPE-Bio, ZPE-FT, ZPE-Geo, ZPE-Ink, ZPE-IoT, ZPE-Mocap, ZPE-Neuro, ZPE-Prosody, ZPE-Robotics, ZPE-XR.

Field Value
Architecture MULTIMODAL_DISPATCH
Encoding UNIFIED_20BIT_WORD

Key Metrics

Metric Value Baseline
MODALITIES 10 one 20-bit transport word
THROUGHPUT 276,798.72 words/sec Phase 6 native run
DETERMINISM 11/11 benchmark scenarios
RUNTIME_TESTS 169/169 run-of-record suite

Source: proofs/logs/phase6_run_of_record_manifest.json; proofs/logs/phase6_determinism_probe.json

Competitive Benchmarks

IMC is the multimodal dispatch/reference repo, not the portfolio's comparator lane for compression sales claims. Competitive benchmark authority lives in the domain repos where the commercial wedges are actually sold: IoT, XR, Robotics, Geo, FT, Bio, Ink, Mocap, Neuro, and Prosody.

What We Prove

  • One public repo ships a shared 20-bit stream contract across 10 modality lanes
  • The public base package imports cleanly and preserves the top-level text compatibility helpers
  • The public native extra resolves to a real Rust kernel package (zpe-imc-kernel) rather than a local-only build step
  • The March 7 Phase 6 runtime packet records a Rust-backed accepted path with deterministic benchmark facts and a native scan contract
  • The historical wave1.0 compatibility vector remains frozen for downstream replay and custody

What We Don't Claim

  • That IMC is the first buying surface for the portfolio
  • That sibling ZPE-* repos import and run on IMC as a production platform core
  • Production deployment readiness or real-world workload authority
  • Universal compression wins across all modalities
  • That the historical 844-word demo is the current native runtime authority

Commercial Readiness

Field Value
Verdict STAGED
Commit SHA e316ddd7
Confidence Phase 6 native runtime packet plus retained multimodal benchmark packet
Source proofs/logs/phase6_run_of_record_manifest.json; proofs/logs/phase6_rust_backend_proof.json

Tests and Verification

Code Check Verdict
V_01 Base package import and top-level text roundtrip PASS
V_02 Public native extra install path (zpe-multimodal[native]) PASS
V_03 Phase 6 native run-of-record (169/169) PASS
V_04 Determinism probe (11/11) PASS
V_05 Multimodal benchmark packet PASS
V_06 Historical wave1.0 compatibility vector (844) PASS

Proof Anchors

Path State
proofs/logs/phase6_run_of_record_manifest.json VERIFIED
proofs/logs/phase6_rust_backend_proof.json VERIFIED
proofs/logs/phase6_determinism_probe.json VERIFIED
proofs/artifacts/modality_benchmarks.json VERIFIED
docs/family/IMC_COMPATIBILITY_VECTOR.json VERIFIED

Repo Shape

Field Value
Proof Anchors 5 verified
Modality Lanes 10
Authority Source proofs/logs/phase6_run_of_record_manifest.json
  • code/: installable zpe-multimodal package, tests, and benchmarks
  • code/rust/imc_kernel/: optional native kernel package for the public native extra
  • executable/: repo-local demo and runtime harnesses
  • proofs/: retained modality packet plus current Phase 6 runtime facts
  • docs/: architecture, legal boundaries, and downstream contract files

Quick Start

python -m pip install --upgrade pip
python -m pip install zpe-multimodal
python - <<'PY'
import zpe_multimodal as zm
ids = zm.encode("hello zpe")
print(zm.__version__)
print(zm.decode(ids))
PY

python -m pip install "zpe-multimodal[native]"
python - <<'PY'
from zpe_multimodal.core.imc import get_kernel_backend_info
print(get_kernel_backend_info())
PY

Expected native-backend facts:

  • backend='rust'
  • compiled_extension=True
  • fallback_used=False

Ecosystem

Workstream Route Notes
ZPE-Bio github.com/Zer0pa/ZPE-Bio Biology codec workstream
ZPE-FT github.com/Zer0pa/ZPE-FT Finance codec workstream
ZPE-Geo github.com/Zer0pa/ZPE-Geo Geospatial codec workstream
ZPE-Ink github.com/Zer0pa/ZPE-Ink Handwriting codec workstream
ZPE-IoT github.com/Zer0pa/ZPE-IoT IoT telemetry codec workstream
ZPE-Mocap github.com/Zer0pa/ZPE-Mocap Motion capture codec workstream
ZPE-Neuro github.com/Zer0pa/ZPE-Neuro Neural signal codec workstream
ZPE-Prosody github.com/Zer0pa/ZPE-Prosody Speech prosody codec workstream
ZPE-Robotics github.com/Zer0pa/ZPE-Robotics Robotics codec workstream
ZPE-XR github.com/Zer0pa/ZPE-XR XR spatial codec workstream
Package docs code/README.md Installable package surface
Architecture docs/ARCHITECTURE.md Current repo/runtime truth
Legal boundaries docs/LEGAL_BOUNDARIES.md Scope and non-claims

Who This Is For

IMC matters when you need one deterministic transport contract for heterogeneous signals, or when you need a reference codec for cross-modality tooling. If you are evaluating a first commercial wedge, start with the domain repos.

Historical Wave-1 Snapshot

The frozen wave1.0 contract and total_words=844 demo anchor remain part of the downstream compatibility story in docs/family/IMC_COMPATIBILITY_VECTOR.json. They are historical contract custody, not the current accepted runtime authority path.

Open Risks (Non-Blocking)

  • All current evidence is still synthetic/reference only
  • The public native extra is only as broad as the published wheel matrix; no Windows claim is made here
  • IMC is still not the first-sale surface; the domain repos remain the commercial entry points

Contributing, Security, Support

Metadata

Release files for zpe-multimodal 3.0.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for zpe-multimodal 3.0.2
File Size Uploaded Provenance
zpe_multimodal-3.0.2.tar.gz 121.7 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for zpe-multimodal 3.0.2
File Interpreter ABI Platform
zpe_multimodal-3.0.2-py3-none-any.whl Python 3 none any Details

Total release size: 272.8 kB

Release files / zpe_multimodal-3.0.2.tar.gz

Download URL zpe_multimodal-3.0.2.tar.gz
Size 121.7 kB
Tags Source
SHA-256 checksum
How to use checksums
15d4d9f84d0e01871e489a15ce19eb36c11c10c29200231bef5586e06c0d8a3c
BLAKE2b-256 checksum
How to use checksums
e8e2bc42199f370e643ae8a7b060ca592529415fb5b5b078faf8c86ed9a43eed
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.13.12

Release files / zpe_multimodal-3.0.2-py3-none-any.whl

Download URL zpe_multimodal-3.0.2-py3-none-any.whl
Size 151.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2a9cdaea30d07562f56f44e515d430024c76953b60cc3801e9af95fab9ac4293
BLAKE2b-256 checksum
How to use checksums
275cee2ab9a64bff65a81fa78e65b26ead2f98d876d6996aa6a3b16aee12114c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.13.12

Security for zpe-multimodal 3.0.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page