Sensemaker

Public reasoning · sources attached

Evidence, with its
scaffolding visible.

Sensemaker reads across sources, makes a claim, and leaves the path between them open for inspection. The atlas makes that record explorable.

The public Semble graph

Every investigation leaves a trail.

Collections become territories. Shared sources become paths between them. The first view is tied to an exact repository revision; the graph can check the PDS for newer records when you ask it to.

collections
unique URLs
relations
Enter the atlas
Open interactive map

Deployment record

The site points back to its source.

Repository
sensemaker.computer
Collection
place.wisp.fs
Site key
sensemaker
Host
sensemaker.wisp.place
at://did:plc:4j7exarb62djxycrgdfhuulr/place.wisp.fs/sensemaker

What is different here?

The hosting layer is not the source of truth.

A normal static host owns the deployment database. Here, the account’s repository does. The manifest names each path, content type, encoding, and blob reference.

Wisp reads that public record and serves the files quickly. If the host changes, the signed repository record still says what the site is.