[{"data":1,"prerenderedAt":66},["ShallowReactive",2],{"arch-deep-/architecture/engines/issue-engine":3},{"id":4,"title":5,"body":6,"category":51,"deepPage":52,"description":53,"extension":54,"layer":55,"meta":56,"navigation":57,"path":52,"relatedFlows":58,"replaces":60,"seo":63,"stem":64,"__hash__":65},"architecture/architecture/engines/issue-engine.md","Issue engine",{"type":7,"value":8,"toc":47},"minimark",[9,13,20,26,32,38,44],[10,11,12],"p",{},"The issue engine handles every maintenance, service, and operational request in the building. From a leaking faucet to a request for a replacement key fob to a noise complaint about a neighbor — the engine assigns each event a category, a priority, an owner, and a resolution path.",[10,14,15,19],{},[16,17,18],"strong",{},"Categorization."," Submissions arrive with a free-text description and optional photos. The engine classifies the request against the building's domain taxonomy (Access, Deliveries, Spaces, Support, Lifecycle, Environment) and assigns severity based on rules tied to safety, habitability, and resident impact.",[10,21,22,25],{},[16,23,24],{},"Routing."," Each category maps to one or more responders — on-site staff, contracted vendors, or third-party services. SLAs are attached at routing time; missed SLAs trigger escalation paths defined in the behavioral specification.",[10,27,28,31],{},[16,29,30],{},"Work tracking."," State transitions (acknowledged → in-progress → awaiting parts → resolved → closed) are versioned and visible to the resident at the right moments. Parts and vendor coordination are tracked alongside the work order so handover between teams is clean.",[10,33,34,37],{},[16,35,36],{},"Resident communication."," The notification engine handles the resident-facing updates. The issue engine produces structured events; tone and timing are decided by the notification rules. The resident sees a coherent thread, not a stream of system messages.",[10,39,40,43],{},[16,41,42],{},"Feedback capture."," A short, contextual survey fires when the work is closed. The signal feeds Layer 6 — both the building's own scoring and the cross-building intelligence corpus.",[10,45,46],{},"The engine replaces tenant-portal ticketing because tenant portals do not understand the building. The issue engine does.",{"title":48,"searchDepth":49,"depth":49,"links":50},"",2,[],"engine","/architecture/engines/issue-engine","Manages maintenance and service requests end to end — categorization, routing, resolution, feedback.","md","4",{},true,[59],"issue",[61,62],"tenant-portal-ticketing","paper-work-orders",{"title":5,"description":53},"architecture/engines/issue-engine","Yea1HgkhNoEI56qsnSKU1F1-KWJXeqQHsMNNOt1bSy0",1779718756836]