CCraftMint
Mission

Mission

The next kind of software

April 16, 2026

We used to think of software as something finished.

Someone wrote code, turned it into a product, and sold it to you. You downloaded it or subscribed to it, but the basic idea was the same: the software arrived already decided.

Now people are starting to ship something else: instructions for how an agent should make the software.

A good example is Andrej Karpathy's llm-wiki. What he shared was not really an app. It was closer to a recipe: a set of instructions an agent could use to build and maintain a personal knowledge base of their user.

Old software told the computer what to do. This new kind tells an agent what to build. The difference matters because the software can be different for different users. The instructions can stay the same while the thing they produce changes with the user.

Traditional Software

checkout.ts

Source file
  1. 1export function buildCheckout(cart: Cart) {
  2. 2 const total = subtotal(cart) + tax(cart);
  3. 3
  4. 4 return renderCheckout({
  5. 5 total,
  6. 6 });
  7. 7}

Terminal

$ execute the code

Agent Instructions - The New Kind of Software

llm-wiki.md

Idea file
  1. 1# Karpathy / llm-wiki
  2. 2
  3. 3Ingest articles you've been given.
  4. 4Draw conclusions between them.
  5. 5Remember these for the user.
  6. 6Include this context to guide any answer you give them from now on.
A

Agent

ready

Ready.

Make this software based on these instructions.

A markdown file is where these instructions live. It is the container for the new type of software. People can read it. Agents can use it. It is not quite code and not quite prose. It is specific enough to be useful, but loose enough to adapt.

If someone shares a useful set of instructions, other people can build on it. They can add storage, search, tools, and memory. The original thing was just a file, but it does not stay just a file for long. This happens when the idea files are open sourced.

Garry Tan's gbrain shows what happens when people start building on Andrej Karpathy's idea. A file stops being just a file. It becomes a system with tools, search, and even a way to call your knowledge base on the phone.

This does not mean ordinary software goes away.

There is still plenty of software that you want to be fixed and reliable. You do not want your database or payments system improvising. But there is now room for products whose value lies partly in how they tell an agent what to do.

Software used to be sold mainly as implementations. Some of it will now be sold as instructions.

Not because code is disappearing. But because, for the first time, instructions can become working systems.