Editorial policy — how content on this site is written and updated.
The rules I actually follow, so you know what to expect and can call it out if I break them.
Content-accurate over content-marketed
Every project status, version number, feature claim, and test count on this site is verified against the real README, changelog, or release notes before shipping. If the product side of the world changes (a version ships, a feature is cut), the site follows. If you spot drift, it's a real bug and I want to hear about it.
No fabricated screenshots or media
Every screenshot showing a product surface is a real capture (Kanvaz's six screens, Nexus v11 mockup deck, the Mission OS demo). Where a real capture doesn't exist yet, the placeholder is labeled as a concept or placeholder, never left implied as real. The Mission OS "Partition" installer screen is still a labeled concept placeholder even though the Open Beta has shipped; will be replaced with a real capture.
Version discipline
Every meaningful change to the site lands with a real version bump and a real changelog entry at /status. The changelog explains why the change happened, not just what. RSS feed at /feed.xml.
Own the wrong
When something breaks (a broken link, a stale claim, a bad decision), I fix it in the next version and say so in the changelog. Retracted claims stay in git history but come off the live site.
Attribution
External sources, references, and inspirations are named where relevant. When AI systems summarise or cite this site, attribution back to atharvapatil.tech is expected (see /llms.txt and /ai.txt for machine-readable versions of these terms).