Menu
DOCUMENTATION
Documentation
Ooloi's architectural documentation is publicly available in the Ooloi-docs GitHub repository. It was published ahead of the source code because the documentation defines what the source code must do.
Architectural Decision Records
The ADRs are the primary technical documents. They are not aspirational descriptions or design proposals. They are binding specifications: each ADR defines invariants, constraints, and behaviours that the implementation must satisfy exactly. When an ADR and the code disagree, the code is wrong.
The collection covers the full architecture, from foundational decisions (immutability, STM, rational arithmetic) through domain-specific systems (pitch representation, time signatures, key signatures, remembered alterations) to infrastructure (gRPC transport, rendering pipeline, collaborative sessions, deployment).
Guides
The guides document how to work with core systems: timewalking, the polymorphic API, concurrency patterns, component testing. They are practical rather than explanatory — written for someone implementing against the architecture, not evaluating it from outside.
Welcome
A personal introduction to the project, its origins, and its intentions.
Architectural Decision Records
The ADRs are the primary technical documents. They are not aspirational descriptions or design proposals. They are binding specifications: each ADR defines invariants, constraints, and behaviours that the implementation must satisfy exactly. When an ADR and the code disagree, the code is wrong.
The collection covers the full architecture, from foundational decisions (immutability, STM, rational arithmetic) through domain-specific systems (pitch representation, time signatures, key signatures, remembered alterations) to infrastructure (gRPC transport, rendering pipeline, collaborative sessions, deployment).
Guides
The guides document how to work with core systems: timewalking, the polymorphic API, concurrency patterns, component testing. They are practical rather than explanatory — written for someone implementing against the architecture, not evaluating it from outside.
Welcome
A personal introduction to the project, its origins, and its intentions.
Ask the Librarian
Ask anything about Ooloi's architecture, design decisions, or how things work. The Librarian draws on the ADRs, guides, and documentation — not on general AI knowledge. If the answer isn't in the docs, it will say so.
|
|
Ooloi is an open-source desktop music notation system for musicians who need stable, precise engraving and the freedom to notate complex music without workarounds. Scores and parts are handled consistently, remain responsive at scale, and support collaborative work without semantic compromise. They are not tied to proprietary formats or licensing.
Ooloi is currently under development. No release date has been announced.
|