mdc-lite v1.2.0

mdc-lite v1.2.0

Breaking on-disk format change. Every entry's encrypted bytes are now DNA-encoded (2 bits/base, 00→A 01→C 10→G 11→T — the same mapping MDC Platform's DNA archive tier uses) before being written to disk, so a stored file is ACGT text, not raw binary. This is applied to ciphertext, never plaintext — the mapping is public, so encoding plaintext directly would only be obfuscation; XChaCha20-Poly1305 encryption (unchanged) is what actually protects an entry.

v1.1.0 and earlier stores are not readable by v1.2.0, and vice versa. No migration path for this prototype-stage format change — re-put() existing entries under the new version if you have any.

What's new

• src/dna.rs: the DNA encode/decode module, 6 new tests.
• 3 new tests in src/lib.rs confirming the on-disk file is genuinely ACGT text, doesn't leak the plaintext value, and that a corrupted (non-ACGT) file fails cleanly rather than panicking.
• 23/23 tests passing (up from 14).

Positioning correction (docs only, no code change)

mdc-lite has always been mobile/wearable-only — no CLI, no standalone desktop app. Docs now say so explicitly, and clarify why macOS/Windows builds still exist: desktop-companion-app embedding, and a planned (not yet built) MDC Platform CLI bridge to open an mdc-lite store when a phone/wearable is connected to a Windows machine. mdc-lite also doesn't store AI models — that's MDC Platform's job; mdc-lite stores small generic objects (settings, credentials, cached blobs).

See BUILD_INFO.md for exact verification details per artifact, and the whitepaper for the DNA-encoding design shared with MDC Platform.

mdc-lite v1.1.0

mdc-lite v1.1.0

No source changes to the crate itself since v0.1.0 — same 14 tests, same 5-function API, same 345 KB footprint. This release exists because rebuilding these exact artifacts from the previously-published instructions failed, and that's worth fixing properly rather than quietly re-uploading the same files under a new tag.

The bug, found by re-running our own docs

Following v0.1.0's Android build instructions exactly (CC_*/AR_* env vars only) reproduces a real failure:

ld: unknown options: --version-script=... --no-undefined-version ...
clang: error: linker command failed with exit code 1

CC_*/AR_* only satisfies the blake3 dependency's own C build script — a separate concern from cargo's own linker selection for the final Rust link step. Without CARGO_TARGET_<TRIPLE>_LINKER set explicitly, cargo fell through to the host's system linker (Apple's ld, which doesn't understand the ELF-target flags rustc was passing it) instead of the NDK's. Fixed in the README and docs site — verified by reproducing the failure, then reproducing the fix, before documenting either.

What's verified, honestly

Platform	Asset	Status
macOS (Apple Silicon)	mdc-lite-v1.1.0-macos-arm64.dylib	✅ Built natively; cargo test (14/14) passing on this exact target
Windows x86_64	mdc-lite-v1.1.0-windows-x86_64.dll + import lib	⚠️ Cross-compiled and linked (mingw-w64) to a real PE32+ DLL; not executed — no Wine available here
Android arm64-v8a / armeabi-v7a / x86_64	mdc-lite-v1.1.0-android-*.so	⚠️ Rebuilt with the corrected linker configuration, real Android NDK (r29); ELF format confirmed; not executed — no emulator/device on hand
iOS / watchOS	—	🛠️ No prebuilt artifact — requires full Xcode.app, not available in this build environment (an Apple distribution requirement, not a missing package)

Full detail: BUILD_INFO.md. SHA-256 for every asset in CHECKSUMS.txt below.

Docs

saji1970.github.io/ModelDB

mdc-lite v0.1.0

mdc-lite v0.1.0

An embeddable, encrypted key-value store for the places a server can't reach — a watch face, a phone app, a background service. XChaCha20-Poly1305 for every value and every key name, a 5-function API, no runtime.

Get it

Download a prebuilt build below for your platform, or build from source — grab mdc-lite-v0.1.0-source.tar.gz (or clone the repo) and run cargo build --release; full per-platform build commands (including iOS/watchOS, which has no prebuilt binary here — see why below) are in docs.html and the crate README.

What's verified, honestly

Platform	Asset	Status
macOS (Apple Silicon)	mdc-lite-v0.1.0-macos-arm64.dylib	✅ Built natively here; cargo test (14/14) passing on this exact target
Windows x86_64	mdc-lite-v0.1.0-windows-x86_64.dll + import lib	⚠️ Cross-compiled and linked (mingw-w64) to a real PE32+ DLL; not executed — no Wine available to run a Windows binary on macOS
Android arm64-v8a / armeabi-v7a / x86_64	mdc-lite-v0.1.0-android-*.so	⚠️ Built with the real Android NDK (r29) clang toolchain, ELF format confirmed; not executed — no emulator/device on hand
iOS / watchOS	—	🛠️ No prebuilt artifact. Apple requires linking against the real SDK, which ships only inside full Xcode.app — not a missing package, an Apple distribution requirement. Build from source on a Mac with full Xcode.

Full detail on exactly what "verified" means per artifact: BUILD_INFO.md. Every asset's SHA-256 is in CHECKSUMS.txt below.

Docs

saji1970.github.io/ModelDB — installation, quickstart, the on-disk format, the full security model (including why "quantum encryption" isn't the relevant concept for local storage), and platform key-custody guidance (Keychain/Secure Enclave, Android Keystore).