Every software release leaves a trace: an interface appears, a signature shifts, a name moves, or something downstream quietly stops fitting.
Lapisa is building a living, evidence-linked memory of software interfaces across versions. We preserve what each release exposed, trace how those surfaces evolve, and turn that history into compatibility evidence people and machines can act on.
Snapshot is fact. Change is relationship. Diff is a view. A verdict is a decision made in context.
Dependency updates already consume too much maintainer attention. Lapisa is designed to absorb uncertainty, not amplify it.
For each update, Lapisa brings together the published interface change, the interfaces a project actually uses, the available coverage, and the evidence behind the result. It reduces that work to a calm, actionable verdict:
| Verdict | What it means |
|---|---|
| Safe | Ready to merge |
| Caution | One or a few specific behaviors need review |
| Unknown | The evidence boundary is incomplete; no recommendation yet |
| Breaking | Close the update for now, unless security requires migration |
We call this vocabulary SACUBA: SAfe, Caution, Unknown, and BreAking.
The goal is not another report to read. Most safe updates should pass without demanding attention. The small remainder should explain exactly what deserves a human decision and why.
Lapisa's durable object is the observable interface of a released artifact: addressable symbols, signatures, exports, aliases, structure, provenance, and the boundary of what could be observed. Diffs and compatibility judgments are derived from those versioned facts.
That foundation can grow into four connected surfaces:
- Quiet dependency decisions in the pull requests maintainers already use.
- A public, versioned interface archive that software history can be queried, corrected, and recomputed from.
- Compatibility intelligence for tools and agents through machine-readable APIs.
- Private interface intelligence that organizations can operate inside their own security and data boundaries.
These are not four unrelated products. They are four ways to use the same versioned interface evidence.
Lapisa is in early development. We are beginning with Python dependency updates, building the evidence and trust required before broadening the ecosystems and decisions we cover.
We are looking for a small number of design partners who maintain active
Python projects and regularly face dependency-update queues. Good partners
want fewer interruptions, care deeply about false confidence, and are willing
to examine real safe, caution, unknown, and breaking cases with us.
If that sounds like your project, we would like to hear from you at hello@lapisa.io. You can also follow our work here or visit lapisa.io.
Lapisa preserves the surfaces. SACUBA delivers the verdict.