ROOTDRIFTER//DRIFTDECK
DRIFTDECK is the management suite comprising the Splice video module and the Quill document module — local-first pipelines built for practitioners who keep their assets on their own hardware. No cloud processing, no upload gates, no hosted inference. Your files stay on your machine; DRIFTDECK gives you the tools.
rootdrifter's utilities
Application Composer
Rank opportunities, compose the application, send by hand.
A local-first word processor for applications. It keeps a ranked, de-duplicated log of opportunities fed from your own files, then composes and renders drafts from your corpus and templates — deterministically, offline, with identity placeholders left unfilled until you send by hand. Dry-run is the default; nothing is sent automatically.
- Status: Live
- Status panel — token-gated; the composer itself runs on your own machine.
- Open →
Video Assembler
Cut, proxy, assemble and render — originals never touched.
A local video-assembly orchestrator. It turns an edit list into a reviewable trim plan, assembles and renders low-resolution proxies, and keeps an append-only run ledger with refusals recorded at the same weight as passes. Original recordings are never modified; every step is dry-run first and prints the exact command it would run.
- Status: Staged
- Runs on your own machine — no web surface yet.
Open market
The open market lists open-source utilities made by fellow drifters. To list yours: publish the source under an open licence, write a module manifest (see the manifest spec), and send the link through the contact page. Listings are reviewed by hand before they appear.
The manifest spec is not published yet; it will live at https://rootdrifter.io/deck/manifest/
Status boards
Your deck
Sign in to keep your own deck of utilities — pick from the catalogue above and arrange it your way.
or use the site sign-in:
Local-first by design
Both modules share a single principle: the deterministic core runs entirely on your hardware. Masters, documents, and provenance records never leave your storage unless you explicitly export them. The suite ships the tools; the processing is always yours.
BYO-AI — optional, fully self-directed
The deterministic core of each tool needs no AI. If you want AI-assisted features, the pipeline accepts three connection patterns — all operator-controlled, none hosted by DRIFTDECK:
MCP server
Connect your own Claude instance via the Model Context Protocol. You supply the session; the tool exposes the interface.
API key
Bring your own API key for any supported provider. Calls go directly from your machine to the provider — no relay, no proxy.
Local models
Point the tool at a local model endpoint. No external network required — fully air-gapped operation is supported.