Editorial Guidelines
How we research, test, and publish on CogitoDaily, and what we do when we get something wrong.
1. Who is behind CogitoDaily
CogitoDaily is written and edited by Alfian Majid, a solo developer based in Indonesia. He is the only author credited on this site, and every article carries his byline. You can reach him directly at [email protected] about any article.
2. Sourcing
News coverage starts from primary material: official blog posts, release notes, documentation, model cards, and published benchmarks. Secondary reporting is used only to add context, and claims that trace back to a single unverified post are labeled as such or left out.
3. Testing and reviews
Reviews are based on actual use of the tool or API. Where a claim in an article comes from a hands-on test, the article states the setup used (plan tier, model version, date tested). Pricing and feature claims are re-checked before publication because they change constantly.
4. Versions and freshness
AI tooling ages quickly. Every draft is checked against current model versions before it goes out, and outdated version references are rejected rather than published. Evergreen guides are re-checked on a rolling schedule.
5. Corrections
If something we published is wrong, we fix the article rather than delete it, and update the publication date. Send the article URL and the specific claim to [email protected] and we will respond.
6. Independence
Rankings and verdicts are not sold. We do not accept payment for placement in a review, a tool list, or a recommendation. When an article contains affiliate links, they are marked in the article itself.
7. No fabricated proof
We do not invent benchmarks, testimonials, user counts, or quotes. If a number cannot be traced to a source we name, it does not go in the article.
8. Use of AI in our workflow
We work on AI topics, so it would be strange to ignore AI tools in our own workflow. AI assistance is used for research assistance and drafting. The constraint is that nothing publishes on trust alone: factual claims, pricing, version numbers, and links are checked against sources before an article goes live, and duplicate or outdated drafts are rejected by our publishing pipeline rather than shipped. The opinions, verdicts, and recommendations in each article are the author's.
We do not use AI to generate fake reviews, fake user quotes, or performance numbers we did not observe.
9. Not financial, legal, or professional advice
Our career, salary, and tool-buying articles are editorial analysis based on public information at the time of writing. They are not professional advice, and salary or pricing figures move faster than we can update every page.
10. Feedback and corrections
Found a wrong price, a dead link, a retired model version, or a claim that does not hold up? Send the article URL and the specific line to [email protected]. Corrections are applied to the article itself rather than quietly ignored.