developer · developer

Public pages and private material

A public build needs a small, deliberate content boundary.

A public reading build should include only the pages, reviewed copy, styles, scripts, and decorative assets needed for that release. Original research, reports, drafts, permissions, and internal source metadata belong outside it.

Search should receive only the approved public projection. Enforce publication and audience conditions before content reaches the browser; a result filter cannot protect private text already shipped in a script.

Temporary notes must stay outside the search dataset, analytics payloads, logs, and public render. This edition has no note-submission service; the chosen download creates a file through the browser.

Before adding a consequential service, require current purpose, actor, resource, version, and scope at its server or worker boundary. Recheck permission when a queued action executes. These are requirements for a future implementation, not a claim that such a service exists here.

Edition 2026-10-09.1