Skip to content

[DYN-022] Household and checklist presentation #254

Description

@veryCrunchy

Roadmap

Verified initial scope

The current Chores contract proves a parent-scoped read hierarchy from Team to Chores and Work history. Create, edit, assignment, completion, recurrence, invitation, and scoring writes remain excluded until their exact versioned contracts are verified.

Acceptance criteria

  • Recognize household, member, invitation, checklist, recurring task, assignment, points, and completion-history records from conservative schema and route evidence.
  • Open a useful household overview before secondary invitation, archive, or history resources.
  • Propagate verified parent scope into child chore and work-history reads.
  • Present active, assigned, recurring, overdue, completed, member, points, invitation, and activity states adaptively.
  • Provide invitation-required, no-household, empty, read-only, cached-error, and retry states.
  • Gate every action from verified capability and safe identity context; do not infer unsupported writes.
  • Keep shared composables app-independent and activate the adapter from the verified route graph rather than an app ID.
  • Cover compact phone, large phone, and desktop with synthetic fixtures and visual QA.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:dynamic-appsAdaptive contracts, semantic UI, and app integrationsneeds-designRequires interaction or visual design before completionneeds-protocol-reviewRequires protocol or upstream source verificationplatform:androidAndroid-specific implementation or validationplatform:desktopDesktop-specific implementation or validationpriority:P1Required for the pre-release product experiencetype:featureNew product capability

    Type

    No type

    Projects

    Status
    In Progress

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions