developer · developer

Build a place that keeps its promise

A practical starting point for contributors.

Build a complete journey around a real task: entry, useful action, interruption, uncertain result, correction, and return. Identify which actions need authority and which remain available without an account.

This edition offers public reading and client-side temporary notes. It has no public API, credential service, payment workflow, human-help submission, or connected private workspace.

The developer readings describe components, audience boundaries, interruption, and evidence. Requirements for future consequential services are proposed contracts; their presence in documentation does not mean they are deployed.

Use the smallest implementation that can tell the truth about its outcome. A request accepted by the browser is a request, not proof that a file exists or a person received it.

Edition 2026-10-09.1