Overview
A framework for continuous, coherent software delivery, built to preserve the context, capability, and intent that connect decisions to outcomes.
Context degrades across handoffs. As work moves from conversation to document to ticket to review and back again, the reasoning behind decisions is lost. Harmonic Composition addresses this directly, by making context, capability, and intent explicit, and by keeping them connected throughout delivery.
How the framework is organized
Harmonic Composition rests on key concepts, organized across three phases, and governed by six quality dimensions. Each section below is a full entry point into the documentation.
Key Concepts
Notes, Beats, Revisions, and Coda — the primitive concepts that give every part of the system an explicit name and role.
Explore the elements →Phases
Explore, Compose, and Execute — the phases that organize how delivery progresses from context-setting to capability-building to incremental advancement.
Understand the phases →Quality Gates
Six dimensions every Beat must satisfy before the system can progress — Distinctive, Harmonious, Substantial, Durable, Clear, and Strategically Aligned.
Review the dimensions →Getting started
A practical pathway for applying Harmonic Composition to a new system or phase of work.
- Capture initial Notes
Record the assumptions, constraints, guidance, and decisions you already know. Notes at this stage document the context that will shape everything downstream: what the team knows about the problem space, what boundaries must be respected, and what is being taken as given.
Initial Notes are not expected to be complete — understanding deepens as work progresses. The goal is to capture what is known now in a form that remains useful when the context has changed or when new people join the work.
- Define the Coda
Articulate the specific, resolved end-state the system is converging toward for this phase. The Coda should describe a concrete outcome — what the system will be able to do, or what condition it will be in, when this phase is complete. Favor observable, testable descriptions over aspirational language.
A clear Coda is the prerequisite for everything that follows. If multiple stakeholders are involved, surface any disagreement at this step — misaligned Codas are far more costly to resolve in Execute than in Explore.
- Identify the Beats
Define the durable capabilities the system must possess to reach the Coda. Each Beat should describe an outcome-oriented capability, not a task, deliverable, or feature. Ask: what must the system be able to do, and for how long will that need persist?
Aim for a set of Beats that collectively covers what the Coda requires, without significant overlap. Completeness matters more than precision at this stage — the Compose phase exists to sharpen each Beat before delivery begins.
- Apply the quality gates
Evaluate each Beat against the six quality dimensions: Distinctive, Harmonious, Substantial, Durable, Clear, and Strategically Aligned. Beats that do not satisfy all six are refined, split, merged, rewritten, or removed until the full set is ready.
Also evaluate the Beats as a system: do they collectively support the Coda? Are there capabilities the Coda requires that no Beat yet describes? Resolving these gaps is the purpose of the Compose phase.
- Plan Beat Versions and execute Revisions
Once Beats are quality-gated, each one is advanced through Beat Versions — planned increments that carry the description, scope, and acceptance criteria for a slice of the Beat's capability. Each Beat Version is then delivered through one or more Revisions, which are the PR-level execution units.
This is the Execute phase: Revisions ship incrementally, the system moves toward the Coda Beat by Beat, and Notes continue to accumulate as decisions are made along the way.
The time invested in steps 1–4 is not overhead — it is the work that makes step 5 coherent. Teams that skip Explore and Compose typically rebuild the same context later, at higher cost, under more pressure.