Web/A in One Deck

An archival document format that makes reading, sharing, and verifying possible with a single HTML file.

Context

Why Web/A

  • PDF is durable, but weak in structure, verification, and evolution
  • The Web is flexible, but weak in long-term preservation
  • Teams need both easy distribution and trustworthiness

HTML-Complete by Design

  • Single-file HTML delivery
  • Fonts and assets embedded
  • Designed to stay readable for decades

The 4-Layer Model

  • Layer 1: The Template (Definitions)
  • Layer 2: The Data (Encrypted Facts)
  • Layer 3: The Context (Routing & Metadata)
  • Layer 4: The Presentation (UI & Layout)
Web/A Document (.html) Layer 4: Presentation (UI / View) CSS, Fonts, display logic Layer 3: Context (Metadata / Routing) Transport Tag, Expiry, Nonce, Policy Ref Layer 2: Data (Facts / Records) Encrypted payload, User Signature (VP) Layer 1: Template (Definition / Core) Human Readable HTML / Template Bound Machine Readable JSON-LD / Logic Issuer Signature: Ed25519 + PQC

Strength 1: Distribution Simplicity

  • Send one file
  • Open with any browser
  • Eliminate environment drift

Strength 2: Built-in Authenticity

  • Embedded signatures for tamper detection
  • Passkeys for holder binding
  • Verification logs baked in

Web/A Form

  • Low-frequency, high-value workflows
  • Create, sign, and submit inside the browser
  • Local aggregation with HTML-based aggregator

Web/A L2 Encryption

  • Encrypted for recipient-only access
  • Bound to Layer 1 template via AAD
  • Designed for Passkey-first UX

Web/A Folio

  • A personal/organizational data container
  • Bundle history, proofs, and records
  • Structured for AI collaboration

AI-First Workflow

  • Agents can read structure + signatures
  • Assist input, summarize, verify
  • Built on Human-Machine Parity

Presentation Mode

  • This page becomes a sales deck
  • Full-screen slideshow from the same HTML
  • Share, archive, and present with zero extra tools

Summary

  • Web/A is an HTML-native document platform
  • Balances preservation, distribution, and verification
  • Turns static documents into usable artifacts

Next Step

  • Try the Web/A Form Maker
  • Convert an existing doc into Web/A
  • Apply Web/A to your internal workflows