KINETIC GAIN · tenant maintenance lane
Property operations + WordPress portal governance
Maintenance packets · vendor escalation · SLA posture
docs CNAME · tenant.kineticgain.com PHP + static Pages bundle

Operator documentation for the tenant maintenance escalation primitive.

This repo exists to prove that Kinetic Gain can ship a WordPress-adjacent property-ops surface that stays buyer-readable, route-clean, and machine-readable at the same time.

Lead recommendation

Service-safe escalation posture
Escalate the water intrusion packet now: vendor acknowledgement, tenant comms, and temporary habitability notes are still split across three systems and the SLA clock is already red.

OverviewMaintenance LaneEscalation QueueService PostureVerificationDocs

Operator summary

tenant promise + vendor accountability
5
Tracked tickets
Emergency, recurring, compliance, and access-device lanes in one surface.
2
Healthy lanes
Aligned to current resident comms, vendor packet, and closure steps.
1
Watch lanes
Need ETA, vendor, or resident-portal repair before the next update cycle.
2
Critical tickets
Unsafe to treat as routine until the full evidence and escalation packet converges.
4
Vendor escalations
Canonical escalation queue across mitigation, HVAC, plumbing, and certification lanes.
Service-safe maintenance escalation
Operator posture
Maintenance treated like an operating system, not just a ticket inbox.

Docs

implementation notes
D-01
primitive

WordPress + property portal evidence surface

The plugin publishes a maintenance snapshot shortcode and REST endpoint so the same packet can surface in both WordPress and the static portfolio proof layer.

D-02
delivery

Static Pages bundle with machine-readable payloads

Prerendered routes, JSON payloads, robots, sitemap, screenshots, and the custom domain all ship together for buyer-readable proof.