A formal WDS deployment record for production deployments (what changed, version/commit/snapshot, build command and result, deployment target/env, deploy time, verification steps)
Post-deploy route-checking records for key routes
An accessibility checklist and recorded accessibility verification for public deployment
A rollback or restore note (manual or automated procedures)
A monitoring expectations note (uptime monitoring status, cadence, alerting channels)
Static asset organization notes (documented layout and generation/source provenance)
Release or publication notes / changelog tied to deployments
Create a deployment-record template and backfill the most recent production deploy: site id/domain, commit or content snapshot, build command & result, target env, deploy time, verification steps
Run and record post-deploy route checks for key routes listed in sitemap.xml, storing results alongside the deployment record
Produce an accessibility checklist and run an accessibility audit for production pages; attach results to the deployment record
Document rollback and restore expectations (manual steps and any automated restore scripts)
Add a monitoring expectations document — cadence, alerting, whether uptime is actively monitored vs. manual review — linked to mirror-status.json's publication process
Automate deployment-record generation as part of the build/deploy script (git commit, build output, timestamps, route checks, accessibility results)
An automated post-deploy route and HTML metadata checker (validate title/description/JSON-LD presence)
Lightweight uptime monitoring (internal pings or external checks), surfaced to the operator via email/Telegram
GPG verification and signed manifests for snapshot releases and ISO artifacts, for improved provenance
An operator-facing runbook consolidating manifest editing, mirror adding, rsync commands, and troubleshooting steps
Creative enhancements (ideas on file, not committed)
An operator "reconstructibility" dashboard surfacing items marked reconstructible by AI, showing provenance chains, and queuing automated reconstruction jobs
An offline operator utility (Tauri/Electron) mirroring key dashboards and allowing local verification/rsync command generation for air-gapped environments
A compact "archive DOI" mechanism — stable content-addressed identifiers and JSON-LD records referenceable by external research papers and datasets
P2P gateway integration (BitTorrent webseed + optional IPFS mirror) for high-resilience distribution of critical snapshots
An LLM-driven changelog summarizer auto-generating human-readable release notes from deployment records, schema diffs, and mirror-status changes