{"id":12,"date":"2026-03-13T22:42:48","date_gmt":"2026-03-13T22:42:48","guid":{"rendered":"https:\/\/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:\/\/harmonic-framework.com\/es\/docs\/","title":{"rendered":"Documentation"},"content":{"rendered":"<div class=\"hf-docs-page\">\n<div class=\"hf-docs-hero\">\n<h1>Documentation<\/h1>\n<p>Practical guides, quick references, and implementation standards for applying Harmonic Design in real projects.<\/p>\n<\/p><\/div>\n<div class=\"hf-docs-inner\">\n<section class=\"hf-docs-section\">\n<h2>Getting Started<\/h2>\n<div class=\"hf-docs-steps\">\n<div class=\"hf-docs-step\">\n<div class=\"hf-docs-step__num\">1<\/div>\n<div class=\"hf-docs-step__title\"><a href=\"\/es\/about\/\">Understand the framework<\/a><\/div>\n<p class=\"hf-docs-step__desc\">What Harmonic Design is, why it exists, and who it helps. Start with the conceptual foundation before reaching for the tools.<\/p>\n<\/p><\/div>\n<div class=\"hf-docs-step\">\n<div class=\"hf-docs-step__num\">2<\/div>\n<div class=\"hf-docs-step__title\"><a href=\"\/es\/methodologies\/\">Explore the four pillars<\/a><\/div>\n<p class=\"hf-docs-step__desc\">VBD, EBD, BDT, and Project Design \u2014 each a complete methodology, each structurally isomorphic with the others.<\/p>\n<\/p><\/div>\n<div class=\"hf-docs-step\">\n<div class=\"hf-docs-step__num\">3<\/div>\n<div class=\"hf-docs-step__title\">Apply to a real project<\/div>\n<p class=\"hf-docs-step__desc\">Follow the four-phase checklist below. Begin with volatility analysis, then decompose experience, map your tests, and derive your plan.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n<section class=\"hf-docs-section\">\n<h2>Applying HD to a Project<\/h2>\n<div class=\"hf-docs-phases\">\n<div class=\"hf-docs-phase hf-docs-phase--1\">\n<div class=\"hf-docs-phase__header\">\n<div class=\"hf-docs-phase__icon\">\n              <svg viewbox=\"0 0 24 24\" width=\"20\" height=\"20\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><rect x=\"3\" y=\"3\" width=\"7\" height=\"7\" rx=\"1\"\/><rect x=\"14\" y=\"3\" width=\"7\" height=\"7\" rx=\"1\"\/><rect x=\"3\" y=\"14\" width=\"7\" height=\"7\" rx=\"1\"\/><rect x=\"14\" y=\"14\" width=\"7\" height=\"7\" rx=\"1\"\/><\/svg>\n            <\/div>\n<div>\n<div class=\"hf-docs-phase__label\">Phase 1 &mdash; VBD<\/div>\n<div class=\"hf-docs-phase__name\">Volatility Analysis<\/div>\n<\/p><\/div>\n<\/p><\/div>\n<div class=\"hf-docs-phase__body\">\n<p>Before writing any structure, identify where change is concentrated.<\/p>\n<ul>\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<p style=\"margin-top:0.75rem;\">Draw the boundary map: <strong>Managers<\/strong> orchestrate, <strong>Engines<\/strong> execute, <strong>Resource Accessors<\/strong> isolate I\/O, <strong>Utilities<\/strong> handle cross-cutting concerns.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<div class=\"hf-docs-phase hf-docs-phase--2\">\n<div class=\"hf-docs-phase__header\">\n<div class=\"hf-docs-phase__icon\">\n              <svg viewbox=\"0 0 24 24\" width=\"20\" height=\"20\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><circle cx=\"12\" cy=\"5\" r=\"2\"\/><path d=\"M12 7v4\"\/><circle cx=\"5\" cy=\"17\" r=\"2\"\/><circle cx=\"19\" cy=\"17\" r=\"2\"\/><path d=\"M12 11l-5.27 4.27M12 11l5.27 4.27\"\/><\/svg>\n            <\/div>\n<div>\n<div class=\"hf-docs-phase__label\">Phase 2 &mdash; EBD<\/div>\n<div class=\"hf-docs-phase__name\">Experience Decomposition<\/div>\n<\/p><\/div>\n<\/p><\/div>\n<div class=\"hf-docs-phase__body\">\n<p>Identify core user journeys and decompose each into three structural levels.<\/p>\n<ul>\n<li><strong>Experience<\/strong> &mdash; the complete journey (e.g., &ldquo;Onboard a new user&rdquo;)<\/li>\n<li><strong>Flows<\/strong> &mdash; goal-directed sequences within it (e.g., &ldquo;Collect user info&rdquo;)<\/li>\n<li><strong>Interactions<\/strong> &mdash; the atomic inputs (e.g., text fields, dropdowns, toggles)<\/li>\n<\/ul><\/div>\n<\/p><\/div>\n<div class=\"hf-docs-phase hf-docs-phase--3\">\n<div class=\"hf-docs-phase__header\">\n<div class=\"hf-docs-phase__icon\">\n              <svg viewbox=\"0 0 24 24\" width=\"20\" height=\"20\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><circle cx=\"12\" cy=\"12\" r=\"9\"\/><path d=\"M9 12l2 2 4-4\"\/><\/svg>\n            <\/div>\n<div>\n<div class=\"hf-docs-phase__label\">Phase 3 &mdash; BDT<\/div>\n<div class=\"hf-docs-phase__name\">Test Strategy<\/div>\n<\/p><\/div>\n<\/p><\/div>\n<div class=\"hf-docs-phase__body\">\n<p>Map the test spiral to your component boundaries.<\/p>\n<ul>\n<li><strong>Unit tests<\/strong> &mdash; Engines and Flows; mock at the boundary<\/li>\n<li><strong>Integration tests<\/strong> &mdash; Manager &rarr; Engine seams, Engine &rarr; Accessor seams<\/li>\n<li><strong>E2E tests<\/strong> &mdash; Complete user journeys, full stack<\/li>\n<\/ul><\/div>\n<\/p><\/div>\n<div class=\"hf-docs-phase hf-docs-phase--4\">\n<div class=\"hf-docs-phase__header\">\n<div class=\"hf-docs-phase__icon\">\n              <svg viewbox=\"0 0 24 24\" width=\"20\" height=\"20\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 3H5a2 2 0 0 0-2 2v4\"\/><path d=\"M15 3h4a2 2 0 0 1 2 2v4\"\/><path d=\"M9 21H5a2 2 0 0 1-2-2v-4\"\/><path d=\"M15 21h4a2 2 0 0 0 2-2v-4\"\/><path d=\"M7 12h10\"\/><path d=\"M12 7v10\"\/><\/svg>\n            <\/div>\n<div>\n<div class=\"hf-docs-phase__label\">Phase 4 &mdash; PD<\/div>\n<div class=\"hf-docs-phase__name\">Project Plan<\/div>\n<\/p><\/div>\n<\/p><\/div>\n<div class=\"hf-docs-phase__body\">\n<p>Derive the project plan directly from the architecture.<\/p>\n<ul>\n<li>Each component &rarr; work package<\/li>\n<li>Each dependency &rarr; precedence relationship<\/li>\n<li>Critical path &rarr; project duration<\/li>\n<li>Float distribution &rarr; risk profile<\/li>\n<\/ul><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n<section class=\"hf-docs-section\">\n<h2>Quick Reference<\/h2>\n<h3 style=\"font-size:1rem;font-weight:700;margin:0 0 0.75rem;\">Communication Rules<\/h3>\n<div class=\"hf-docs-callout\">\n        The universal rule: <strong>state flows downward, results propagate upward, horizontal coordination is prohibited.<\/strong>\n      <\/div>\n<figure class=\"wp-block-table\" style=\"margin:0 0 2rem;\">\n<table>\n<thead>\n<tr>\n<th>Call Pattern<\/th>\n<th>Allowed?<\/th>\n<th>Notes<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Manager &rarr; Engine<\/td>\n<td>&#10003;<\/td>\n<td>Synchronous invocation<\/td>\n<\/tr>\n<tr>\n<td>Manager &rarr; Accessor<\/td>\n<td>&#10003;<\/td>\n<td>For reads or state persistence<\/td>\n<\/tr>\n<tr>\n<td>Manager &rarr; Manager<\/td>\n<td>&#10003; (async only)<\/td>\n<td>Fire-and-forget via event bus<\/td>\n<\/tr>\n<tr>\n<td>Engine &rarr; Accessor<\/td>\n<td>&#10003;<\/td>\n<td>For reference data or persistence<\/td>\n<\/tr>\n<tr>\n<td>Engine &rarr; Engine<\/td>\n<td>&#10007;<\/td>\n<td>Manager composes instead<\/td>\n<\/tr>\n<tr>\n<td>Accessor &rarr; Accessor<\/td>\n<td>&#10007;<\/td>\n<td>Manager fetches from both<\/td>\n<\/tr>\n<tr>\n<td>Engine &rarr; Manager<\/td>\n<td>&#10007;<\/td>\n<td>Upward call forbidden<\/td>\n<\/tr>\n<tr>\n<td>Accessor &rarr; Engine<\/td>\n<td>&#10007;<\/td>\n<td>Upward call forbidden<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n<h3 style=\"font-size:1rem;font-weight:700;margin:0 0 0.75rem;\">Component Directory Structure<\/h3>\n<pre class=\"wp-block-code\"><code class=\"\" data-line=\"\">managers\/\n&#x251C;&#x2500;&#x2500; order_manager\/\n&#x2502;   &#x251C;&#x2500;&#x2500; i_order_manager.py      # Interface (contract)\n&#x2502;   &#x251C;&#x2500;&#x2500; order_manager.py        # Implementation\n&#x2502;   &#x2514;&#x2500;&#x2500; _helpers.py             # Private helpers\nengines\/\n&#x251C;&#x2500;&#x2500; pricing_engine\/\n&#x2502;   &#x251C;&#x2500;&#x2500; i_pricing_engine.py\n&#x2502;   &#x2514;&#x2500;&#x2500; pricing_engine.py\naccessors\/\n&#x251C;&#x2500;&#x2500; inventory_accessor\/\n&#x2502;   &#x251C;&#x2500;&#x2500; i_inventory_accessor.py\n&#x2502;   &#x2514;&#x2500;&#x2500; inventory_accessor.py\nutilities\/\n&#x2514;&#x2500;&#x2500; logging\/\n    &#x2514;&#x2500;&#x2500; logger.py<\/code><\/pre>\n<p style=\"font-size:0.875rem;color:var(--hf-muted);margin-top:0.75rem;line-height:1.6;\">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<\/section>\n<div class=\"hf-docs-notice\">\n      Full documentation including stack-specific implementation guides (Python, Java, TypeScript, .NET, Go), project structure templates, and worked examples is in development. <a href=\"\/es\/contact\/\">Get in touch<\/a> if you need implementation support now.\n    <\/div>\n<\/p><\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>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 \u2014 each &#8230; <a title=\"Documentation\" class=\"read-more\" href=\"https:\/\/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:\/\/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 \u2014 each&hellip;","_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":4,"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages\/12\/revisions"}],"predecessor-version":[{"id":173,"href":"https:\/\/harmonic-framework.com\/es\/wp-json\/wp\/v2\/pages\/12\/revisions\/173"}],"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}]}}