"Public sharing is an explicit projection of the original, never a dump of the entry."
How the well grows
Sharing is the moment private practice may become public speech. The safest default is narrow: an author explicitly selects an entry, reviews the original, and shares that original. Translations, notes, prompts, and photos do not hitchhike.
Attach it with a narrow contract
Prefill a narrow share sheet from entry.original_text. Its explicit form fields are body, emotion, visibility, and include_media; the entry id stays in the route. Never serialize the entire entry object and subtract fields afterward.
When extension steals sovereignty
A generic share function can accidentally choose the currently visible translation. Object spreading can leak review notes or asset references added by a future schema. Allowlisting makes new private fields stay private by default.
Retest the first promise
Even after “Share Only the Original” arrives, the original returns first, the author keeps the pen, and late work asks permission. Trace whether sharing, scheduling, search, or audio invents copied originals, hidden clocks, or broad payloads for convenience. An extension that bypasses old invariants has changed the product rather than grown it.
Run the whole path
Compare the explicit share form with object spreading after the entry schema gains review notes and image paths. Add duplicate delivery, source editing, deletion, stale artifacts, and permission denial. Prove that database rows, outbound payloads, and sibling references tell the same story instead of trusting one successful screen.
What it means to close the well
Closing does not mean stopping features. It means one practice is complete from original draw through paper, recovery, rediscovery, and deliberate sharing. When technology appears only to explain itself and otherwise recedes behind the ink, the well has grown useful hands.
The extension's actual contract
The sheet begins with entry.original_text, never a translation. Only body, emotion, visibility, include_media, and explicitly selected files cross the route; a successful share appends a publication row without mutating the entry.
New private fields therefore remain private unless a later contract deliberately adds them.