Skip to main content

HBK Core

HBK means Heart, Brain, and Soul.

It is the shared product core that stays intact even when HausFlow splits into Family, Roommate, or future Professional and white-label editions.

Why HBK Matters​

The subject changes by edition.

  • Family deals with shared home life, parent load, and child participation
  • Roommate deals with fairness, agreements, and adult-neutral coordination
  • Professional and white-label editions may deal with team operations, branded workflows, or partner-specific environments

What should not change is the deeper product character.

HBK is that character layer.

Heart​

Heart is how the system relates to people.

It defines:

  • tone
  • care
  • dignity
  • emotional safety
  • no-shame support

Heart prevents the product from becoming cold, punitive, or manipulative.

In Family, Heart feels warm and supportive.

In Roommate, Heart feels respectful and boundary-aware.

In Professional editions, Heart should still protect dignity even when the language becomes more operational.

Brain​

Brain is how the system thinks.

It defines:

  • structure
  • logic
  • prioritization
  • clarity
  • sequencing
  • low-friction defaults

Brain turns confusion into usable next steps. It is where Behavioral OS becomes practical product behavior.

Brain should stay strong across every edition:

  • responsibilities should be visible
  • the next action should be easier to identify
  • resets should be built in
  • better defaults should reduce avoidable friction

Soul​

Soul is what the product ultimately stands for.

It defines:

  • worldview
  • product ethics
  • standards
  • long-term identity

Soul answers the question: what kind of system are we building, and what do we refuse to become?

For HausFlow, Soul includes:

  • systems over willpower
  • support over shame
  • clarity over chaos
  • consistency over intensity
  • recovery as part of the design, not proof of failure

HBK Across Editions​

HBK stays shared.

What changes is the application layer:

  • Heart changes tone by audience
  • Brain changes workflow framing by environment
  • Soul stays aligned to Mavaro standards

That means editions can diverge without becoming different philosophies.

Practical Rule​

When a new edition is added, do not rewrite the whole product philosophy.

Instead:

  1. keep HBK intact
  2. adapt the surface language
  3. adapt the governance model
  4. adapt the examples and workflows
  5. document only the edition-specific differences

That is how HausFlow scales without turning into three unrelated products.