Domain
Video, broadcast and production; networking and transport.
The engineering spine
CueSeal's research runs on a modular corpus covering the overlap between audiovisual-over-IP engineering and applied AI — the part most learning resources treat as two separate fields with two separate vocabularies. It is written to be loaded a module at a time, by a person or by a model, and everything non-trivial is cited to a publisher.
Released under CC BY 4.0 · not yet published openly
Module 00 is the always-on core: identity, principles, conventions, citation policy, and a router that decides which of the rest to pull for a given task. The other twelve are loaded on demand so working context stays lean.
Broadcast and software use the same words for different things — “frame”, “stream”, “buffer”, “reference”. Each glossary owns one sense and cedes the others to its counterpart rather than duplicating them.
Video, broadcast and production; networking and transport.
AI/ML engineering; software engineering and DevOps.
The operating vocabulary (cue-then-seal, holdover, the three planes) and the engineering glossary.
Each appendix takes a concrete system through the module rigor — threat model, evals, acceptance criteria, artifacts — rather than describing it in the abstract.
A worked spec: deterministic rules, golden vectors, and the failure modes a naming layer has to survive.
A human-directed studio and civic-video pipeline: shared threat model, safety evals distinct from accuracy, and a two-stage anti-hallucination binder.
Provenance and verification workflow for a working newsroom, with the human gates drawn explicitly.
A worked example carrying cue meaning end to end and re-attesting it at every hop.
Each platform charter scopes what that plane owns and where it defers to the shared control room. The strategy thesis spans all three.
Live / timing / transport — PTP, ST 2110 / NMOS, air-path monitoring.
Encode / package / assembly — ladder economics measured against golden references.
Meaning / metadata / provenance — extraction, verification, durable attestation.
Why the operability layer, not the model layer, is where the durable engineering work sits.
Access
The corpus is released under CC BY 4.0 but is not published openly yet — it is still moving fast enough that a public snapshot would be out of date on arrival, and the source-authority index (module 12) is mid-pass. If you want to read it, ask and we will send it.
Researchers, broadcast engineers, and anyone working on trustworthy media infrastructure are all welcome to ask. Tell us roughly what you are working on so we can point you at the right modules rather than dumping the whole set on you.