Writing docs and blog posts
The manual explains current behavior; the architecture document states what must remain true. Before adding a command to an example, run that version in a disposable directory and check its exit status and observable result. Set both OBIT_HOME and OBIT_CONFIG_DIR for manual tests. Do not demonstrate against an everyday ledger, registry configuration or Recycle Bin.
A development post may explain why a change was made. Date it by the actual development event and link facts to public commits, issues, pull requests, release notes or versioned source paths. A build does not establish that a native desktop interaction works. Distinguish observations from intent and inference.
Publish without bylines. Omit internal records, local account names, private paths, addresses, credentials and chat transcripts. Pair each developer page with its translation. Check code blocks, links and language switching in both the regular and mirror builds.