Why an /ai page?
We are living through a transformation in how software, text, and media are produced. Generative AI tools and large language models have become remarkably capable at generating text, churning out summaries, and assisting developers.
However, with that capability comes an influx of synthetic noise and automated spam across the web. To preserve trust, transparency is essential. I was inspired by Damola Morenikeji's original /ai manifesto and peers like Cassidy Williams who published an /ai page to openly articulate where and how artificial intelligence enters their work.
Here is my clear stance.
Content and writing
All ideas, perspectives, and opinions are 100% my own.
Italian is my mother tongue. When sharing technical concepts, architectural post-mortems, and engineering insights in English, I sometimes use AI tools as an editorial assistant. It helps me spot grammatical slips, smooth out phrasing, and ensure the text is easily understood by engineers around the world.
What I do not do:
- I do not use AI to generate articles from scratch or brainstorm opinions.
- I do not publish synthetic posts or filler tutorials generated by prompts.
- I do not outsource my critical thinking or engineering perspective.
Every tutorial, blog post on dev.to/kasuken, book chapter, or newsletter issue is rooted in real-world scenarios I have encountered throughout my 20+ years of working in tech.
Code, architecture, and engineering
I am a software engineer and a GitHub Technical Lead. Writing code is what I love doing, and that has not changed.
I actively use modern developer tools, including GitHub Copilot, for productivity — things like exploring new API surfaces, scaffolding boilerplate, or looking up repetitive patterns. But AI never acts on autopilot.
I write and review my code as I always have. Every line of code that goes into my open-source projects, SaaS applications, or educational demos is reviewed, tested, and maintained by me. If something breaks, I am responsible for diagnosing and fixing it. Engineering rigor, security, performance, and architecture remain human-driven responsibilities.
Community, newsletter, and media
I believe deeply in authentic community relationships. When you subscribe to my newsletter, read my updates, or interact with me on GitHub, LinkedIn, or Twitch:
- You are reading words written directly by me, not an automated ghostwriter.
- Any reply to an email or direct message comes straight from my desk.
- The screenshots, diagrams, and code snippets represent real systems, not synthetic mockups.
Your time and attention are valuable. If someone takes five minutes out of their day to read what I've published, it is my duty to ensure that it reflects genuine thought, real effort, and authentic human experience.
Machine-readable human authorship: human.json
In addition to publishing this human-readable manifesto, I also support the human.json protocol, as adopted by creators like Cobb and specified by Beto Dealmeida.
You can inspect my human.json file directly on this site, also discovered via <link rel="human-json" href="/human.json"> in the HTML header.
Why add a human.json file?
While an editorial manifesto speaks to humans who visit the page, human.json provides a lightweight, open, and machine-verifiable complement:
- Verifiable human assertion: It provides a machine-readable declaration of human authorship tied to URL ownership, without relying on corporate surveillance or third-party identity silos.
- Decentralized Web of Trust: Through mutual and directional vouches, real creators establish a crawlable trust graph. Readers can start from a seed site they trust and discover other genuine human creators through verified hops.
- Browser extension recognition: Verifier extensions (such as the Human.json Verifier for Firefox and Chrome) instantly detect the file and notify readers that they are browsing authentic, human-crafted work rather than synthetic content farms.
Join the /ai movement
If you produce content, code, or creative work on the web, consider publishing your own /ai page and declaring your human.json file.
It does not matter whether your policy is strictly zero-AI or deeply integrated into your workflow — what matters is honesty, attribution, and respecting your audience.
To read more about the philosophy and explore other creators' declarations: