MoRSo · Segments of Origin · patent pending

The origin receipt says VALID.
The clip still lies.

A Media Origin Receipt proves a piece of footage is real and unaltered. Good. Now someone cuts a ten-second clip out of it. Every frame is authentic, the MoR still verifies, and the meaning is inverted. MoRSo is the receipt the clip carries. It builds on the parent and makes the cut itself visible: honest edits verify clean, meaning-altering edits do not.

You keep the footage. We keep the proof. Verify it in your own environment. It works even if we disappear.

8/8edit classes computed live, in your browser
ML-DSA-65FIPS 204 · derived receipt · offline-verifiable
0bytes of your media Hive ever receives

The problem a MoR alone can't solve

Provenance answers "is this footage real?" It does not answer "is this excerpt faithful to what was said?" A clip can inherit a perfect origin receipt and still remove the question, truncate the qualifier, or splice two answers together. So MoRSo runs the parent check and the segment check side by side.

Parent · Media Origin Receipt
✓ MoR VALID

Every frame in this clip is authentic. Seal reconciles. C2PA present. No pixel was fabricated.

Segment · MoRSo derived receipt
Select an edit

Pick an edit below. MoRSo classifies it against the boundary map sealed at capture.

This is the whole point. The parent stays VALID for every honest and dishonest cut alike. Real footage is real footage. MoRSo is the layer that tells a fair excerpt apart from a doctored one, using only boundaries the source sealed at capture. No editorial decision enters.

Run the eight edits

One sealed interview: Q1 [0 to 8s] · A1 [8 to 40s] · Q2 [40 to 46s] · A2 [46 to 92s]. The tail of A1 (30 to 40s) is the qualifier: "...but only under a court order." Every route below is worked out by the classifier built into this page, from the sealed boundary map alone.

FRAMING NOT ASSESSED. MoRSo checks faithfulness to the source record only. It never assesses whether a presentation is fair, balanced, or in good faith. It makes the mechanical edit visible, but a human still assesses the framing. That boundary is deliberate and permanent.

What is and isn't claimed

What MoRSo proves

The assembly of this excerpt against its sealed parent. Which spans it stitches together, in what order, and every boundary the cut crosses. Honest edits, like a cough, a stumble, dead air, or filler removed inside one answer, verify clean. Cutting a question, cutting off a qualifier, splicing across answers, and reordering all turn visible. The subject gets their own copy and can refute a distortion with proof, not just a denial.

Sealed boundary mapAssembly graphPosition + adjacency commit

What MoRSo never claims

It does not assess framing, fairness, or intent. That line ships in every route. It does not stop distortion. It makes distortion something you can disprove. It never sees your media: Hive gets fingerprints, never footage, transcript, or excerpt content. We can't hold your data, by design. And it only works on top of a MoR: no parent origin receipt, no MoRSo. If Hive vanishes tomorrow, the receipt still verifies with the public key you already hold.

Framing not assessedNon-possessionOffline verifier
← Media Origin Receipt See the full Canon table → Put MoRSo on your excerpts
MoRSo · Media Origin Receipt: Segments of Origin · patent pending · derived receipt, builds on a parent Media Origin Receipt · ML-DSA-65 / FIPS 204 · sig 3,309 B · pk 1,952 B · checkable offline, zero network calls · MoRSo checks faithfulness to the sealed source record only, never framing, fairness, or intent (FRAMING NOT ASSESSED ships in every verification output) · classification is mechanical, by reference to boundaries sealed at capture. No editorial decision enters · Hive never receives media, transcript, or excerpt content. Fingerprints only, we can't hold your data, enforced in CI · relocating a sealed boundary breaks the parent seal · the absence of a receipt is an affirmative, verifiable fact · we never fake a receipt · Hive Civilization · Wyoming, USA
Private by design. Hive does not store your prompts. Every request is already receipted by a one-way SHA-256 fingerprint, not the words. Proof, not surveillance.