Technology

Measure it. Verify it.
Keep the record.

Every product here sits at a handoff: a card leaving a location, a drive leaving a vendor. Each is a different job on the same engineering. Nothing is released until it has been checked, the record is extended rather than edited, and a check that did not run is never reported as one that passed.

What the products share → Where each one stands

The engines · by product

DailiesDrop™: Transport · four bonded routes
: Scheduler · re-decides every 5 s
ShuttleCheck™: Conformance · infer, check, seal
: Custody · ASC MHL, extended

MVRK SYSTEMS · DOC MVRK-ARCH-00

01 · Shared engineering

Five commitments, held by
every product the same way.

The products do different jobs for different people. What makes them one company's work is that each makes the same five promises, and each can be held to them.

Commitment	DailiesDrop™	ShuttleCheck™
Verified before it is releasedthe gate, not a feature	A file is released to the destination only when its SHA-256 matches the source manifest.	The far end checks a sealed drive against its ASC MHL hash list, offline and with no account.
The record is extended, never editedcustody	The edge cache is held until a verified copy exists, and the status plate says when it is safe to format.	A seal never overwrites the one before it; the chain of custody extends. Renames are journalled and can be reverted.
Refuse, rather than degrade quietlyno false passes	A chunk that fails its check is re-queued, never delivered. Corrupt media is worse than late media.	Without ffmpeg, codec checks are reported as skipped, not passed. The checker reads; it cannot write.
State is a word before a colourreadable in one colour	Five lamps, seven states: solid when settled, pulsing when in progress or when it needs attention, blinking blue while footage is moving. Readable from across a set.	Every faceplate key carries a status line: what it found, or the one thing it is waiting for.
It runs without being askedapplied automation	The scheduler re-decides routes every five seconds; the operator never picks a mode.	The convention is worked out of a job you have already finished, then held against every new delivery.

02 · Transport · DailiesDrop™

One file, four routes,
one checksum.

A single connection is a single point of failure. The edge node treats every available link as one lane of a wider road (a house Ethernet line, two cellular carriers, a satellite dish), and the file exists whole again only on the machine that receives it.

Ethernet (wired, whenever the location has one) CELL A (bonded) CELL B (bonded) SAT (where there is nothing else)

Ingest and stageedge: The card stages to the internal NVMe cache as fast as it will read, and staging is complete before a byte leaves the box, so a dropped link never costs a re-copy.
Slice64 MB chunks: Files are cut into encrypted chunks, each with its own ordinal and hash, which is what lets four links of very different latency be treated as one.
Bondup to four routes: Throughput on each lane is measured continuously and the queue re-weights against it; a congested tower or an unplugged cable degrades the run, and does not stop it.
Stitch and verifyat the receiver: ShuttleCheck™ in receive mode reassembles the chunks on the post house's own machine and checks a SHA-256 against the source manifest; only a verified file is released, with an xxHash64 sidecar beside it.
Connectdirect, then relay: Transport is direct peer-to-peer by default: the control plane brokers the connection between the box and the receiving machine, and an encrypted relay carries the data only when a direct connection cannot be made. The box holds no storage credentials; the receiving machine places verified files into storage.

Integrity · controls

Transport: Direct peer-to-peer · encrypted relay only as fallback
Credentials: No storage credentials on the box
In flight: Per-chunk encryption
Ordering: Ordinal + per-chunk SHA-256
On arrival: SHA-256 against source manifest
Interop: xxHash64 sidecar, MHL-compatible
On failure: Chunk re-queued and re-allocated
Retention: Edge cache held until verified
Release: Webhook fires on verify only

MVRK SYSTEMS · DOC MVRK-ARCH-02

03 · Applied AI · the scheduler

Six mechanisms keep mismatched
pipes simultaneously full.

Bonding a 400 Mbps tower to a 20 Mbps dish is not a matter of splitting the file in half. Most of the work is in prediction and failure handling: estimating what each link will do next, and not mistaking a slow path for a broken one. No model is trained on your footage; the intelligence is in the decision-making, and it runs entirely on the box.

Deficit-weighted allocation

Each path is scored by goodput × urgency × cost. Work goes to whichever path will run dry soonest. Cost is a mild tiebreak only; never a reason to pick a cheap slow path over a fast one mid-transfer.

Adaptive stall detection

The stall threshold scales with the work in flight. A 64 MB chunk on a 20 Mbps dish legitimately takes 26 seconds, so a fixed timeout would bench a healthy satellite link on every chunk.

Automatic re-probing

A stalled path revives after twenty seconds and re-enters with small trial chunks. Without it, one tunnel or one underpass removes a path for the rest of the shoot.

Tail duplication

Past 95% complete, the oldest outstanding chunk is speculatively re-issued to any healthy path at least 1.5× faster. It costs a few hundred megabytes and removes the wait on one straggler.

