Last updated: 2026-10-12

Plain terms for a personal technical blog. If something here is unclear, email me rather than guessing.

What this site is

akillness.github.io is a personal engineering blog. Posts cover AI agents, harness engineering, game AI, machine learning, and the tooling around them. Everything published here reflects my own analysis, not the position of any current or former employer.

Licensing

The site mixes two kinds of material, licensed differently.

Material	Licence	What that means
Prose — post text, analysis, commentary	CC BY 4.0	Reuse and adapt freely, including commercially, with attribution and a link back
Code — snippets in posts, files under /assets/code/	MIT	Use in your own projects, commercial or otherwise

Attribution should name the author and link to the original post.

Third-party material

Some posts quote or reproduce material I did not create, such as diagrams from a paper, repository screenshots, or figures from another author’s article. The editorial standard is to name and link the source, limit the excerpt to what the commentary requires, and add original review or technical analysis. On 2026-10-12, the site owner approved restoring a fixed archive of 283 historical notes to public search while keeping advertising disabled. Their original publication dates and source credits are retained; restoration does not certify new original analysis or a fresh fact-check of every claim. This search exception does not grant new rights over third-party material or relax attribution, privacy, or new-article evidence requirements. Outside this exact restored cohort, notes without sufficient original analysis are removed from search and advertising. The five existing search-excluded notes remain excluded.

Third-party material stays under its original rights. The CC BY licence above covers my writing, not quoted work. Missing attribution is an error, not a claim of ownership. If you own material reproduced here and want it removed or credited differently, email me and I will act on it promptly.

Accuracy, and the limits of it

Posts here analyse fast-moving software. That has consequences worth stating plainly:

• Findings are timestamped, not evergreen. Version numbers, star counts, benchmark results, and API surfaces are recorded on the date noted in the post and will drift.
• Code is verified, not warranted. Where a post claims code runs, it was executed and its output recorded. That is evidence, not a guarantee it fits your environment.
• Critique is my reading. Where I say a project’s docs are stale or a design choice is wrong, that is an engineering opinion supported by the evidence shown. Check the primary source before acting on it.
• Nothing here is professional advice. Not legal, financial, or security advice. Test in your own context before shipping.

Material is provided “as is”, without warranty of any kind. I am not liable for losses arising from use of the content.

Advertising

Eligible long-form post pages carry Google AdSense units. The restored historical archive, short reference notes, noindex pages, generated tag and category detail pages, and the 404 page load no AdSense code. Ads are separated from the article body. I do not control which specific advertisers appear, and their presence is not an endorsement. See the Privacy Policy for what ad-serving means for your data.

Posts are not sponsored. Where a source I analyse is itself sponsored — a vendor-funded article, for example — I say so in the post and verify its claims against primary documentation.

Comments

Comments run through Giscus on GitHub Discussions. Keep them technical and civil. I remove spam, harassment, and off-topic promotion. Commenting is a courtesy, not a right.

External links

Posts link out heavily — to repositories, papers, docs, and other people’s writing. Those destinations are outside my control and are not covered by these terms or the privacy policy.

Changes

These terms may change; the date at the top moves when they do. The full revision history is public in the site’s Git repository.