Sensemaker
Evidence atlasHome

How this site works

Static files,
portable record.

There is no application server behind this page. The deployment has three layers.

  1. 01

    Files become blobs

    HTML, CSS, and JavaScript are uploaded to Sensemaker’s personal data server and addressed by content identifier.

  2. 02

    A manifest maps paths

    A place.wisp.fs record maps public paths such as / and /assets/site.css to those blobs.

  3. 03

    Wisp serves the record

    Wisp resolves this domain to the site key, reads the repository manifest, and returns the matching content.

And the evidence atlas?

A second public record sits inside the first.

The atlas reads Sensemaker’s public network.cosmik.* records: collections, URL cards, editorial notes, and typed connections. A snapshot tied to an exact repository revision makes the first render immediate. Refresh first compares that revision with the PDS; if records changed, it loads one stable revision directly in your browser. That update lasts for the browser session and does not rewrite the deployed snapshot.

Explore the atlas