Skip to main content

HausFlow Editions

HausFlow is one platform with multiple editions.

The foundation stays consistent:

  • systems over willpower
  • clarity over guesswork
  • support over shame
  • visible responsibilities over invisible load
  • recovery built into the product, not bolted on afterward

What changes by edition is the context, tone, and governance model.

Shared Platform Layer​

Every edition should preserve the same underlying standards:

  • clear next actions
  • low-friction follow-through
  • repeatable routines and flows
  • calm, explainable support
  • trust-centered privacy and safety

That lets HausFlow reuse one documentation system without flattening every audience into the same wording.

Shared Core, Split Subjects​

HausFlow should be understood in two layers:

  • the shared core
  • the edition subject

The shared core carries HBK, Behavioral OS, trust boundaries, and product standards.

The edition subject changes the environment those standards are applied to:

  • Family = household harmony and support
  • Roommate = fairness and equal shared living
  • Professional / White-Label = operational clarity with controlled brand variation

See HBK Core and Edition Operating Model.

Current Edition Map​

HausFlow Family​

For households that need calmer coordination, visible responsibilities, and shared home rhythm.

  • warm and supportive
  • family-centered
  • parent and kid participation where appropriate
  • focused on reducing home stress and mental load
  • the most complete active implementation in this repository

See HausFlow Family Edition.

HausFlow Roommate​

For adults sharing a home who need fairness, transparency, and clear agreements between equals.

  • neutral and adult-oriented
  • fairness-centered
  • accountability without parental framing
  • focused on shared-space operations and conflict prevention
  • currently represented here more as edition architecture and partial/shared backend logic than as a full roommate app surface

See HausFlow Roommate Edition.

HausFlow Professional / White-Label​

For future partner, enterprise, or branded deployments built on the same core operating model.

  • edition-aware branding
  • configurable tone and policy boundaries
  • shared infrastructure with controlled variation
  • strong guardrails around rebranding and feature scope
  • future-facing in this repo, not a shipped product layer

See Professional and White-Label Direction.

Codebase Reality​

If you are using this docs hub to understand the current product, keep one distinction in mind:

  • the shared HausFlow model is broader than this single repo
  • this repo is primarily a HausFlow Family implementation
  • roommate and future professional variants should be documented as edition branches unless the local code proves feature parity

See Current Product Core.

Documentation Strategy​

This knowledge hub is now organized to avoid copy-pasting the same docs for every edition:

  1. Shared foundation docs explain the Mavaro and Behavioral OS layer once.
  2. Shared core docs explain HBK and the edition operating model once.
  3. Edition docs explain tone, audience, and operational differences.
  4. Shared systems docs stay reusable unless an edition needs its own exception.
  5. Legal and compliance docs can stay edition-specific where required.

The goal is one coherent docs system with edition-specific branches, not three near-duplicate sites.