No description
Find a file
ZDDC cf4101b9e4 build(zddc-server): use tini as PID-1 entrypoint
Adds tini to the runtime image and routes ENTRYPOINT through it so
zddc-server runs as PID 2 with proper orphan reaping and signal
forwarding. Today zddc-server is a single-process server and the change
is invisible; the motivation is the upcoming render path that will
shell out to pandoc (which itself shells out to xelatex / lua filters /
dot) — any grandchild orphaned by a mid-run crash gets reparented to
PID 1, and a Go server is not the right thing to put in charge of
reaping subprocesses it never spawned.

tini is ~24KB and does exactly this one job. Putting it in the upstream
image (rather than each downstream consumer's Dockerfile) means every
deployment of codeberg.org/varasys/zddc-server gets the fix for free,
including the Burns & McDonnell prod chart wrapper that's about to land.

Cut a new release with `sh release-image.sh <version> stable` to
publish.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-29 10:02:57 -05:00
archive feat(archive,landing): local-mode ?projects= filter + ?v= propagation 2026-04-28 17:24:07 -05:00
bootstrap refactor: rename channel 'latest' to 'stable' across all artifacts 2026-04-28 09:30:24 -05:00
classifier feat(build): symlink website/releases/<tool>_alpha.html into dist instead of copying 2026-04-28 14:01:41 -05:00
landing feat(archive,landing): local-mode ?projects= filter + ?v= propagation 2026-04-28 17:24:07 -05:00
mdedit feat(build): symlink website/releases/<tool>_alpha.html into dist instead of copying 2026-04-28 14:01:41 -05:00
pandoc Initial commit 2026-04-27 11:05:47 -05:00
shared fix(build): copy dist into website/releases/<tool>_alpha.html instead of symlinking 2026-04-28 18:41:27 -05:00
tests feat(archive,landing): local-mode ?projects= filter + ?v= propagation 2026-04-28 17:24:07 -05:00
transmittal feat(build): symlink website/releases/<tool>_alpha.html into dist instead of copying 2026-04-28 14:01:41 -05:00
website fix(build): copy dist into website/releases/<tool>_alpha.html instead of symlinking 2026-04-28 18:41:27 -05:00
zddc build(zddc-server): use tini as PID-1 entrypoint 2026-04-29 10:02:57 -05:00
.gitignore Initial commit 2026-04-27 11:05:47 -05:00
AGENTS.md fix(zddc-server): per-revision .archive entries + global index with ACL filter 2026-04-29 06:33:32 -05:00
ARCHITECTURE.md feat(web): releases index, alpha+beta channel builds, inline server section 2026-04-28 10:00:10 -05:00
build.sh chore(release): default to alpha cascade; tidy stale CI references 2026-04-28 18:17:16 -05:00
CLAUDE.md fix(build): copy dist into website/releases/<tool>_alpha.html instead of symlinking 2026-04-28 18:41:27 -05:00
dev-server Initial commit 2026-04-27 11:05:47 -05:00
freshen-channel feat: freshen-channel helper and channel-discipline protocol 2026-04-27 13:43:42 -05:00
LICENSE.txt Initial commit 2026-04-27 11:05:47 -05:00
package.json Initial commit 2026-04-27 11:05:47 -05:00
playwright.config.js Initial commit 2026-04-27 11:05:47 -05:00
README.md refactor: rename channel 'latest' to 'stable' across all artifacts 2026-04-28 09:30:24 -05:00
release-image.sh chore(release): default to alpha cascade; tidy stale CI references 2026-04-28 18:17:16 -05:00

Zero Day Document Control (ZDDC)

The Universal Distributed Filing Cabinet

ZDDC is an information management convention plus a small set of single-file HTML tools. 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 archive — no server, no database, no software required to read it.

The name "Zero Day Document Control" comes from the convention itself — adopt it on day zero of a project, with no setup time. The tools are optional interfaces around the structure; the structure works without them.

For end users: https://zddc.varasys.io/ introduces the project, links to all tool channels (stable / beta / alpha), and offers install.zip for self-hosted deployments.

Tools

Tool What it does
Archive Browser Browse, search, and filter a project archive folder. Group by transmittal, export selections as ZIP.
Transmittal Creator Self-contained HTML transmittal records with SHA-256 checksums and optional digital signatures.
Document Classifier Spreadsheet-like bulk-renamer that copy/pastes with Excel and writes back to disk.
Markdown Editor Browser-based markdown editor with YAML front matter, TOC, and direct local file access.

Each tool is published in three channels (stable, beta, alpha) at https://zddc.varasys.io/releases/<tool>_<channel>.html. Append ?v=alpha (or ?v=0.0.4, etc.) to any URL to switch versions for one request. See bootstrap/README.md for the install / pin / audit story.

File-naming convention

The full specification — filename format, tracking numbers, revision rules, status codes, folder naming, and the transmittal workflow — lives at https://zddc.varasys.io/reference.html.

Quick example: 123456-EL-SPC-2623_A (IFR) - Specification For Switchgear.pdf

Build & develop

git clone https://codeberg.org/VARASYS/ZDDC.git && cd ZDDC

sh build.sh                              # build all tools (writes to dist/ only)
sh archive/build.sh                      # build one tool

sh archive/build.sh --release            # cut stable; auto-bumps patch from last tag
sh archive/build.sh --release 0.1.0      # explicit version
sh archive/build.sh --release alpha      # cut alpha (mutable channel, no tag)
sh archive/build.sh --release beta       # cut beta

npm install && npx playwright install chromium && npm test    # tests
./dev-server start                       # cache-busting HTTP on :8000

Authoritative build/release docs are in AGENTS.md. Architecture notes (single-file rationale, JS module pattern, security model) are in ARCHITECTURE.md. zddc-server (optional Go HTTP server with ACL and a virtual archive index) is in zddc/README.md.

Contributing

ZDDC is an open source project hosted on Codeberg at https://codeberg.org/VARASYS/ZDDC. Bug reports, feature requests, and pull requests welcome.

ZDDC is designed for zero configuration to start and minimal configuration overall — feature proposals are filtered through that lens.

License

GNU Affero General Public License v3.0. Free to use, modify, and distribute, including commercially, under the terms of the license. Provided "as is" without warranty.