Frequently Asked Questions

Questions about Harmonic Methods, how its frameworks work, and how their concepts apply in practice.

• How is this different from existing delivery approaches?

  Traditional and iterative delivery approaches tend to center on delivery cadence and task management, organizing work into time-boxed cycles, tracking completion of items, and measuring velocity through those items.

  Harmonic Composition centers on different concerns: system coherence, capability evolution, and preserving context across handoffs. The primary unit is not a task to be closed but a capability to be developed. The primary measure of progress is not throughput but alignment — between what the system can do, what it is becoming, and where it is headed.

  These are complementary concerns. Harmonic Composition does not prescribe how a team should organize its time or meetings. It addresses what gets lost between those events: the reasoning, the capability definitions, and the destination.

• How does this help with AI agents?

  AI agents execute well when context is explicit and the destination is clear. When the Coda is defined, Notes capture assumptions and constraints, and Beats describe durable capabilities, agents have the structured context they need to operate reliably instead of guessing at intent.

  Without that structure, agents fill the gaps themselves. The gaps get filled quickly, but not necessarily correctly. Harmonic Composition was designed in part to address exactly this: the faster agents can execute, the more important it becomes to give them something accurate to execute against.

• How do the three frameworks relate to each other?

  Harmonic Composition operates within a single system or engagement. Harmonic Orchestration coordinates delivery across multiple systems and agents. Harmonic Portfolio Management operates at the portfolio level, mapping capabilities across the wider landscape.

  They are designed to compose: Orchestration assumes Composition is running within each system; Portfolio Management provides the strategic context that individual Codas should reflect. You can start with Composition alone and layer in the others as the scope of your work expands.

Composition

• What happens to old Beats?

  Beats are durable by definition. A Beat remains in the system and continues to evolve through Revisions for as long as the capability it describes is relevant to the current Coda.

  When a capability is no longer relevant — because the Coda has changed, the system has moved on, or the need no longer exists — the Beat can be retired. A retired Beat is not deleted. It becomes part of the record of what the system was and what it needed at a prior stage, which is itself a form of context worth preserving.

• How does the Coda relate to Beats?

  The Coda defines the destination; Beats define the durable capabilities the system needs to reach it. The relationship is directional: the Coda shapes which Beats are relevant for a given phase, and the Beats collectively describe the path to the Coda.

  A Beat that cannot be connected to the current Coda does not belong in the current phase. Conversely, a Coda that has no Beat supporting a critical capability it requires signals that the Beat set is incomplete. During the Compose phase, the relationship between the Coda and the Beats is explicitly evaluated — not just whether each Beat is well-formed, but whether the full set of Beats is sufficient to reach the destination.

• What is the role of Notes in execution?

  Notes carry the context — assumptions, constraints, and decisions — that keeps Revisions aligned with intent even as the team changes or time passes.

  During the Execute phase, Notes serve as the reference layer: when a decision in a Revision is unclear, or when a constraint makes a straightforward approach unworkable, Notes provide the explanation. They transform institutional memory from something that lives in people's heads into something that lives in the system, available to whoever needs it, whenever they need it.