Data Definition Document: Operations Services

Domain: Operations (maintenance, security, personnel, services) Logical Sub-Domain: Services (Support Functions) Physical Packages: @sd/mod-operations/procurement, hospitality, telemetry Related Documents: Process Blueprint Context: This document defines the Data Structures for Supply Chain and Guest Services. Source: packages/modules/operations/src/{procurement,hospitality,telemetry}/schema.ts

0. Entity Relationship Diagram (ERD)

erDiagram
    VENDOR ||--o{ PURCHASE_ORDER : "receives"
    RFP ||--o{ BID : "solicits"
    RFP ||--|| PROPOSAL : "triggers_vote"

    AMENITY ||--o{ BOOKING : "reserved_via"
    ASSET ||--o{ TELEMETRY : "emits"

    VENDOR {
        string id PK
        enum compliance "verified, pending"
        string[] services
    }

    PURCHASE_ORDER {
        string id PK
        float totalAmount
        enum status "draft, approved"
        json[] lineItems
    }

1. Primary Entities

Entity: Vendor

A service provider partner.

Field	Type	Required	Description
id	string	Yes	Unique ID.
legalName	string	Yes	Official Name.
classification	string	Yes	hoa_contracted vs owner_hired.
complianceStatus	string	Yes	verified (Insurance OK), pending.
services	string[]	Yes	Tags (plumbing, security).

Entity: PurchaseOrder (PO)

A formal commitment to spend.

Field	Type	Required	Description
vendorId	string	Yes	Supplier.
totalAmount	number	Yes	Value.
status	string	Yes	submitted, approved, fulfilled.
items	object[]	Yes	Line item details.

Entity: AmenityBooking

Reservation of common areas.

Field	Type	Required	Description
amenityId	string	Yes	The Space.
userId	string	Yes	The Resident.
startTime	Timestamp	Yes	Start.
endTime	Timestamp	Yes	End.

Entity: TelemetryReading

IoT Data Point.

Field	Type	Required	Description
assetId	string	Yes	Source Device.
pointId	string	Yes	Sensor (e.g. temp).
value	any	Yes	Measurement.

4. Changelog

Date	Author	Description	Reference
2026-01-24	Antigravity	Initial creation	Implementation Plan