Skip to main content

Edition Operating Model

HausFlow should be structured as one shared core with multiple operating layers.

The easiest way to think about it is:

  • core layer = shared platform intelligence
  • edition layer = audience-specific behavior

That is similar to a manager/worker setup.

Not in the sense of hierarchy between people, but in the sense of software responsibility separation.

Shared Core as the Manager Layer​

The shared core decides the standards, boundaries, and reusable logic.

This includes:

  • HBK
  • Behavioral OS principles
  • trust and safety standards
  • reusable workflow patterns
  • privacy and governance guardrails
  • shared framework definitions

The core layer should manage what is common.

It should not keep rewriting itself every time a new edition appears.

Editions as Worker Layers​

Each edition takes the shared core and executes it in a different environment.

Family worker layer​

Adapts the core for:

  • parent and kid roles
  • home routines
  • gentle participation
  • invisible household labor
  • support-first coordination

Roommate worker layer​

Adapts the core for:

  • adult equals
  • fairness
  • proof and agreements
  • shared-space operations
  • neutral accountability

Professional / White-Label worker layer​

Adapts the core for:

  • partner branding
  • configurable roles
  • more operational tone
  • edition-aware packaging
  • controlled scope variation

What Stays Centralized​

These should stay in the manager layer unless there is a strong reason to branch:

  • HBK
  • Behavioral OS definitions
  • glossary-level framework logic
  • reset and recovery philosophy
  • no-shame standards
  • governance and trust posture

What Belongs in Worker Layers​

These should branch by edition:

  • tone
  • examples
  • role names
  • handoff language
  • workflow labels
  • policy details where product behavior truly differs

Decision Rule​

When writing or updating docs, ask:

Is this principle-level?​

If yes, keep it in shared core docs.

Is this audience-level?​

If yes, place it in the edition docs.

Is this brand-only?​

If yes, treat it as a surface override, not a full rewrite.

Why This Matters​

Without this separation, HausFlow will keep producing duplicate doc sets with minor wording changes.

With this separation:

  • the philosophy stays coherent
  • editions stay distinct
  • new editions are easier to add
  • the docs stay maintainable

That is the operating model this knowledge hub should follow.