Public diary and content publication policy
The manual owner-review gate for this repository, with explicit exclusions for private material.
Public diary and content publication policy
This repository contains a manually curated public subset. There is no automatic export from private diaries, chat history, task logs or a private knowledge base. The diary category is reserved for intentionally public lab notes or an independently approved public reflection.
Before an entry is published
- Prepare a separate public draft using synthetic examples and public sources.
- Check factual claims, dates, links and reproducible examples.
- Obtain explicit owner review of the final draft before the parent publication workflow releases it.
- Run content-loading and build checks, then inspect the reading page.
- Publish only the reviewed public file. Keep approval evidence outside the article body when it contains private context.
Material that stays out
Private diaries, raw conversation transcripts, private prompts, credentials, access tokens, customer records, private identifiers and confidential screenshots must not be copied here. Replacing a name with an initial does not establish that a story is safe to disclose. If a source cannot be reviewed for public use, leave it out.
Honest authorship
Do not invent personal experience, a customer case study or a measured outcome. Label proposals as proposals and worked examples as examples. Public technical references support claims; they do not grant permission to disclose private facts.
When revising an approved entry, review the changed content again. Local preparation and tests are not approval for production publication. This policy governs editorial release; it does not claim to be legal advice or an automated privacy audit.