Thank you for subscribing.

Ooloi is unusual in that the early work has gone into the invisible foundations: the abstractions of music itself, and the architecture that lets those abstractions behave correctly at scale.

So far we’ve built the core structures – scores, notes, articulations, slurs – and then shifted to what looks like “plumbing”: the server/client system, transactions, and real-time event streaming. That isn’t a detour; it’s the condition for everything that follows.

Why this matters musically
Ooloi is collaborative at its core. Not as a bolt-on, but as the default. Even when you work alone, you are – from Ooloi’s perspective – a collaboration network of exactly one. The same machinery that lets two or twenty musicians work together is what ensures a single flautist can edit smoothly — no lag, no freezes — even on very large scores.

What’s next
With the foundations stable, the next steps are explicitly musical: engraving-quality layout, performance-level MIDI, and deeper semantics that make notation more than symbols on a page.

Cadence
Expect updates once or twice a week during active phases, slower during periods of architectural deep work. Each issue will say what’s been built, what broke, and why decisions were made.

I’ll probably write a blog post expanding this “collaboration of one” idea — it’s an interesting shift in how I think notation software should be built now.

For background, the announcement is here: Announcing the Ooloi Newsletter.

— Peter Bengtson
ooloi.org