Phase 1 · HTML Everything · Output 01

Complete HTML Authority Set

The whole visible application must be designed before React Fidelity and before later data/schema/storage work. Output 01 therefore covers not only Phase 0 destinations, but the complete application envelope: platform front door, app entry, shells, cross-app switching, global utilities, administration, integrations, operational surfaces, identity/security, support, and every necessary deep/detail/workflow surface.

Phase 1Active · Inventory in ProgressOutput 01 of 06
Hard rule. Every bounded application must be checked against the whole-envelope inventory independently. “The platform has it” does not prove Household Ledger or Grocery has all application-level surfaces it requires.

A · Whole Visible Application Envelope

Required completeness sweep for each bounded app
  • Platform / Application Family Front
  • Application Entry
  • Home / Dashboard / Command Center
  • Primary domain pages
  • Detail / workflow / intake / edit pages
  • Desktop Shell
  • Phone Shell
  • Cross-App Return / Switching
  • Global Utilities
  • Settings / Preferences
  • Administration / Governance
  • Integrations / Connections
  • Import / Export / Migration
  • Operations / Status / Logs / Queues
  • Identity / Security / Permissions
  • Help / Onboarding / Guidance
  • History / Activity where applicable
  • Meaningful empty / error / loading / restricted / destructive states
Global Utilities are application chrome, not ordinary workflow pages: Search, Quick Add, Command Palette, Notifications/Attention, Profile/Account, Household/Workspace selector, Sign-out, and App Switcher.

B · Platform / Application Family

Front door and cross-app architecture

Application-Family Front / Launcher

Front / Tile PageThe visual surface from which Household Ledger and Grocery are entered.
Not started
App tiles / entry choices
Not started

Cross-App Switching / Return

Return to platform/family
Not started
Switch to another app
Not started
Global vs app-specific chromeEstablish what remains visible and what changes across app boundaries.
Inventory
Context continuityHousehold/person/workspace context that visibly follows the user.
Inventory

C · Household Ledger Application-Level Authority

Everything around the ten destinations

Application Entry

Brand transition, context, household/person selection where used, and initial destination treatment.

Not started

Desktop Shell

Brand, primary/local navigation, active state, page hierarchy, top bar, utilities, breadcrumbs where applicable.

Not started

Phone Shell

Mobile header, complete destination access, open/closed navigation, back/context behavior, mobile-safe actions.

Not started

Global Utilities

  • Global Search
  • Quick Add
  • Command Palette
  • Notifications / Attention
  • Profile / Account
  • Household / Workspace selector
  • Sign-out
  • App Switcher
Inventory

Household Administration / Governance

Administrative home plus materially distinct household/app management surfaces.

Not started

Integrations / Connections

Connections home plus connection setup, detail, disconnected, failed, and reconnect states where materially distinct.

Not started

Import / Export / Migration

Import, export, migration, preview/review, progress, completion, and failure surfaces where applicable.

Inventory

Operations / Observability

Job status, sync status, queues, processing, activity logs, diagnostics, retries, failures, and operational attention surfaces where used.

Inventory

Identity / Security / Permissions

Account/security treatment, roles/permissions, restricted/unauthorized surfaces, and security-relevant confirmations where applicable.

Inventory

Help / Onboarding / Guidance

First-use onboarding, contextual explanation, setup guidance, and help surfaces where intentionally part of the product.

Inventory

Settings / Preferences

Application and user preferences plus materially distinct subordinate settings.

Inventory

History / Activity

Application-level chronology/activity where it is materially visible and not owned by a domain destination.

Inventory

D · Household Ledger Product Destinations

10 accepted Phase 0 destinations
Household

Overview

Primary authority + necessary deep/detail/workflow inventory.

Daily Command

Primary authority + necessary deep/detail/workflow inventory.

Communications

Primary authority + necessary deep/detail/workflow inventory.

Vision

Primary authority + necessary deep/detail/workflow inventory.

Core

Records

Primary · list/search/filter · record detail · create/intake · edit/configure · other material workflows.

Cash Flow

Primary + necessary deep/detail/workflow surfaces.

Matters

Primary + matter/detail/intake/workflow surfaces.

Assets

Primary · asset detail · create/edit · materially distinct asset workflows.

Accounts

Primary · account detail · create/edit/configure · materially distinct account workflows.

Binder

Primary · evidence/detail · intake/capture · materially distinct binder workflows.

E · Grocery Whole-Envelope Check

Independent bounded-app review

Application Entry

Grocery branding/context transition and initial Home treatment.

Not started

Desktop + Phone Shells

Five persistent destinations, Settings utility, complete mobile access, app-family return.

Not started

Global / App Utilities

Search, quick actions, notifications, profile/context, app switcher only where Grocery requires them.

Inventory

Settings / Administration

Grocery settings plus any app-specific administrative/governance surfaces that materially exist.

Inventory

Integrations / Import / Export

Grocery-specific connections, import/export, migration, or intake surfaces where applicable.

Inventory

Operations / Status / Logs

Sync, processing, imports, queues, failures, retries, or diagnostics where Grocery exposes them.

Inventory

F · Grocery Product Destinations

5 persistent destinations + Settings utility

Home

Primary/default landing + necessary deep/workflow surfaces.

Inventory

Primary · Staples · House Check · item detail · create/edit · other material workflows.

Shop

Primary · shopping preparation/list · Shopping Mode · closeout/reconciliation/history.

Meals

Primary · meal planning · leftovers · other material workflows.

Recipes

Primary · Cookbooks · recipe detail · intake/create/edit · cooking mode.

Settings

Utility authority, not a sixth persistent destination.

Output 01 Close Gate

Nothing visible may be left for React or data work to invent
  • Application-family front / launcher accepted.
  • Application-entry treatment accepted for each bounded app.
  • Desktop and phone shells accepted for each bounded app.
  • Cross-app return/switching and context continuity accepted.
  • Global utility envelope fully inventoried and accepted where used.
  • Settings, Administration/Governance, and Integrations accepted where required.
  • Import/Export/Migration authority exists where applicable.
  • Operations/Status/Logs/Queues authority exists where applicable.
  • Identity/Security/Permissions authority exists where applicable.
  • Help/Onboarding/Guidance and History/Activity are covered where applicable.
  • Every Phase 0 destination has accepted primary HTML authority.
  • Every necessary detail/intake/edit/workflow pattern has accepted authority.
  • Meaningful empty/error/loading/unavailable/restricted/destructive states are represented.
  • Every accepted authority has an exact repository path.
  • Historical/reference artifacts remain distinguishable from fresh Phase 1 authority.
  • Owner accepts the complete HTML authority set.