Relay
Share the work.
Keep its source intact.
I wanted a place for technical work to travel without losing the source, its history or the rules around who can use it.
Relay brings an artifact reader, source view, sharing controls and agent access into one product experience.
Try the readerThe prototype, in 52 seconds.
Download filmThis film shows the product prototype. Sign-in, sharing and agent connection flows are simulated; they do not establish a live production service.
What I built around it.
I designed and built the interactive product prototype and the launch film. I also worked through the platform architecture: how people publish artifacts, how versions preserve source, how access is granted, and what an agent is allowed to do.
- Built
- Interactive product mockup, reader and source views, sharing and developer-access flows, responsive layouts and the launch film.
- Implementation underway
- Rendering and security packages, plus the isolated renderer. The repository includes backend work; the complete platform is not released.
- Designed
- Immutable versions, individual ownership, four access modes, separate human/CLI/automation credentials, and safe Markdown and HTML rendering boundaries.
Open an artifact.
A small, read-only example. Switch between the document, its source and history.
Keep the evidence with the answer.
Example artifact · Markdown · Version 3
Keep the evidence with the answer.
A useful technical note should preserve what was observed, where it came from, and which decision it supports.
- Keep the original source available.
- Record each version rather than overwriting it.
- Make access an explicit decision.
Illustrative content authored for this portfolio demo.
# Keep the evidence with the answer.
A useful technical note should preserve what was observed,
where it came from, and which decision it supports.
- Keep the original source available.
- Record each version rather than overwriting it.
- Make access an explicit decision.Source is displayed as text. This preview does not execute uploaded HTML.
- Version 3 · CurrentAdded explicit access rules.
- Version 2Added source and versioning notes.
- Version 1Created the artifact.
Illustrative history; these entries are browser fixtures, not stored records.
Who can read it?
Explore the four access modes in the product design. Ownership stays with the author.
Private
Only the owner can read this artifact. Creating an artifact starts here; publication is a separate choice.
- Ownership
- Stays with the author.
- Editing
- Only the owner creates new versions.
Changing this example only changes the explanation. It does not publish a document or grant access.
The engineering decisions.
Keep rendering separate from authority.
The design separates safe Markdown from arbitrary HTML. HTML belongs on a credential-free renderer origin with a sandbox and restrictive content policy. Source remains inspectable as escaped text.
Rendering and security packages are in the repository. This portfolio page illustrates the product; it does not reproduce the backend or accept uploads.
Give people and agents different access paths.
Human sessions, interactive CLI grants and automation tokens have different jobs and revocation paths. An agent should receive bounded access rather than inherit an owner's entire session.
The connection flow in the film is a prototype. Live credential issuance and a complete end-to-end platform are not claimed here.
Make a version a record.
The architecture preserves immutable versions and keeps source, rendered output and provenance tied together. Sharing grants viewing and commenting; it does not transfer ownership or grant editing rights.