Zero Day Document Control

What is it?

ZDDC is a convention, not a platform. Every deliverable's filename encodes its tracking number, revision, status, and title; every transmittal folder is date-prefixed and self-describing. A plain shared folder becomes a fully searchable, auditable information-management system — no server, no database, no software required to read the archive.

The four tools below are optional interfaces around this structure. Each is a single self-contained HTML file that works two ways: open it locally and point it at a folder on your disk, or put it behind any web server (including the optional zddc-server described below) and use it over the network. Same on-disk layout either way.

Read the full specification →

Try the tools

Each tool is published in three channels. Stable is versioned and immutable; beta and alpha are mutable previews of in-flight work.

Append ?v=alpha (or ?v=0.0.4, etc.) to any URL to switch versions for a single request — useful for sharing a link to an exact build. Direct local-folder access requires a Chromium-based browser (the File System Access API is unavailable in Firefox / Safari). Browse all versions →

zddc-server (optional)

The tools work two ways over the same on-disk archive. Pick whichever fits your team:

zddc-server is a small Go binary purpose-built to serve ZDDC archives. Any web server gives you online mode; zddc-server adds things a generic web server can't:

• Access control via .zddc files. Behind a reverse proxy that authenticates users and sets an X-Auth-Request-Email request header, zddc-server consults YAML .zddc files in directories — cascading bottom-up; deeper rules override. No database, no admin UI.
• Virtual .archive URL space. GET /Project/.archive/123-XYZ.html resolves to the canonical revision file at request time. Computed from filenames; no cache, no separate index file.
• Per-request access logging keyed to the authenticated user.
• TLS, ETags, conditional GET, CORS, autoindex. The mundane glue.

The on-disk layout is the same in both modes. Stop the server and the directory is still a perfectly valid ZDDC archive that opens in local-directory mode. The server is convenience, not lock-in.

Source, environment-variable contract, container image, and ACL syntax: codeberg.org/VARASYS/ZDDC zddc/ · pre-built image at codeberg.org/varasys/zddc-server (channel-tagged :stable, :beta, :alpha).

Install on your server

Each option below is a short shell snippet. cd into your deployment directory, copy-paste one of the four blocks into your terminal, and the files land in CWD. All four use curl; nothing else to install.

set -eu
B=https://zddc.varasys.io
for t in archive transmittal classifier mdedit; do
  curl -fsSL "$B/releases/${t}_stable.html" -o "${t}.html"
done
curl -fsSL "$B/releases/landing_stable.html" -o index.html
mkdir -p _template
for t in archive transmittal classifier mdedit; do
  curl -fsSL "$B/bootstrap/level1/${t}.html" -o "_template/${t}.html"
done

set -eu
B=https://zddc.varasys.io/bootstrap/track-stable
for f in archive transmittal classifier mdedit index; do
  curl -fsSL "$B/${f}.html" -o "${f}.html"
done

set -eu
B=https://zddc.varasys.io/bootstrap/track-beta
for f in archive transmittal classifier mdedit index; do
  curl -fsSL "$B/${f}.html" -o "${f}.html"
done

set -eu
B=https://zddc.varasys.io/bootstrap/track-alpha
for f in archive transmittal classifier mdedit index; do
  curl -fsSL "$B/${f}.html" -o "${f}.html"
done

See bootstrap/README.md for the level-1 / level-2 model, the per-project / per-tool override pattern, and the audit grep that lets you see what every project on a deployment is pointing at.

Learn more

• Technical Reference — the full ZDDC convention: filename format, tracking numbers, revisions, status codes, folder naming, transmittal workflow.
• All releases — every version and channel build of every tool, with per-version pin URLs.
• codeberg.org/VARASYS/ZDDC — source code, issue tracker, contributor docs.