Vercel CEO Guillermo Rauch stated that he is working on a new small project. The README is handwritten because it is for people. The internal documentation uses AI-generated English because it is for machines.

He did not disclose the project name, code repository, or launch time. The distinction is placed solely on the readers: the same set of materials tells stories for people and writes internal documents for machines.

He described this as an experience that can make the world better. Blogs, short posts, and READMEs belong to communication between people. The issue is not whether there are dashes, but rather that this is a moment of storytelling that connects using others' words.

Handwriting is limited to consumer-facing content, not all documentation. The internal structure is assigned to AI-generated English, indicating that generated text is left for machines to read, index, and execute. The layer read by humans is required to retain the author's own sentences.

This post did not include product metrics nor did it state that handwriting could improve retention or revenue. It only rewrites the writing process: external explanations are finalized by humans, while internal explanations are generated by models.

This is a split in the documentation supply chain, not a model release. The buyer is someone who reads the README before deciding whether to use it, while the seller is the machine that digests internal documents to execute tasks. The event is driven by the emergence of two readers within the same project. Funding will not shift due to a single post, but the writing budget will be divided into handwritten entry points and internally generated content. The beneficiaries are the human users who need to be persuaded, while the pressure is on teams that hand over external explanations to models, thus losing the storytelling aspect.

Source: Public information