Blog authoring notes
These notes apply to this repository unless a more-specific AGENTS.md overrides them.
AI collaboration disclosure
- Every post drafted or revised with AI assistance must include an “AI collaboration note” footer.
- The footer should clearly state the approximate contribution pattern for that post, for example:
- “Jeremy outlined this post and dictated a rough draft. GPT-5.5 then wrote a clean draft, which Jeremy edited before publication.”
- Adjust the note for each post so it accurately reflects the real workflow. Do not reuse boilerplate if the workflow changed.
- When useful and not distracting, include the author’s prompts or dictation context as footnotes, collapsible details, or hover-style annotations so readers can see how the AI collaboration happened.
- Keep the disclosure in plain language. It should be understandable to a non-technical reader.
R/Pharma developer diary series
- The first R/Pharma posts should read primarily as a developer diary: informal, exploratory, fun, and honest about what worked or did not work.
- Prefer concrete stories and artifacts over polished thought-leadership framing.
- Keep the recurring question visible: “What can we do with these tools right now?”
- Later posts can go deeper on current best practices for agentic engineering, validation, review, and GxP-ready workflows.