Skip to content

Lane MNT: Maintenance Calls agent and work queue #32

Description

@caosos

Parent: #25

Ownership

Maintenance Calls only.

Build

  • resident maintenance call intake
  • acknowledge -> start -> blocked/parts/vendor -> complete lifecycle
  • resident-visible status
  • Grand Central maintenance.call.* events
  • bridge into existing maintenance/work-order concepts without duplicate records

Required tests

  • same open issue re-request increments attention instead of duplicating
  • two different maintenance issues in same room remain distinct
  • category-only dedupe is prohibited
  • event replay is idempotent
  • resident/room isolation
  • completion/status is reflected consistently to staff, room profile, and Aria

Acceptance

Maintenance Calls operate as their own live queue in the simulated building and preserve issue identity correctly.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions