CareTV Open Media Fabric
Today the pieces are converging: common storage, 100Gb networking, portable GPU workstations, open surveillance, browser-driven television, remote access, and AI indexing can become one reusable open-source media layer instead of a pile of unrelated boxes and cloud-transfer workflows.
Working idea: JavaScript/Chrome is the visible head. Native Windows/Linux services do deterministic real-time media work underneath. Shared storage makes every workstation disposable, replaceable, and immediately useful.
1. What changes once common storage is online
Capture anything → stream it → identify it → index it → store it → make it immediately addressable.
Workstations stop being permanent islands of files. A workstation can use a fast local 4TB NVMe as a working tier, while CareTV indexes new material in the background and transfers verified copies to the server pool over 100GbE. Large 8TB SSDs remain centralized in the storage server rather than duplicated across every workstation.
The authoritative namespace remains machine-independent. On Windows, StableBit DrivePool can present the current pool. Later, the same media drives can move to a Linux rack server and be presented through an open pooling layer while keeping the same logical CareTV paths and portable indexes.
2. The workstation we actually want
Today’s physical comparison made the requirement clearer than a benchmark chart could: avoid both extremes. Do not buy another ultra-compact machine whose NVMe sockets require archaeological disassembly, and do not make the standard office machine an enormous tower that is miserable to move or reach behind.
Portable, not miniature
Small enough for one person to carry safely between floors and easy to grip, but large enough to service without dismantling the computer.
GPU expansion
Physical, electrical, thermal and PSU support for an RTX 5090-class GPU.
100GbE is mandatory
Room for the existing dual-port 100Gb QSFP28 NIC at the same time as the large GPU.
One more real slot
Preserve another genuinely usable PCIe expansion position for a second GPU, video I/O, capture, networking or a future accelerator.
Easy NVMe
Open panel → see M.2 → replace drive → close panel. No motherboard extraction, hidden sockets or multi-hour disassembly.
Standard parts
Prefer ordinary replaceable ATX/mATX-style components over proprietary workstation internals.
128GB+ RAM4TB local NVMeRTX 5090-readydual-port 100GbEextra PCIecarryableserviceable
3. 100GbE becomes the house media backbone
The already-purchased MikroTik 100Gb switch becomes the high-speed hub. A permanent fiber path between the office and garage means we do not need a forest of point-to-point cables or huge storage arrays inside each workstation.
Thunderbolt remains useful as an overflow or laptop expansion technology—especially for fast SSD access on the laptop-server—but it is not the foundation of the desktop architecture.
4. Universal CareTV media service
The next software layer is a reusable native service derived where useful from open OBS Studio media code, but without OBS as the end-user application. OBS is no longer the head. JavaScript is.
Native service owns
- capture and decode
- frame queues and clocks
- audio/video synchronization
- GPU surfaces and media buffers
- encoding
- recording
- IP streaming
- hardware/device interfaces
JavaScript / Chrome owns
- layout
- source selection
- nonlinear programming logic
- titles and overlays
- multilingual presentation
- controls
- configuration
- operator/player experience
The service should expose low-latency local media surfaces to JavaScript while also producing configurable IP streams of the final program state. Chrome can be the visual head without being responsible for real-time frame deadlines.
5. 8K nonlinear multilingual television
CareTV does not need a physical 8K monitor or a DeckLink capture path merely to operate on 8K media. The internal canvas and buffers can remain 8K60 while the workstation operator uses a practical 4K viewport.
Short translated segments can be queued nonlinearly and scheduled frame-accurately. JavaScript can use GPU-accelerated composition for titles, captions, lower thirds, clocks, translated text, graphics and layout. The native service then captures/encodes the final composed program surface so the same result can be streamed to YouTube or other IP destinations.
The original giant Blackmagic workstation can become an optional specialty ingest node rather than dictating the size and ergonomics of the everyday workstation.
6. Open surveillance replaces the proprietary DVR model
Cameras become network media sources rather than channels owned by a proprietary DVR. CareTV nodes can ingest open camera streams, record originals, analyze selected frames, retransmit streams, and present arbitrary browser layouts.
The goal is horizontal expansion: add cameras, then add processing/storage nodes as needed. Recording, AI analysis, viewing and storage do not need to be the same process or even the same machine.
Recording
Preserve original compressed camera streams wherever possible instead of needlessly re-encoding everything.
Analysis
Independent AI processes can subscribe for detection, transcription, event classification, indexing and search.
Viewing
JavaScript provides 1/4/9/16/variable grids, full-screen views, timelines, PTZ controls and event navigation.
Storage
Local NVMe can absorb bursts; verified recordings migrate into the common CareTV storage namespace.
7. The same video layer becomes remote KVM
The screen-streaming service can double as a cross-platform remote console. The video plane sends the desktop/program surface; a separate control plane sends keyboard, mouse, touch and related events back to the target.
This makes basement and garage machines practical headless appliances and, importantly, can remove manual testing labor from software iteration. Instead of repeatedly walking to another machine, taking screenshots and reporting results, CareTV can increasingly observe the result, collect telemetry and exercise software remotely.
A separate out-of-band recovery path remains desirable for BIOS/UEFI or total-OS-failure access.
8. Phones, tablets, laptops and desktops become capture endpoints
Windows, macOS/iOS and Android endpoints should be able to send screen, camera and microphone media directly over the local network to CareTV recording/indexing storage. Wi-Fi 6/7 devices use the same ingest model as wired workstations, just at different bandwidths.
The intended result is to eliminate routine dependence on iCloud, OneDrive and Google Drive file-transfer loops merely to move media between the device that created it and the machine that needs to process, index or demonstrate it.
9. Hard design rules emerging today
- 100GbE is not optional on the primary workstation/server class.
- RTX 5090-class expandability is not optional.
- The 5090 and dual-port 100Gb NIC must coexist without blocking each other.
- Preserve another useful PCIe expansion path when practical.
- Do not buy machines that require extensive disassembly for routine NVMe service.
- Do not make the recommended office machine so large or heavy that moving it becomes a problem.
- Use local NVMe for speed; use common storage for durability and machine independence.
- Keep indexes portable across Windows DrivePool today and Linux storage later.
- JavaScript is the visible head; native services own deterministic real-time media work.
- Prefer open protocols and open-source components over vendor-locked DVR/media ecosystems.
10. Why this is suddenly close to an actionable beta
Many of the previously separate experiments now collapse into the same primitives: fast shared files, live video buffers, recording, indexing, JavaScript composition, network streaming, remote viewing, remote control and distributed compute.
The first beta does not need to solve everything. It needs to prove that one CareTV service can ingest media, expose it locally, record it into the common storage model, index it, and let JavaScript control what is seen and streamed.
Once that primitive works reliably, 8K television, surveillance, remote KVM, phone capture, AI naming and distributed rendering become extensions of the same architecture rather than separate products.
11. Immediate next build sequence
- Finish the common Windows file/storage service and portable CareTV index.
- Select the standard carryable workstation chassis/platform with 5090 + dual-port 100GbE + extra PCIe room.
- Bring up one 100Gb workstation-to-core link.
- Create the first headless CareTV Windows media service.
- Expose one live/local video source to JavaScript in Chrome.
- Record that source to the CareTV storage namespace while indexing it.
- Emit an IP stream representing the exact JavaScript-selected program state.
- Add one open IP surveillance camera as another source.
- Add remote keyboard/mouse control as the first KVM loop.
- Then scale outward instead of rewriting the foundation.
Working destination
https://8k.art/beta/_daily-build/2026-08-26/
Suggested filename: caretv-open-media-fabric-idea-spec-v001.html