The link format

A tensr share link is an ordinary https URL whose payload rides in the fragment — the part after #. The URL is just the vehicle; the fragment is the data.

https://app.tensr.fitness/share#share=H4sIAAAA…

Why the fragment

One load-bearing reason: browsers never transmit the fragment to a server. A tensr link pasted into a chat, an email, a text — the payload stays on the devices at each end. The link carries a session, a routine, a card; no tensr server sees the contents. It's POSSE at the link level: the data travels as a copy you hold, not a lookup against a database someone else owns.

Reading a link (for agents & tools)

Because the data is in the fragment, reading a shared link is a decode, not a fetch. Take everything after #kind=, and for the data-bearing kinds:

1. Split the payload on . — a link may carry several dot-separated blobs.
2. base64url-decode each blob.
3. gunzip it (the blobs are gzip-compressed).
4. Parse the result as the artifact JSON (a session's stats, a routine, etc.).

Nothing to fetch, nothing to authenticate — the link is self-contained. An agent handed a #share= link can read the session straight out of the URL.

Link kinds

Safety property

A link in a chat must never mutate a database. Data-bearing links stage inert and wait for consent; the only thing that auto-runs is a read-only query. The fragment can move your data around, never act on someone else's behind their back.