No description
Find a file
ZDDC 33ce3886f2 fix(form,browse): drop divergent local overrides of shared chrome
Two more half-contract leaks surfaced by sweeping shared chrome class
usage across tools:

1. form/ had its own design-token namespace (--color-primary,
   --color-bg, --color-text, --color-border, --color-bg-alt,
   --color-text-muted) defined nowhere but fallback'd to hardcoded
   hex values different from shared (#1e3a5f vs shared's #2a5a8a).
   Form's buttons, inputs, fieldsets, array-row borders, and status
   colors all rendered with subtly different palette than the rest
   of the suite.

   Form also redefined .btn, .btn-primary, and a (form-local)
   .btn-small class — the redefinition shadowed shared/base.css's
   button system entirely. Form's JS used 'btn btn-small' for the
   add/remove row buttons in form-array widgets.

   Fixes:
   - form/css/form.css: rename every --color-* reference to the
     matching shared token (--primary, --bg, --bg-secondary, --text,
     --text-muted, --border, --radius, --danger, --success).
   - form/css/form.css: delete the .btn / .btn-primary / .btn-small
     blocks entirely. Shared covers .btn / .btn-primary /
     .btn-secondary / .btn-sm / .btn-lg / .btn-link.
   - form/js/array.js: switch the row add/remove buttons to
     'btn btn-sm btn-secondary' so they pick up shared's sizing
     and outline variant.
   - tests/form-safety.spec.js: update the selector
     button.btn-small → button.btn-sm.

2. browse/ had .hidden { display: none !important; } — exact
   duplicate of shared/base.css's rule. Delete the redundant copy
   (left a one-line comment pointer in case anyone wonders why
   it's missing from the local sheet).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-10 14:16:23 -05:00
.forgejo fix(build,ci): auto-commit embedded refresh on beta cuts; pin chart to HEAD 2026-05-05 20:48:09 -05:00
archive fix(shared): .header-left/.header-right belong in the shared chrome rule 2026-05-10 14:09:23 -05:00
browse fix(form,browse): drop divergent local overrides of shared chrome 2026-05-10 14:16:23 -05:00
classifier fix(shared): .header-left/.header-right belong in the shared chrome rule 2026-05-10 14:09:23 -05:00
form fix(form,browse): drop divergent local overrides of shared chrome 2026-05-10 14:16:23 -05:00
helm fix(client): plug confused-deputy bind in client mode 2026-05-08 10:03:51 -05:00
landing refactor(landing): project landing is now a single-file SPA, not server-rendered 2026-05-10 07:57:30 -05:00
mdedit fix(shared): .header-left/.header-right belong in the shared chrome rule 2026-05-10 14:09:23 -05:00
pandoc Initial commit 2026-04-27 11:05:47 -05:00
shared fix(shared): .header-left/.header-right belong in the shared chrome rule 2026-05-10 14:09:23 -05:00
tables feat(shared): clickable logo links every tool's header to project home 2026-05-10 07:34:28 -05:00
tests fix(form,browse): drop divergent local overrides of shared chrome 2026-05-10 14:16:23 -05:00
transmittal feat(shared): clickable logo links every tool's header to project home 2026-05-10 07:34:28 -05:00
zddc chore(embedded): cut v0.0.17-beta 2026-05-10 14:09:33 -05:00
.gitignore test: add tests/data/test-archive.sh — synthetic ZDDC fixture builder 2026-05-08 09:03:38 -05:00
AGENTS.md docs: correct tool/artifact counts to eight tools / nine artifacts 2026-05-09 18:38:58 -05:00
ARCHITECTURE.md docs(architecture): state-mgmt patterns, zddcMode dispatcher, polyfill gaps 2026-05-09 18:48:33 -05:00
build fix(build): drop dead form.html reference in embedded-commit step 2026-05-09 20:13:21 -05:00
CLAUDE.md docs: correct tool/artifact counts to eight tools / nine artifacts 2026-05-09 18:38:58 -05:00
deploy refactor: separate website repo + deploy-host model 2026-05-02 09:14:40 -05:00
dev-server Initial commit 2026-04-27 11:05:47 -05:00
freshen-channel refactor: separate website repo + deploy-host model 2026-05-02 09:14:40 -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 feat(shared): clickable logo links every tool's header to project home 2026-05-10 07:34:28 -05:00
README.md docs: correct tool/artifact counts to eight tools / nine artifacts 2026-05-09 18:38:58 -05:00
SECURITY.md docs: add SECURITY.md (vulnerability disclosure policy) 2026-05-04 17:53:13 -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 prints copy-paste shell snippets to install on a self-hosted deployment.

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.
Form Renderer Schema-driven *.form.yaml editor — every form spec auto-mounts an editable form at <name>.form.html.
Tables Sortable, filterable, in-place-editable grid view over a directory of YAML rows; click a row → edit in the form renderer. Auto-mounts on any directory containing a table.yaml.
Browse File-tree navigator with previews; the everywhere-available companion to the Archive Browser when you want plain folder navigation rather than tracking-number aggregation.
Landing The project picker served at the deployment root of a zddc-server.

Each tool is published in three channels (stable, beta, alpha) as static files served from https://zddc.varasys.io/releases/. Local use: download a .html file from releases/ and open it in a browser. Server use: run zddc-server — the current-stable build of every tool is baked into the binary at compile time, so a fresh deployment Just Works with zero config. Tools auto-appear at folder-name-driven paths (archive everywhere; classifier in Incoming/Working/Staging; mdedit in Working; transmittal in Staging). Override per-directory by writing an apps: entry in any .zddc file (channel/version/URL/path). URL overrides are fetched once and cached in <ZDDC_ROOT>/_app/; drop a real .html file at any path to override entirely.

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

./build                                  # dev build of every tool (writes to dist/ only)
sh archive/build.sh                      # iterate on one HTML tool

./build alpha                            # lockstep alpha cut for all nine artifacts
./build beta                             # lockstep beta cut
./build release                          # lockstep stable, coordinated next version
./build release 1.2.0                    # lockstep stable at explicit version

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. Example Helm charts for deploying zddc-server (production + dev) are under helm/.

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.