Reference

Glossary

Concise definitions of the key terms used across Harmonic Methods. Each entry links to the full documentation for that concept.

• AI-Native Software DeliveryAn approach to building software where AI coding agents perform most execution against an explicit, structured representation of intent, while people own the destination, tradeoffs, and review. Harmonic Methods is the delivery method built for it. Learn more →
• Harmonic CompositionA framework for continuous, coherent software delivery, built to preserve context, capability, and intent across handoffs. One of three frameworks under Harmonic Methods. Learn more →
• Harmonic MethodsThe umbrella brand for three connected frameworks: Harmonic Composition, Harmonic Orchestration, and Harmonic Portfolio Management. Return to the hub →
• Harmonic OrchestrationA framework for coordinating human and AI agents to execute against shared context across systems and teams.
• Harmonic Portfolio ManagementA framework for mapping and arranging capabilities across the wider landscape, managing a portfolio of systems and initiatives in alignment with strategic intent.

Harmonic Composition

• Beat VersionThe planning increment of a Beat — a planned slice of its capability, carrying the description, scope, and acceptance criteria for a unit of planned work. A Beat Version is delivered through one or more Revisions. Learn more about Beats →
• BeatsDurable, outcome-oriented capabilities the system must possess. Beats persist as long as the capability is relevant and evolve through Revisions rather than being closed and discarded. Learn more about Beats →
• ClearOne of the six quality dimensions. A Beat is Clear when its intent and scope are unambiguous and can be understood by anyone working in the system without additional explanation. See all quality dimensions →
• CodaThe specific, resolved end-state the system converges toward. The Coda defines what done looks like for the current phase of delivery and shapes which Beats are relevant. Learn more about Coda →
• DistinctiveOne of the six quality dimensions. A Beat is Distinctive when it represents a capability that stands apart from others in the system without unnecessary overlap. See all quality dimensions →
• DurableOne of the six quality dimensions. A Beat is Durable when it is expected to remain relevant throughout the current phase and beyond, not rendered obsolete by its first Revision. See all quality dimensions →
• HarmoniousOne of the six quality dimensions. A Beat is Harmonious when it integrates cleanly with the other Beats and supports, rather than conflicts with, the overall Coda. See all quality dimensions →
• NotesExplicit, versioned, discoverable context that preserves the reasoning behind the work. Every Note has a type: Context, Constraint, Guidance, Decision, or Document. Learn more →
• Quality GatesThe six dimensions — Distinctive, Harmonious, Substantial, Durable, Clear, and Strategically Aligned — that every Beat must satisfy before it can transition to composed and Revisions begin. Learn more →
• RevisionsShippable increments that evolve a Beat while preserving continuity. Each Revision advances a capability without pivoting or discarding what has already been established. Learn more →
• Strategically AlignedOne of the six quality dimensions. A Beat is Strategically Aligned when it advances the system toward the Coda and reflects the priorities of the current phase. See all quality dimensions →
• SubstantialOne of the six quality dimensions. A Beat is Substantial when it addresses a capability of genuine, lasting significance rather than a thin or incidental concern. See all quality dimensions →

See the FAQ for common questions →