Practical guides, quick references, and implementation standards for applying Harmonic Design in real projects.<\/p>\n\n\n\n
What Harmonic Design is, why it exists, and who it helps. Start with the conceptual foundation before reaching for the tools.<\/p>\n <\/div>\n\n
VBD, EBD, BDT, and Project Design – each a complete methodology, each structurally isomorphic with the others.<\/p>\n <\/div>\n\n
Follow the four-phase checklist below. Begin with volatility analysis, then decompose experience, map your tests, and derive your plan.<\/p>\n <\/div>\n\n <\/div>\n <\/section>\n\n \n Applying HD to a Project<\/h2>\n \n\n \n \n \n <\/svg>\n <\/div>\n \n Phase 1 — VBD<\/div>\n Volatility Analysis<\/div>\n <\/div>\n <\/div>\n \n Before writing any structure, identify where change is concentrated.<\/p>\n \n What changes most often? (business rules, UI interactions, schema)<\/li>\n What almost never changes? (orchestration sequence, core algorithms)<\/li>\n What crosses a system boundary? (filesystem, network, database, subprocess)<\/li>\n <\/ul>\n Draw the boundary map: Managers<\/strong> orchestrate, Engines<\/strong> execute, Resource Accessors<\/strong> isolate I\/O, Utilities<\/strong> handle cross-cutting concerns.<\/p>\n <\/div>\n <\/div>\n\n \n \n \n <\/svg>\n <\/div>\n \n Phase 2 — EBD<\/div>\n Experience Decomposition<\/div>\n <\/div>\n <\/div>\n \n Identify core user journeys and decompose each into three structural levels.<\/p>\n \n Experience<\/strong> — the complete journey (e.g., “Onboard a new user”)<\/li>\n Flows<\/strong> — goal-directed sequences within it (e.g., “Collect user info”)<\/li>\n Interactions<\/strong> — the atomic inputs (e.g., text fields, dropdowns, toggles)<\/li>\n <\/ul>\n <\/div>\n <\/div>\n\n \n \n \n <\/svg>\n <\/div>\n \n Phase 3 — BDT<\/div>\n Test Strategy<\/div>\n <\/div>\n <\/div>\n \n Map the test spiral to your component boundaries.<\/p>\n \n Unit tests<\/strong> — Engines and Flows; mock at the boundary<\/li>\n Integration tests<\/strong> — Manager → Engine seams, Engine → Accessor seams<\/li>\n E2E tests<\/strong> — Complete user journeys, full stack<\/li>\n <\/ul>\n <\/div>\n <\/div>\n\n \n \n \n <\/svg>\n <\/div>\n \n Phase 4 — PD<\/div>\n Project Plan<\/div>\n <\/div>\n <\/div>\n \n Derive the project plan directly from the architecture.<\/p>\n \n Each component → work package<\/li>\n Each dependency → precedence relationship<\/li>\n Critical path → project duration<\/li>\n Float distribution → risk profile<\/li>\n <\/ul>\n <\/div>\n <\/div>\n\n <\/div>\n <\/section>\n\n \n Quick Reference<\/h2>\n\n Communication Rules<\/h3>\n \n The universal rule: state flows downward, results propagate upward, horizontal coordination is prohibited.<\/strong>\n <\/div>\n\n \n \n \n Call Pattern<\/th>Allowed?<\/th>Notes<\/th><\/tr>\n <\/thead>\n \n Manager → Engine<\/td>✓<\/td>Synchronous invocation<\/td><\/tr>\n Manager → Accessor<\/td>✓<\/td>For reads or state persistence<\/td><\/tr>\n Manager → Manager<\/td>✓ (async only)<\/td>Fire-and-forget via event bus<\/td><\/tr>\n Engine → Accessor<\/td>✓<\/td>For reference data or persistence<\/td><\/tr>\n Engine → Engine<\/td>✗<\/td>Manager composes instead<\/td><\/tr>\n Accessor → Accessor<\/td>✗<\/td>Manager fetches from both<\/td><\/tr>\n Engine → Manager<\/td>✗<\/td>Upward call forbidden<\/td><\/tr>\n Accessor → Engine<\/td>✗<\/td>Upward call forbidden<\/td><\/tr>\n <\/tbody>\n <\/table>\n <\/figure>\n\n Component Directory Structure<\/h3>\n managers\/\n├── order_manager\/\n│ ├── i_order_manager.py # Interface (contract)\n│ ├── order_manager.py # Implementation\n│ └── _helpers.py # Private helpers\nengines\/\n├── pricing_engine\/\n│ ├── i_pricing_engine.py\n│ └── pricing_engine.py\naccessors\/\n├── inventory_accessor\/\n│ ├── i_inventory_accessor.py\n│ └── inventory_accessor.py\nutilities\/\n└── logging\/\n └── logger.py<\/code><\/pre>\n Every component gets its own subdirectory. Interface and implementation can live together – start simple and separate as deployment needs evolve. Components can have private helpers without polluting the tier namespace.<\/p>\n\n <\/section>\n\n \n Full documentation including stack-specific implementation guides (Python, Java, TypeScript, .NET, Go), project structure templates, and worked examples is in development. Get in touch<\/a> if you need implementation support now.\n <\/div>\n\n<\/div>","protected":false},"excerpt":{"rendered":"Documentation Practical guides, quick references, and implementation standards for applying Harmonic Design in real projects. Getting Started 1 Understand the framework What Harmonic Design is, why it exists, and who it helps. Start with the conceptual foundation before reaching for the tools. 2 Explore the four pillars VBD, EBD, BDT, and Project Design – each … 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-12","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:\/\/harmonic-framework.com\/es\/author\/"},"uagb_comment_info":0,"uagb_excerpt":"Documentation Practical guides, quick references, and implementation standards for applying Harmonic Design in real projects. Getting Started 1 Understand the framework What Harmonic Design is, why it exists, and who it helps. Start with the conceptual foundation before reaching for the tools. 2 Explore the four pillars VBD, EBD, BDT, and Project Design – each…","_links":{"self":[{"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages\/12","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/types\/page"}],"replies":[{"embeddable":true,"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/comments?post=12"}],"version-history":[{"count":7,"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages\/12\/revisions"}],"predecessor-version":[{"id":762,"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages\/12\/revisions\/762"}],"wp:attachment":[{"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/media?parent=12"}],"wp:term":[{"taxonomy":"methodology","embeddable":true,"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/methodology?post=12"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
Before writing any structure, identify where change is concentrated.<\/p>\n
Draw the boundary map: Managers<\/strong> orchestrate, Engines<\/strong> execute, Resource Accessors<\/strong> isolate I\/O, Utilities<\/strong> handle cross-cutting concerns.<\/p>\n <\/div>\n <\/div>\n\n \n \n \n <\/svg>\n <\/div>\n \n Phase 2 — EBD<\/div>\n Experience Decomposition<\/div>\n <\/div>\n <\/div>\n \n Identify core user journeys and decompose each into three structural levels.<\/p>\n \n Experience<\/strong> — the complete journey (e.g., “Onboard a new user”)<\/li>\n Flows<\/strong> — goal-directed sequences within it (e.g., “Collect user info”)<\/li>\n Interactions<\/strong> — the atomic inputs (e.g., text fields, dropdowns, toggles)<\/li>\n <\/ul>\n <\/div>\n <\/div>\n\n \n \n \n <\/svg>\n <\/div>\n \n Phase 3 — BDT<\/div>\n Test Strategy<\/div>\n <\/div>\n <\/div>\n \n Map the test spiral to your component boundaries.<\/p>\n \n Unit tests<\/strong> — Engines and Flows; mock at the boundary<\/li>\n Integration tests<\/strong> — Manager → Engine seams, Engine → Accessor seams<\/li>\n E2E tests<\/strong> — Complete user journeys, full stack<\/li>\n <\/ul>\n <\/div>\n <\/div>\n\n \n \n \n <\/svg>\n <\/div>\n \n Phase 4 — PD<\/div>\n Project Plan<\/div>\n <\/div>\n <\/div>\n \n Derive the project plan directly from the architecture.<\/p>\n \n Each component → work package<\/li>\n Each dependency → precedence relationship<\/li>\n Critical path → project duration<\/li>\n Float distribution → risk profile<\/li>\n <\/ul>\n <\/div>\n <\/div>\n\n <\/div>\n <\/section>\n\n \n Quick Reference<\/h2>\n\n Communication Rules<\/h3>\n \n The universal rule: state flows downward, results propagate upward, horizontal coordination is prohibited.<\/strong>\n <\/div>\n\n \n \n \n Call Pattern<\/th>Allowed?<\/th>Notes<\/th><\/tr>\n <\/thead>\n \n Manager → Engine<\/td>✓<\/td>Synchronous invocation<\/td><\/tr>\n Manager → Accessor<\/td>✓<\/td>For reads or state persistence<\/td><\/tr>\n Manager → Manager<\/td>✓ (async only)<\/td>Fire-and-forget via event bus<\/td><\/tr>\n Engine → Accessor<\/td>✓<\/td>For reference data or persistence<\/td><\/tr>\n Engine → Engine<\/td>✗<\/td>Manager composes instead<\/td><\/tr>\n Accessor → Accessor<\/td>✗<\/td>Manager fetches from both<\/td><\/tr>\n Engine → Manager<\/td>✗<\/td>Upward call forbidden<\/td><\/tr>\n Accessor → Engine<\/td>✗<\/td>Upward call forbidden<\/td><\/tr>\n <\/tbody>\n <\/table>\n <\/figure>\n\n Component Directory Structure<\/h3>\n managers\/\n├── order_manager\/\n│ ├── i_order_manager.py # Interface (contract)\n│ ├── order_manager.py # Implementation\n│ └── _helpers.py # Private helpers\nengines\/\n├── pricing_engine\/\n│ ├── i_pricing_engine.py\n│ └── pricing_engine.py\naccessors\/\n├── inventory_accessor\/\n│ ├── i_inventory_accessor.py\n│ └── inventory_accessor.py\nutilities\/\n└── logging\/\n └── logger.py<\/code><\/pre>\n Every component gets its own subdirectory. Interface and implementation can live together – start simple and separate as deployment needs evolve. Components can have private helpers without polluting the tier namespace.<\/p>\n\n <\/section>\n\n \n Full documentation including stack-specific implementation guides (Python, Java, TypeScript, .NET, Go), project structure templates, and worked examples is in development. Get in touch<\/a> if you need implementation support now.\n <\/div>\n\n<\/div>","protected":false},"excerpt":{"rendered":"Documentation Practical guides, quick references, and implementation standards for applying Harmonic Design in real projects. Getting Started 1 Understand the framework What Harmonic Design is, why it exists, and who it helps. Start with the conceptual foundation before reaching for the tools. 2 Explore the four pillars VBD, EBD, BDT, and Project Design – each … 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-12","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:\/\/harmonic-framework.com\/es\/author\/"},"uagb_comment_info":0,"uagb_excerpt":"Documentation Practical guides, quick references, and implementation standards for applying Harmonic Design in real projects. Getting Started 1 Understand the framework What Harmonic Design is, why it exists, and who it helps. Start with the conceptual foundation before reaching for the tools. 2 Explore the four pillars VBD, EBD, BDT, and Project Design – each…","_links":{"self":[{"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages\/12","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/types\/page"}],"replies":[{"embeddable":true,"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/comments?post=12"}],"version-history":[{"count":7,"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages\/12\/revisions"}],"predecessor-version":[{"id":762,"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages\/12\/revisions\/762"}],"wp:attachment":[{"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/media?parent=12"}],"wp:term":[{"taxonomy":"methodology","embeddable":true,"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/methodology?post=12"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
Identify core user journeys and decompose each into three structural levels.<\/p>\n
Map the test spiral to your component boundaries.<\/p>\n
Derive the project plan directly from the architecture.<\/p>\n
managers\/\n├── order_manager\/\n│ ├── i_order_manager.py # Interface (contract)\n│ ├── order_manager.py # Implementation\n│ └── _helpers.py # Private helpers\nengines\/\n├── pricing_engine\/\n│ ├── i_pricing_engine.py\n│ └── pricing_engine.py\naccessors\/\n├── inventory_accessor\/\n│ ├── i_inventory_accessor.py\n│ └── inventory_accessor.py\nutilities\/\n└── logging\/\n └── logger.py<\/code><\/pre>\n Every component gets its own subdirectory. Interface and implementation can live together – start simple and separate as deployment needs evolve. Components can have private helpers without polluting the tier namespace.<\/p>\n\n <\/section>\n\n \n Full documentation including stack-specific implementation guides (Python, Java, TypeScript, .NET, Go), project structure templates, and worked examples is in development. Get in touch<\/a> if you need implementation support now.\n <\/div>\n\n<\/div>","protected":false},"excerpt":{"rendered":"Documentation Practical guides, quick references, and implementation standards for applying Harmonic Design in real projects. Getting Started 1 Understand the framework What Harmonic Design is, why it exists, and who it helps. Start with the conceptual foundation before reaching for the tools. 2 Explore the four pillars VBD, EBD, BDT, and Project Design – each … 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-12","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:\/\/harmonic-framework.com\/es\/author\/"},"uagb_comment_info":0,"uagb_excerpt":"Documentation Practical guides, quick references, and implementation standards for applying Harmonic Design in real projects. Getting Started 1 Understand the framework What Harmonic Design is, why it exists, and who it helps. Start with the conceptual foundation before reaching for the tools. 2 Explore the four pillars VBD, EBD, BDT, and Project Design – each…","_links":{"self":[{"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages\/12","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/types\/page"}],"replies":[{"embeddable":true,"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/comments?post=12"}],"version-history":[{"count":7,"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages\/12\/revisions"}],"predecessor-version":[{"id":762,"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages\/12\/revisions\/762"}],"wp:attachment":[{"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/media?parent=12"}],"wp:term":[{"taxonomy":"methodology","embeddable":true,"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/methodology?post=12"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
Every component gets its own subdirectory. Interface and implementation can live together – start simple and separate as deployment needs evolve. Components can have private helpers without polluting the tier namespace.<\/p>\n\n <\/section>\n\n
Documentation Practical guides, quick references, and implementation standards for applying Harmonic Design in real projects. Getting Started 1 Understand the framework What Harmonic Design is, why it exists, and who it helps. Start with the conceptual foundation before reaching for the tools. 2 Explore the four pillars VBD, EBD, BDT, and Project Design – each … 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-12","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:\/\/harmonic-framework.com\/es\/author\/"},"uagb_comment_info":0,"uagb_excerpt":"Documentation Practical guides, quick references, and implementation standards for applying Harmonic Design in real projects. Getting Started 1 Understand the framework What Harmonic Design is, why it exists, and who it helps. Start with the conceptual foundation before reaching for the tools. 2 Explore the four pillars VBD, EBD, BDT, and Project Design – each…","_links":{"self":[{"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages\/12","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/types\/page"}],"replies":[{"embeddable":true,"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/comments?post=12"}],"version-history":[{"count":7,"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages\/12\/revisions"}],"predecessor-version":[{"id":762,"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages\/12\/revisions\/762"}],"wp:attachment":[{"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/media?parent=12"}],"wp:term":[{"taxonomy":"methodology","embeddable":true,"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/methodology?post=12"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}