Affinity routing

Chunks are tagged ANY, CHEAP_ONLY, or FAST_ONLY, and routes are filtered by affinity before scoring. This is what guarantees independent mode cannot quietly spend cellular data.

Starvation guard

A usable path idle for more than five seconds is force-fed work so its estimate cannot go stale, and no single throughput sample may exceed twice a path's observed peak.

Transfer modes · chosen, not set

Bonded: All routes serve one queue
Independent: RAW pinned to the flat-rate route
Standby: Metered route idle until others fail
Priority: PROXY · METADATA · RAW · BACKFILL

A 200 GB RAW BACKLOG NEVER DELAYS A 400 MB PROXY

The only genuine configuration A per-job deadline and a cellular budget, set once by the producer when the shoot is created. Nothing else is configurable, because nothing else should be.

The policy engine re-evaluates every five seconds against queue composition, available routes, deadline and the cellular budget, with a thirty-second minimum hold so it does not flap on a marginal link. Plugging in a network cable mid-shoot is a configuration change everywhere else; here it is a route appearing.

AGGREGATION PERFORMANCE WILL BE MEASURED ON HARDWARE, NOT SIMULATED · FIELD TEST PENDING

04 · Conformance · ShuttleCheck™

The rule is written down once,
and travels with the media.

A naming convention usually lives in a document nobody delivering to it has read. ShuttleCheck™ recovers the rule from work that already follows it, holds every new delivery to it, and seals it to the drive so the far end can check the delivery for itself.

Infershuttlecheck init: Work the convention out of a job you have already finished and write it down, rather than drafting it from a style guide and finding out later where it disagrees with practice.
Checkshuttlecheck validate: Hold a tree to the convention: names, structure, codecs, packages. It reports what does not conform and changes nothing, which is what makes it something a stranger will run on a live job.
Roll calldeclared against arrived: What was declared against what arrived, and which supplier owes the difference. The only check that can report a file that is not there.
SealASC MHL: A checksum per file and the rule beside it, written into the drive. A new seal extends the chain of custody; it never overwrites the one before.
Vendor packsone rule, many suppliers · licensed: Each supplier receives the rules for their own work, cut from the one convention.
Conform and revertlicensed: The one tool that writes over somebody's work. It prints a plan before anything moves, writes under a journal, and undoes a whole run in one press.

Exit codes are the contract: 0 conforms, 1 findings, 2 could not run. A delivery gate in CI is three lines. The six tools →

05 · Status language

State is a word before it is a colour.

Colour is reserved for state and never decorative, and no state is carried by colour alone: each survives a one-colour print, a screenshot in a ticket, and the commonest form of colour blindness. On a device that means behaviour as well as colour; on a screen it means a word.

DailiesDrop™ · five lamps, seven states


Power: Solid green · booted, voltage stable

Ingest: Pulsing amber · copying card to internal cache

Network: Blinking blue · streaming across bonded routes

Ready: Pulsing green · one verified copy, safe to eject

Ready: Solid green · two independent copies, safe to format

Error: Pulsing red · the cache is running out of room; attach a drive or a route

Error: Solid red · the unit has stopped: cache full, or something is not copying

SOLID = SETTLED · PULSING = IN PROGRESS OR NEEDS ATTENTION

ShuttleCheck™ · the faceplate

Nothing greyed out and unexplained

Six keys, one per tool, and the line under each is what that tool found, or the one thing standing between it and an answer.

Why no screen on the device

A screen is a thing to read

Anything with a menu invites configuration, and configuration on a wet camera cart at 2 a.m. is how footage gets lost. The plate reports state; the producer sets the deadline and the budget once, before the shoot.

06 · Roadmap

The parent is the engineering house.
The products say what they do.

Two are in hand: ShuttleCheck™ is published, and DailiesDrop™ is in development with pilots opening. Two more are named and not yet written; they are future work, not products, and would share DailiesDrop™'s transport and its receiver.

In development · pilots opening

DailiesDrop™

Zero-UI edge ingestion. Card in, cloud out, across a bonded uplink. Functional prototypes at ISE 2027.

Specification → Python package on PyPI · free, no account

ShuttleCheck™

Naming and delivery conformance. The convention written down, checked against the media, and sent with the drive so the far end can check it too.

What it checks →

Future work · not in development

CueSync™

Automated live-show showcalling. Cue stacks driven from the same orchestration layer that moves the media, so the show and the media never drift apart.

Future work · not in development

StatCast Edge™

Real-time sports telemetry. Field-side capture and distribution for broadcast rights-holders, on the same chassis discipline.

Technical review

Bring us the case that breaks things.

A dead cell zone on a terabyte day, a vendor list nobody has written down. Those are the interesting ones.

Talk to engineering → What the products share

Measure it. Verify it.Keep the record.