Partner network: create

Settled (Q4 roadmap): “A network admin creates an invite-only group tied to an event.”

Working decision D3: any organization admin, nonprofit or supplier, and GIK staff can create a network. The convener here is a nonprofit as an example only.

D16, settled 2026-10-07: the name is Partner Networks, settled in the 2026-10-07 prototype review call (spec v0.5a). The folder and file names now match.

Platform today: the Organizations tab is the existing follow-based directory. Following an organization is not network membership. Discovery and join requests are Later (model round 2).

Settled (Q4 roadmap) and first release, item 1: a network is tied to an event and starts from a disaster-specific template.

▲ Decision pending D1 (Shabab): one network per event that can start from a previous network’s members is the internal working decision and Augusto’s recommendation. The PRD leans toward a standing group, so the alternative is still live.

Working decision (spec D19, “Reuse” in the decision record): reused members are pre-selected as invitees and each accepts again. Model D-a: recorded as created_from_network_id; it seeds invitations, never memberships, and nothing else carries forward.

▲ Conflict, D2 (what counts as an event): spec section 5’s default is “attach to an existing disaster record where one exists, and allow a network without one”. The decision record’s working answer adds “also allow a free-form event”. ERD R1’s event_label and the ontology follow the record, but a model agreeing is not a decision. Drawn so both readings are visible: existing disasters, an Other event name, and the field may be left empty. Unresolved; GIK has confirmed neither. ▲ Open: whether the event is its own record (R9).

D4, what a template pre-fills: spec section 5’s default and the decision record agree on “both”, suggested members and a supply list; neither is confirmed by GIK. ▲ Conflict on types: the spec’s default is “starting with Hurricane” and only notes that the v1 wireframes show four; the record names Hurricane, Wildfire, Coordination and Start Empty as the types. All four are drawn, marked by this conflict.

Pre-fill commits nothing: suggested organizations become invite candidates, not invitations or members. The starter supply list is a planning checklist, kept apart from inventory: it is not a Network Resource Share (model R4), and nothing on it is published or requested. A reused member list is the only thing that carries over from an earlier network. Gap: where the starter supply list appears after creation is not defined; template storage is open (T8, ERD R10).

D11, a network with no supplier: spec section 5’s default and the decision record agree: allow it, with a warning at setup. Not confirmed by GIK. Drawn as information only, shown when there are invite candidates and none is a supplier; it neither blocks creation nor asks for a supplier. Choose Coordination with no previous members to see it.

Working decision D5: five-minute setup is a design target. Nothing here measures it; the v1 page’s running clock is not carried over.

Gap (model R1): a network has a description; no description field is drawn.

Model R2, R11: creating the network makes no memberships. ▲ Open (R11): whether the convener’s organization is a member and how it is counted, so the admin is listed apart from joined organizations.

Next: the convener invites organizations. The invite page assumes the convener reused Hurricane Lala’s members, so two organizations arrive pre-selected.