Editorial Policy
Last updated: April 25, 2026
Minbook is a solo-operated technical blog about building and operating AI products. This page documents how content is written, how it is verified, and how it is separated from advertising and sponsorships. The goal is to give readers what they need to judge our credibility for themselves.
1. Writing & verification principles
- Primary sources first — official documentation, IR filings, peer-reviewed papers, and source repositories are preferred over secondhand reports
- Verifiable claims — numbers, benchmarks, and pricing always cite the source as of the time of writing
- Runnable code — code samples are designed to run in real environments, with dependency versions noted
- Citation — external sources are linked inline or listed at the end of the post
- Review cycle — incorrect or outdated information is updated post-publication, and the "Last updated" date is bumped
2. AI disclosure
Minbook is a builder's notebook on AI products, and AI tools are part of our writing workflow as well. Here is how — and how not — we use them.
- What AI is used for — research aggregation, drafting structure, polishing prose, KO↔EN translation, code review
- What AI is not used for — fact verification, source vetting, primary thesis writing, data interpretation
- Tools used — Claude (Anthropic), ChatGPT (OpenAI), GitHub Copilot
- Human review — every post is read end-to-end by the operator (MJ) before publication; facts, logic, and numbers are checked manually
We never publish unedited AI output. All external links are verified by hand to prevent fabricated citations (hallucinations).
3. Advertising, sponsorship, affiliates
- Advertising — Google AdSense automatic ads only, clearly distinguished from editorial content
- Sponsored content — we do not publish posts paid for by sponsors
- Affiliate links — if used, they are explicitly labeled "contains affiliate links" in the post (currently not in use)
- Editorial independence — we do not change the angle or conclusions of a post at the request of advertisers, partners, or vendors
- Disclosure of interest — when covering products built by the operator (WICHI, MMU, BoltShark, etc.), the post discloses this at the top and bottom
4. Corrections & takedowns
- Typos & minor errors — fixed on discovery; the "Last updated" date is bumped
- Material factual errors — a "Correction" notice is added to the top of the affected post
- Reader correction requests — please email contact@minbook.dev with the post URL; reviewed within 2–3 business days
- Unpublish or removal — content may be unpublished if it causes clear harm to the author or a third party
5. Plagiarism & quotation
- We do not republish other publications' work verbatim
- Quotations are limited to what's necessary, with sources cited
- Images and diagrams are either original or used under clear license
- Readers may quote or summarize with attribution; full republishing requires prior consent (see Contact)
6. Categories
- Deep Dive — technical and market analysis grounded in primary sources
- Build — engineering notes from products we have actually shipped
- Lab — experiments with new tools, libraries, and techniques