UncrushView build status

Implemented foundation

Current work,
without launch theatre.

This matrix is the public product boundary. It separates implemented engineering, later plans, and claims that current evidence does not support.

01

Status matrix

Current code · v0.1

Implemented

The native codebase analyzes supported MOV/MP4, creates verified same-container fast-start copies, and remuxes one closed QuickTime profile to verified MP4 while preserving H.264/AAC encoded media for the supported profile.

  • Bounded MOV/MP4 analysisReads the supported container profile with explicit limits and exact integer timing.
  • Canonical encoded-sample identityDescribes selected encoded video and audio samples in a stable, versioned form.
  • Direct safe-transform-v1 verificationCompares encoded payloads, timing, decoder setup, geometry, color, and audio meaning between supported files.
  • Native CLI foundationProvides analysis, identity, verification, verified same-container fast-start, and closed-profile MP4 remux commands.
  • Source-bound transformation planningBinds checked copy and rewrite actions to one exact immutable source snapshot.
  • Bounded streaming container writerCopies supported media through a reusable buffer without decoding or re-encoding it.
  • Verified faststart-v1Moves moov for same-container fast-start output and rewrites required absolute chunk offsets.
  • Generated-output re-analysisReopens the private candidate and analyzes it independently before publication.
  • Verified MOV-to-MP4 remuxConverts one closed QuickTime AVC/AAC wrapper profile to deterministic fast-start MP4 under safe-remux-v1.
  • Mandatory publication gatePublishes media only after the applicable safe-transform-v1 or safe-remux-v1 policy returns verified.

Current boundary

In development

Work on broader compatibility and conversion remains in development. It does not broaden the implemented closed profile today.

  • Broader compatibility and conversionFuture profiles require separate design, implementation, and preservation evidence before they can be called supported.

Later milestones

Planned

Browser/WASM processing, platform profiles, and controlled platform research require separate milestones and evidence.

  • Browser WASM processorIntended to run approved processing locally in a future browser experience.
  • Versioned platform profilesPlanned profiles will encode measured, reviewable preparation rules instead of folklore.
  • Controlled rendition experimentsLater research will compare retrieved delivery renditions under documented conditions.
  • Mobile applicationsiOS and Android experiences remain future work after the portable processing boundary exists.

Evidence boundary

Not claimed

Uncrush publishes platform-quality statements only after controlled, reproducible testing supports them.

  • No public processor yetThis website explains the work. It does not accept, transform, store, or upload video.
  • No proven TikTok-quality resultNo controlled rendition experiment has shown that Uncrush improves TikTok delivery quality.
  • No upload automationThere are no accounts, cloud media services, platform integrations, or automated uploads.
  • No decoded-media claimCurrent verification compares encoded samples and supported container semantics, not decoded pixels or audio.
02

Sequence

Now

The verifier comes before the processor.

  1. CompleteNative CLI foundation
  2. CompleteVerified faststart-v1
  3. CompleteVerified MOV-to-MP4 remux
  4. LaterBrowser WASM processor
  5. ResearchControlled rendition experiments