Guide

PostSnail Architecture

Alpha 2 is deliberately forkable: a browser admin, static files, signed proofs, and an optional registry Worker.

Admin Modules

The browser admin uses small ES modules for encrypted local Shell storage, content normalization, Markdown sanitization, signing-key cryptography, encrypted workspace vaults, public ZIP export, legacy backup migration, and ZIP verification.

Workspace Format

.postsnail is a JSON envelope with non-secret metadata, AES-256-GCM ciphertext, PBKDF2-SHA-256 parameters, and a SHA3-512 workspace fingerprint. The decrypted payload is versioned workspace data.

Public ZIP Format

The generated ZIP contains HTML pages, assets, RSS, JSON feed, sitemap, .well-known/postsnail.json, post proof records, commit history, and postsnail.manifest.json. It excludes drafts and private workspace state.

Verification

The admin verifier recomputes SHA3-512 file hashes, canonical post record digests, post signatures, the manifest signature, and bundle fingerprint from a complete ZIP.

Forest Worker

Forest fetches public proof metadata, verifies signatures and digests, indexes site/post summaries in D1, and exposes search plus registration APIs.

Compatibility Layer

Protocol constants and compatibility helpers keep legacy manifests, workspaces, and ZIP exports working while new optional extensions are added safely.

Extend

Future tools can build new themes, alternate trackers, local deployment helpers, registry sync, or independent verifiers. Protocol-risk changes should use the PSEP process.