Editorial Policy
This site publishes technical write-ups about infrastructure, networking, security and tooling. This page explains how they are produced, because the process matters more than the disclaimer.
How an article is made
Topics come from primary sources: project repositories, release notes, RFCs, vendor documentation and public incident reports. A draft is assembled by an AI research assistant, then checked against the sources and validated mechanically before publication.
The publishing pipeline refuses an article when it fails any of these gates: a duplicated topic, a title that overflows the search result, fewer than two contextual internal links, a dead cited URL, unclosed editor blocks, or leaked private project names. The rules are code, not good intentions.
What is not published
No client work, no internal infrastructure, no embargoed incidents. Claims that cannot be traced to a public source are cut rather than softened.
Corrections
If something here is wrong, say so through the contact page. Substantive corrections are applied to the article itself and dated in the changelog entry for that post; the article is not quietly rewritten.
Authorship
Articles on this site are published under Morteza Bahmani’s name. Drafts are produced with an AI research assistant, then checked against primary sources and put through the publication gates described above. Morteza runs the site, sets the editorial direction and is accountable for what appears here.