{"id":4,"date":"2026-03-13T22:42:50","date_gmt":"2026-03-13T22:42:50","guid":{"rendered":"https:\/\/dev.harmonic-framework.com\/?page_id=4"},"modified":"2026-03-14T01:23:06","modified_gmt":"2026-03-14T01:23:06","slug":"home","status":"publish","type":"page","link":"https:\/\/dev.harmonic-framework.com\/es\/","title":{"rendered":"Harmonic Framework"},"content":{"rendered":"
\n\n\n

One Structure. Every Layer.<\/h1>\n\n\n\n

Harmonic Design is a unified software engineering framework. It applies a single organizing principle \u2014 isolate change along its natural axes<\/strong> \u2014 consistently across backend architecture, interface architecture, test strategy, and project planning.<\/p>\n\n\n\n

Every long-lived software system has a backend that must evolve, an interface that must evolve, tests that must survive both kinds of evolution, and a project plan that must anticipate, sequence, and resource all three. These concerns are typically governed by separate frameworks and separate mental models. Harmonic Design unifies them under a single structural discipline.<\/p>\n\n\n<\/div><\/div>\n\n\n\n

\n\n\n

Methodologies<\/h2>\n\n\n\n

Four methodologies, one structural principle. Each governs a different architectural concern. All share the same decomposition logic.<\/p>\n\n\n\n

\n\n\n
\n
\n
\n<\/svg>\n<\/div>\n

Volatility-Based Decomposition<\/a><\/h3>\n

Backend systems organized around anticipated change, not current functionality. Components that change for the same reason belong together; components that change for different reasons belong apart.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n<\/svg>\n<\/div>\n

Experience-Based Decomposition<\/a><\/h3>\n

Interface architecture structured around human intent, not screens. Experiences represent complete user journeys. Flows own goal-directed sequences. Interactions are atomic.<\/p>\n<\/div>\n<\/div>\n\n\n<\/div>\n\n\n\n

\n\n\n
\n
\n
\n<\/svg>\n<\/div>\n

Boundary-Driven Testing<\/a><\/h3>\n

Testing difficulty is architectural evidence. The test spiral is a structural map, not a testing methodology. Correct boundaries produce testable systems; incorrect boundaries produce test friction.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n<\/svg>\n<\/div>\n

Project Design<\/a><\/h3>\n

Project plans derived from architecture. Components become work packages. Dependencies become the project network. Estimation follows from structural analysis, not intuition.<\/p>\n<\/div>\n<\/div>\n\n\n<\/div>\n\n\n<\/div><\/div>\n\n\n\n

\n\n\n

Structural Isomorphism<\/h2>\n\n\n\n

The central claim: the role taxonomy of VBD, the tier taxonomy of EBD, the test scope taxonomy of BDT, and the work package classification of Project Design map onto each other exactly. They are four readings of the same underlying structural map.<\/p>\n\n\n\n

\n\n
Tier<\/th>VBD<\/th>EBD<\/th>BDT<\/th>Project Design<\/th><\/tr><\/thead>
Orchestration<\/td>Manager<\/td>Experience<\/td>Integration \/ E2E<\/td>Integration Milestone<\/td><\/tr>
Execution<\/td>Engine<\/td>Flow \/ Interaction<\/td>Unit<\/td>Core Work Package<\/td><\/tr>
External Boundary<\/td>Resource Accessor<\/td>API Accessor<\/td>Unit (translation)<\/td>Boundary Work Package<\/td><\/tr>
Cross-Cutting<\/td>Utility<\/td>Utility<\/td>Unit<\/td>Shared Infrastructure<\/td><\/tr><\/tbody><\/table><\/figure>\n\n<\/div><\/div>\n\n\n\n

A change in business logic touches one Engine, one Flow, one set of unit tests, and one work package \u2014 structurally bounded, predictably scoped, estimable from the architecture.<\/p>\n\n\n<\/div><\/div>\n\n\n\n

\n\n\n

Read the framework. Apply the structure.<\/h3>\n\n\n\n

Start with the methodology that matches your current concern, or read the white papers for the theoretical foundation.<\/p>\n\n\n\n

\n\n
Methodologies<\/a><\/div>\n\n\n
White Papers<\/a><\/div>\n\n<\/div>\n\n\n<\/div><\/div>","protected":false},"excerpt":{"rendered":"

One Structure. Every Layer. Harmonic Design is a unified software engineering framework. It applies a single organizing principle \u2014 isolate change along its natural axes \u2014 consistently across backend architecture, interface architecture, test strategy, and project planning. Every long-lived software system has a backend that must evolve, an interface that must evolve, tests that must … Read more<\/a><\/p>","protected":false},"author":0,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_uag_custom_page_level_css":"","footnotes":""},"methodology":[],"class_list":["post-4","page","type-page","status-publish"],"uagb_featured_image_src":{"full":false,"thumbnail":false,"medium":false,"medium_large":false,"large":false,"1536x1536":false,"2048x2048":false,"trp-custom-language-flag":false,"post-thumbnail":false,"hf-card":false,"hf-hero":false},"uagb_author_info":{"display_name":"","author_link":"https:\/\/dev.harmonic-framework.com\/es\/author\/"},"uagb_comment_info":0,"uagb_excerpt":"One Structure. Every Layer. Harmonic Design is a unified software engineering framework. It applies a single organizing principle \u2014 isolate change along its natural axes \u2014 consistently across backend architecture, interface architecture, test strategy, and project planning. Every long-lived software system has a backend that must evolve, an interface that must evolve, tests that must…","_links":{"self":[{"href":"https:\/\/dev.harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages\/4","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dev.harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/dev.harmonic-framework.com\/es\/wp-json\/wp\/v2\/types\/page"}],"replies":[{"embeddable":true,"href":"https:\/\/dev.harmonic-framework.com\/es\/wp-json\/wp\/v2\/comments?post=4"}],"version-history":[{"count":4,"href":"https:\/\/dev.harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages\/4\/revisions"}],"predecessor-version":[{"id":166,"href":"https:\/\/dev.harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages\/4\/revisions\/166"}],"wp:attachment":[{"href":"https:\/\/dev.harmonic-framework.com\/es\/wp-json\/wp\/v2\/media?parent=4"}],"wp:term":[{"taxonomy":"methodology","embeddable":true,"href":"https:\/\/dev.harmonic-framework.com\/es\/wp-json\/wp\/v2\/methodology?post=4"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}