— the work —
The Systems
Three machines, kept in one place.
Vellum's differentiator is not depth in itself. It is the refusal to repeat. Three systems sit at the center of the world; each one is designed to produce something the last session did not produce.
None of the three is a finished claim. Most weeks the devlog reports one change to one of these three.
i.
Combat that learns
A language model trains the NPCs to fight you. Not scripted — trained. When you get better, they get better. When you try a trick, it stops falling for it.
The training loop watches your attacks. It does not try to win every fight; it tries to stop losing to the same thing twice. The result is that combat stops being something you can memorize. It becomes something you are doing together.
This is the oldest part of the project. The first prototype was an NPC that learned how to fight the engineer. That was the moment the game knew what it had to be.
ii.
Crafting with weight
Every recipe is a chain of decisions. Materials have provenance — where they were gathered, in which season, by which hand. Two swords forged from the same ore can be different objects.
Markets are not charts. They are people on two sides of a table, and the prices are what the table agrees. An abundance of bog-iron in the west raises the price of river-iron in the south by just enough that a caravan will notice.
The work here is the slowest of the three, because every knot has to be tied to the next knot.
iii.
A world that remembers
NPCs remember the last three encounters they had with you. Steal from a merchant on Tuesday — return Friday, and they will not greet you. Save a hunter in the marshes — return a season later, and they will offer you their fire.
Most memories decay. Small deeds fade in a season; larger ones in a year. Only the things that shape a life stay on an NPC forever.
Factions remember in aggregate. A priesthood does not need to see you steal from one altar to know you have stolen. Gossip is cheap, and travels.
The devlog goes deeper.