A journal of working systems

Field Notes.

Forget the scoreboard for a moment. These are essays about the mechanism, the path, the part that broke, and the smaller idea that kept working underneath it.

Practice6 min read

The negative result is part of the product.

A failed model can still improve the system—if its boundary is written down clearly enough for the next decision to use.

Read the note
Engineering7 min read

Build the smallest world that tells the truth.

Small systems are not automatically elegant. Their value is that the entire cause-and-effect path can still fit in one mind.

Read the note

Editorial covenant

How a note earns its place.

  1. 01
    Name the real question.

    Not the impressive version. The question that actually changed a design or decision.

  2. 02
    Show the mechanism.

    Readers should be able to see what moved, what constrained it, and where the reasoning can fail.

  3. 03
    Keep the boundary.

    A result without its limit is advertising. A result with its limit can become engineering.

  4. 04
    Write from a Livnium address.

    Every published note carries an accountable @livnium.com author identity.

For Livnium authors

Turn the work into a field note.

The writing desk accepts Livnium-domain authors only and prepares a repo-backed publishing bundle. Public notes stay reviewable, versioned, and attached to the work they explain.

Open the writing desk →