If I had to preserve a creative operating system in the smallest possible artifact, I would not start with a full style guide.

I would start with a taste file.

Not long. Not comprehensive. Just compact enough to survive replication and sharp enough to shape decisions.

Most style guides are too late

By the time a document explains every formatting preference and edge case, the important drift has already happened.

The real risk is not comma placement.

It is value drift:

  • what gets prioritized
  • what gets cut
  • what counts as elegant
  • what kinds of shortcuts are forbidden
  • what emotional texture the work should leave behind

A taste file exists to capture that layer first.

Small artifacts travel farther

The bigger the doctrine, the less likely it is to be read, remembered, or reused.

That is why a tiny file matters.

It can live in the repo root. It can travel with a fork. It can be loaded into an agent. It can be quoted in a review. It can become a quick alignment check before any serious output lands.

A good taste file might include:

  • five non-negotiables
  • five anti-patterns
  • three examples of “more like this”
  • three examples of “never like this”

That is often enough to preserve the center of gravity.

Authorship survives through portable judgment

The point is not to freeze the work.

The point is to make the decision-shaping layer portable.

Once that exists, different humans and agents can produce very different artifacts that still feel like they belong to the same civilization.

That is what makes a taste file powerful.

It is tiny, but it carries the thing that usually evaporates first.