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.
Modules
Splice
A local video cut, proxy, and conform pipeline. Source masters stay read-only on your own disk — Splice works from proxies, produces a cut, and conforms back to the master when you are ready. The processing runs entirely on your machine; nothing leaves your storage.
- Proxy-first workflow — originals never modified
- Frame-exact timeline cuts and render output
- Conform back to master on demand
- Zero network dependency at runtime
Quill
A local document compose, lint, and provenance pipeline. Draft, validate, and track the lineage of your documents locally. Nothing is sent anywhere by the tool — Quill operates fully offline from input to signed output.
- Compose and lint documents without leaving your machine
- Provenance tracking built into the pipeline
- Export to multiple target formats
- Zero network dependency at runtime
Utilities
Operational surfaces of the suite — read-only status projections of the tools in operation. Each panel shows verdicts, counts, and states; content never leaves the operator's machine.
Quill · status panel
Staged status snapshot of the Quill document pipeline — run verdicts, gate queue, provenance counters. Baked at stage time; freshness is the printed timestamp.
Open →Console Suite
Cross-module status board — latest run verdicts and the append-only output ledger, refusals kept with the same weight as passes.
Open →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.
Access
Downloads and documentation are available to members. Access is invite-only.
Already a member? Use the sign-in link above — no separate account needed.