Skip to main content

Current Product Core

This page is the practical bridge between the shared HausFlow docs model and the code in this repository.

The short version:

  • the shared HausFlow philosophy is edition-aware
  • the current codebase is primarily a HausFlow Family implementation
  • roommate support exists in the architecture, but not at full product parity in this repo

Shared Platform Layer​

These parts already exist as shared platform thinking, even when the subject changes by edition:

  • Behavioral OS and HBK
  • edition-aware configuration
  • shared household and member domain types
  • responsibility visibility as the primary product pattern
  • low-friction support, reset, and follow-through language

This is why one knowledge hub can serve multiple editions without cloning the philosophy every time.

Active Core In This Repo​

The strongest implemented feature set in this repository is Family-first and household-centered.

Household tasks​

The app supports assignment, start, completion, approval, and task messaging within a family workflow.

Harmony Flows​

Recurring family flows exist for routines like morning, cleanup, meals, bedtime, weekend, and custom flows.

Parent and kid roles​

The app shell has distinct parent and kid navigation surfaces, which makes role separation part of the current product, not just a docs concept.

Invites and member joining​

Invite-code and token-based joining flows exist for household membership.

Fairness and workload balance​

The backend includes fairness scoring and redistribution planning logic to prevent one person from silently carrying too much.

Proof policy​

Proof requirements and verification settings exist as configurable household logic, with a family-friendly vs roommate-strict framing in the backend model.

Rewards and XP​

The Family implementation includes rewards, XP totals, levels, and celebration loops.

What This Means For The Docs​

The docs should describe three layers clearly:

Shared HausFlow core​

Use shared docs for Behavioral OS, HBK, trust boundaries, and the system logic behind visibility, routines, resets, and support.

Active Family product​

Use Family docs when describing the current app surface in this repository:

  • parents
  • kids
  • chores
  • routines
  • family rewards
  • home rhythm
  • household mental load reduction

Roommate and Professional direction​

Use Roommate and Professional docs to describe the edition model, tone rules, and future branch logic.

Do not present them as fully shipped parity inside this Family repo unless the codebase actually reaches that level.

Current Reality By Edition​

Family​

Family is the active implementation in this repo. It has the clearest product surface and the most complete terminology stack.

Roommate​

Roommate is real at the configuration and domain level here, and some backend language already anticipates roommate use cases. But the full roommate experience belongs in its own branch or repo, not as a claim of equal implementation inside this one.

Professional / White-Label​

Professional and white-label remain future-facing edition strategy. The docs can explain the operating model now, but should not imply a shipped partner platform that does not yet exist.

Documentation Rule Going Forward​

When writing docs for HausFlow:

  1. Keep shared principles in shared docs.
  2. Describe Family features from the actual Family code.
  3. Treat Roommate as edition-aware architecture unless the current repo implements a real roommate surface.
  4. Treat Professional or white-label as future direction unless there is code and policy support to document.

That avoids repeating the SquadUp problem of inheriting a strong docs structure but attaching it to the wrong product core.