Skip to content
Build in public

PortLev Labs

Build notes from Portfolio Leverage Co. Each note is the stack, the prompts and the decisions behind a system that shipped, documented the day it shipped.

Most companies write retrospectives months after the work shipped, when the detail is gone and the lessons have softened. PortLev Labs is the opposite: a build note captured the day the work shipped, while the decisions are still fresh.

Yuri writes the first record and signs off on every note before it publishes.

Every build note on this page is the record of what got built, why, how, and what an operator would need to replicate it. The "Reproducibility" section is the most important: if you cannot rebuild the thing from the note, the note failed its own audit.

Catalogue arrow_forward

Build Notes

Every shipped feature, integration and infra change, dated and source-cited. Newest first.

How the build notes get written

  1. A build ships. A feature, a deploy, a content drop, a new system.
  2. The record is captured. An exhaustive chronicle, every claim traced to a decision log or artifact.
  3. The note is structured. Seven sections: Why, What, How, Learned, Next, Reproducibility, Sources.
  4. The note is reviewed. Brand discipline, voice, accuracy checked before it goes out.
  5. The note publishes. Privacy redaction applied, rendered, indexed here.

Yuri reviews every note for accuracy before it publishes.

Why this exists

Portfolio Leverage Co. ships fast. The notes are the proof, not the marketing. If you want to see what actually gets shipped in a week, this is the page.

If you want to reproduce any specific build, the record is here. If you want the marketing-version of the same builds, subscribe to Leverage Brief.