{"id":12,"date":"2026-03-13T22:42:48","date_gmt":"2026-03-13T22:42:48","guid":{"rendered":"https:\/\/dev.harmonic-framework.com\/?page_id=12"},"modified":"2026-03-14T02:50:34","modified_gmt":"2026-03-14T02:50:34","slug":"docs","status":"publish","type":"page","link":"https:\/\/dev.harmonic-framework.com\/es\/docs\/","title":{"rendered":"Documentation"},"content":{"rendered":"<h1 class=\"wp-block-heading\">Documentation<\/h1>\n\n\n\n<p style=\"font-size:20px\">Practical guides, quick references, and implementation standards for applying Harmonic Design in real projects.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Getting Started<\/h2>\n\n\n\n<p>New to Harmonic Design? Start here:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><a href=\"\/es\/about\/\">Understand the framework<\/a> \u2014 what HD is, why it exists, and who it helps<\/li>\n<li><a href=\"\/es\/methodologies\/\">Explore the four pillars<\/a> \u2014 VBD, EBD, BDT, and Project Design<\/li>\n<li><strong>Apply to a real project<\/strong> \u2014 follow the practical checklist below<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Applying HD to a Project<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Phase 1: Volatility Analysis (VBD)<\/h3>\n\n\n\n<p>Before writing any structure, answer:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What changes most often? (business rules, UI interactions, schema)<\/li>\n<li>What almost never changes? (orchestration sequence, core algorithms)<\/li>\n<li>What crosses a system boundary? (filesystem, network, database, subprocess)<\/li>\n<\/ul>\n\n\n\n<p>Then draw the boundary map: <strong>Managers<\/strong> for stable orchestration, <strong>Engines<\/strong> for volatile business logic, <strong>Resource Accessors<\/strong> for all I\/O, <strong>Utilities<\/strong> for cross-cutting concerns.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Phase 2: Experience Decomposition (EBD)<\/h3>\n\n\n\n<p>Identify core user journeys and decompose each into:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Experience<\/strong> \u2014 the complete journey (e.g., &#8220;Onboard a new user&#8221;)<\/li>\n<li><strong>Flows<\/strong> \u2014 the goal-directed sequences within it (e.g., &#8220;Collect user info&#8221;, &#8220;Select preferences&#8221;)<\/li>\n<li><strong>Interactions<\/strong> \u2014 the atomic inputs (e.g., text fields, dropdowns, toggles)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Phase 3: Test Strategy (BDT)<\/h3>\n\n\n\n<p>Map the test spiral to your components:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Unit tests<\/strong> \u2014 Engines and Flows with dependencies mocked at the boundary<\/li>\n<li><strong>Integration tests<\/strong> \u2014 Manager \u2192 Engine seams, Engine \u2192 Accessor seams<\/li>\n<li><strong>E2E tests<\/strong> \u2014 Complete user journeys, full stack<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Phase 4: Project Plan (PD)<\/h3>\n\n\n\n<p>Derive the project plan from the architecture:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Each component \u2192 work package<\/li>\n<li>Each dependency \u2192 precedence relationship<\/li>\n<li>Critical path \u2192 project duration<\/li>\n<li>Float distribution \u2192 risk profile<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Quick Reference<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Communication Rules<\/h3>\n\n\n\n<p>The universal rule: <strong>state flows downward, results propagate upward, horizontal coordination is prohibited.<\/strong><\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Call Pattern<\/th><th>Allowed?<\/th><th>Notes<\/th><\/tr><\/thead><tbody><tr><td>Manager \u2192 Engine<\/td><td>\u2713<\/td><td>Synchronous invocation<\/td><\/tr><tr><td>Manager \u2192 Accessor<\/td><td>\u2713<\/td><td>For reads or state persistence<\/td><\/tr><tr><td>Manager \u2192 Manager<\/td><td>\u2713 (async only)<\/td><td>Fire-and-forget via event bus<\/td><\/tr><tr><td>Engine \u2192 Accessor<\/td><td>\u2713<\/td><td>For reference data or persistence<\/td><\/tr><tr><td>Engine \u2192 Engine<\/td><td>\u2717<\/td><td>Manager composes instead<\/td><\/tr><tr><td>Accessor \u2192 Accessor<\/td><td>\u2717<\/td><td>Manager fetches from both<\/td><\/tr><tr><td>Engine \u2192 Manager<\/td><td>\u2717<\/td><td>Upward call forbidden<\/td><\/tr><tr><td>Accessor \u2192 Engine<\/td><td>\u2717<\/td><td>Upward call forbidden<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Component Directory Structure<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code class=\"\" data-line=\"\">managers\/\n\u251c\u2500\u2500 order_manager\/\n\u2502   \u251c\u2500\u2500 i_order_manager.py      # Interface (contract)\n\u2502   \u251c\u2500\u2500 order_manager.py        # Implementation\n\u2502   \u2514\u2500\u2500 _helpers.py             # Private helpers\nengines\/\n\u251c\u2500\u2500 pricing_engine\/\n\u2502   \u251c\u2500\u2500 i_pricing_engine.py\n\u2502   \u2514\u2500\u2500 pricing_engine.py\naccessors\/\n\u251c\u2500\u2500 inventory_accessor\/\n\u2502   \u251c\u2500\u2500 i_inventory_accessor.py\n\u2502   \u2514\u2500\u2500 inventory_accessor.py\nutilities\/\n\u251c\u2500\u2500 logging\/\n\u2502   \u2514\u2500\u2500 logger.py<\/code><\/pre>\n\n\n\n<p>Every component gets its own subdirectory. Interface and implementation can live together \u2014 start simple and separate as deployment needs evolve. Components can have private helpers without polluting the tier namespace.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p class=\"hf-text-muted\">Full documentation including stack-specific implementation guides (Python, Java, TypeScript, .NET, Go), project structure templates, and worked examples is in development.<\/p>","protected":false},"excerpt":{"rendered":"<p>Documentation Practical guides, quick references, and implementation standards for applying Harmonic Design in real projects. Getting Started New to Harmonic Design? Start here: Understand the framework \u2014 what HD is, why it exists, and who it helps Explore the four pillars \u2014 VBD, EBD, BDT, and Project Design Apply to a real project \u2014 follow &#8230; <a title=\"Documentation\" class=\"read-more\" href=\"https:\/\/dev.harmonic-framework.com\/es\/docs\/\" aria-label=\"Read more about Documentation\">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:\/\/dev.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 New to Harmonic Design? Start here: Understand the framework \u2014 what HD is, why it exists, and who it helps Explore the four pillars \u2014 VBD, EBD, BDT, and Project Design Apply to a real project \u2014 follow&hellip;","_links":{"self":[{"href":"https:\/\/dev.harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages\/12","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=12"}],"version-history":[{"count":4,"href":"https:\/\/dev.harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages\/12\/revisions"}],"predecessor-version":[{"id":173,"href":"https:\/\/dev.harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages\/12\/revisions\/173"}],"wp:attachment":[{"href":"https:\/\/dev.harmonic-framework.com\/es\/wp-json\/wp\/v2\/media?parent=12"}],"wp:term":[{"taxonomy":"methodology","embeddable":true,"href":"https:\/\/dev.harmonic-framework.com\/es\/wp-json\/wp\/v2\/methodology?post=12"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}