[{"data":1,"prerenderedAt":68},["ShallowReactive",2],{"arch-deep-/architecture/flows/issue":3},{"id":4,"title":5,"body":6,"category":57,"deepPage":58,"description":59,"extension":60,"layer":61,"meta":62,"navigation":63,"path":58,"relatedFlows":64,"replaces":64,"seo":65,"stem":66,"__hash__":67},"architecture/architecture/flows/issue.md","Issue flow",{"type":7,"value":8,"toc":53},"minimark",[9,13,20,26,32,38,44,50],[10,11,12],"p",{},"The issue flow handles every maintenance, service, or operational request raised in the building — by a resident, by staff, by a sensor, or by an automated check.",[10,14,15,19],{},[16,17,18],"strong",{},"Submit."," A resident describes a problem in the app, with optional photos, location, and unit context. Staff submit through the operations console with category and priority pre-filled. Sensor-driven submissions arrive from the IoT layer with structured payloads.",[10,21,22,25],{},[16,23,24],{},"Categorize."," The issue engine assigns a domain (Access, Deliveries, Spaces, Support, Lifecycle, Environment) and a severity tier. Categorization combines text classification, the building's domain taxonomy, and explicit overrides where staff intervention is appropriate.",[10,27,28,31],{},[16,29,30],{},"Route."," Each category resolves to one or more responders — on-site staff, contracted vendors, or automated subsystems. The routing engine attaches an SLA based on category and severity, and identifies escalation paths for missed SLAs.",[10,33,34,37],{},[16,35,36],{},"Resolve."," The responder works the issue with state visibility (acknowledged → in-progress → awaiting parts → resolved). Parts, vendor coordination, and elapsed time are tracked alongside the work order. Multi-step resolutions hand off cleanly between teams.",[10,39,40,43],{},[16,41,42],{},"Close."," Completion criteria are explicit per category. A closed issue includes the work performed, the time spent, and any parts consumed. Resident-facing closure messages fire through the notification engine with the building's tone.",[10,45,46,49],{},[16,47,48],{},"Feedback."," A short survey fires after closure — typically one or two questions calibrated to the issue type. The signal feeds Layer 6 in two places: the building's own scoring (trust index, friction minutes, promise-kept rate) and the cross-building intelligence corpus that informs the next version of the behavioral specification.",[10,51,52],{},"The flow is the same whether the issue is a broken bulb or a major HVAC failure. The difference shows up in the SLA, the routing, and the tone — not in the workflow shape.",{"title":54,"searchDepth":55,"depth":55,"links":56},"",2,[],"flow","/architecture/flows/issue","Maintenance and service requests, end to end.","md","2",{},true,null,{"title":5,"description":59},"architecture/flows/issue","ApgZ82r7OaAgNgNmSI0KemnDOj31WO1YJ2Zr5KABdsE",1779718756836]