Editorial policy

What this site publishes

Practices explain how people plan, build, review, and ship software with coding agents. Model notes cover changes that matter to coding, tool use, testing, or cost, not every announcement. Tool notes say what something is for and what it does not do.

How to read a piece

A brief is a short account of something reported elsewhere. It names at least one source. A brief is never marked as tested. A guide is a lasting explanation. A field note records one real task and includes the date, version, and environment.

Reported means the claim belongs to the source. Analyzed means AINativ read the sources and wrote a conclusion without running the tool. Tested means AINativ ran it, and the test record says how.

Vendor statements stay attributed to the vendor. They are not rewritten as results from this site.

Drafts and translations

AI tools may help prepare a draft. A person reviews every draft and is the only one who can publish. An AI-assisted draft starts as needing changes.

Simplified Chinese and Traditional Chinese are separate editions. A converted draft is not ready to publish. The same rule applies to every language. This site does not publish an English page under another language’s address.

When a published piece changes section or slug, the previous address is kept and sent to the new one on the next build. An unpublished draft has no public address to preserve.

Sponsored pieces would be labeled. None are part of the default setup. The updated time on a page is the time the published version last changed.