FORGESITE

> 1. The Phone Booth Concept

> 2. Chain-Verified Publishing

Every page deployed through ForgeSite gets a chain transaction. The content is hashed. The hash is written to BSV via OP_RETURN. The transaction ID is embedded in the page itself.

Visitors see a "Verify This Page" button. Click it. The page computes its own hash, fetches the chain record, and compares. If they match, the page is authentic. If they do not match, something changed after chain stamp. No trust required. The math is the proof.

DEPLOY PIPELINE:

  build page (HTML/CSS/JS)
    |
    v
  compute SHA-256 hash of content
    |
    v
  write hash to BSV (OP_RETURN)
    |
    v
  embed TX hash in page metadata
    |
    v
  rsync/SSH to sovereign server
    |
    v
  sibling node verifies deployed content matches chain record

VISITOR VERIFICATION:

  [VERIFY THIS PAGE]
    Chain TX:   pending...
    Content:    sha256:a1b2c3d4...
    Deployed:   2026-03-13T15:30:00Z
    Status:     VERIFIED (hash match)
      

This is not a gimmick. This is the core value proposition. Every page on the internet can be silently modified by the hosting provider, the CDN, a man-in-the-middle, or a compromised server. ForgeSite pages carry their own proof of authenticity. The chain is the notary. The visitor is the auditor.

> 3. The Lilac Inn Proof

> 4. Ecosystem Integration

ForgeSite is the public face of the Forge ecosystem. Every product that needs a web presence flows through it.

> 5. Technical Architecture

5.1 Deploy Pipeline

LOCAL BUILD
  |
  +-- Template engine processes source files
  +-- Static assets optimized (images, CSS, JS)
  +-- HTML generated from templates + content
  |
  v
CHAIN STAMP
  |
  +-- SHA-256 hash computed for each page
  +-- Hash written to BSV via OP_RETURN
  +-- TX hash embedded in page <meta> tag
  +-- Manifest file: { page: hash, tx: txid, timestamp }
  |
  v
DEPLOY
  |
  +-- rsync over SSH to sovereign server
  +-- Post-deploy verification by sibling node
  +-- Overlay indexes new/updated pages
  +-- ForgeHard verifies SSL + CSP headers active
  |
  v
LIVE
  |
  +-- "Verify This Page" button active
  +-- ForgeServe monitoring uptime
  +-- ForgeView tracking analytics
      

5.2 Chain Stamp Format

OP_RETURN payload:
  protocol:   FORGESITE_V1
  action:     DEPLOY | UPDATE | VERIFY
  page_hash:  sha256 of page content
  page_path:  relative URL path
  timestamp:  ISO 8601
  node_id:    deploying node identifier
  manifest:   hash of full site manifest (on full deploys)
      

5.3 Template Engine

ForgeSite uses a minimal template engine. No React. No Next.js. No webpack. HTML, CSS, and JS. The output is static files that any server can serve. The complexity is in the chain integration, not the frontend framework.

Templates:
  base.html         -- nav, footer, matrix-rain, BSV banner
  gallery.html      -- image grid, lightbox, artist bio
  blog.html         -- post list, single post, RSS feed
  storefront.html   -- product grid, cart, ForgePay checkout
  profile.html      -- social identity, links, verification
  publication.html  -- research paper, citations, DeSci metadata

Build:
  forge-site build              # compile templates + content
  forge-site stamp              # chain-stamp all pages
  forge-site deploy             # rsync to server
  forge-site verify             # sibling verification
  forge-site build-stamp-deploy # full pipeline, one command
      

5.4 Migration Tools

ForgeSite includes scrapers for the platforms it replaces. Wix, Squarespace, WordPress: export your content, rebuild on sovereign infrastructure. The Lilac Inn rescue proved the pipeline works.

forge-site migrate --from wix --url https://old-site.wixsite.com/gallery
forge-site migrate --from squarespace --url https://old-site.squarespace.com
forge-site migrate --from wordpress --export wp-export.xml
      

> 6. Roadmap