[{"data":1,"prerenderedAt":34},["ShallowReactive",2],{"arch-deep-/architecture/flows/delivery":3},{"id":4,"title":5,"body":6,"category":23,"deepPage":24,"description":25,"extension":26,"layer":27,"meta":28,"navigation":29,"path":24,"relatedFlows":30,"replaces":30,"seo":31,"stem":32,"__hash__":33},"architecture/architecture/flows/delivery.md","Delivery flow",{"type":7,"value":8,"toc":19},"minimark",[9,13,16],[10,11,12],"p",{},"The delivery flow handles every parcel, food order, grocery, and goods movement that arrives for a resident. It is the most-frequent guest-style interaction in the building and the one that tends to fail loudest when it is unmanaged — packages stack at the front desk, residents miss handoffs, and recovery costs scale with volume.",[10,14,15],{},"A courier arrives with a delivery code or a known integration with a logistics partner. The access orchestration engine evaluates the credential and grants scoped entry — typically to the lobby and the parcel storage area, never to resident floors. The handoff is acknowledged: by a staff member, by an automated parcel locker, or by a resident who has chosen direct-to-door under their unit's permission policy. The acknowledgement is logged against the behavioral specification.",[10,17,18],{},"The resident is notified through their preferred channel within the response-time window specified by the standard. If retrieval does not occur within a defined period, the issue engine raises a follow-up. Edge cases — wrong unit, refused delivery, damaged parcel — are routed to staff with the context they need to resolve without contacting the resident a second time.",{"title":20,"searchDepth":21,"depth":21,"links":22},"",2,[],"flow","/architecture/flows/delivery","How parcels and goods reach residents — courier arrival, scoped access, handoff, acknowledgement, retrieval.","md","2",{},true,null,{"title":5,"description":25},"architecture/flows/delivery","0XtV3uOn1HYt2TXWlew5UnRHDEBmw02-R1omDJCcAMM",1779718756836]