Partner network: network home and order hand-off
Step 6 of the round-2 walkthrough (scenario S4). Everyone has answered: Kimball shared bottled water and tarps, and Salvation Army joined. The last steps follow Salvation Army from a shared resource into the existing cart.
Partner Networks Hurricane Odalys — Gulf Coast
Hurricane Odalys — Gulf Coast
Shared resources
Resources members have chosen to share with this network.
Bottled water
LiveTarps
LiveMembers’ needs
Existing open needs posted by organizations in this network. These needs are also visible to other signed-in GIK organizations.
Bottled water for Gulf Coast shelters
OpenMedium urgencyMembers
Network admin
Joined organizations
Invitations
Partner Networks Hurricane Odalys — Gulf Coast
Hurricane Odalys — Gulf Coast
Shared resources
Resources members have chosen to share with this network.
Bottled water
LiveTarps
LiveMembers’ needs
Existing open needs posted by organizations in this network. These needs are also visible to other signed-in GIK organizations.
Bottled water for Gulf Coast shelters
OpenMedium urgencyMembers
Network admin
Joined organizations
Partner Networks Hurricane Odalys — Gulf Coast Bottled water
Bottled water
24 × 500 mL bottles per case
Available
100 Cases
From
Kimball Household Goods · Mobile, AL
Cart
CART
One checkout per supplier, as today.
Kimball Household Goods
From here, the existing checkout
This walkthrough stops at the hand-off. What it shows is the proposed network attribution on the cart line: the member can see which network the item came from. The proposal is that checkout, the offer and the order then run through GIK’s existing per-supplier flow. That the network is persisted onto the completed offer and order is an implementation requirement this walkthrough does not show or validate.
- Shown here: the cart line attributed to the network (proposed).
- Not validated here: the network persisted on the offer and the completed order (model R5, network_id on offers and orders; proposed, not built).
- No pricing, payment method, terms or PO number: the first release is in-kind.
- Counting cross-partner orders for the exit criteria depends on that persistence working (D14, T7).
Review notes · 4 · 1 ▲ flagged
First release, item 5: one network page showing members, what is shared, and members’ needs, for every role. The admin sees invitations too.
Working decision D17: members’ existing open needs are listed, filtered by membership; their audience does not change. Network-only needs are Later.
▲ Open (R11): whether the convener counts as a member; the admin is listed apart, with no member count.
Gap, first release item 8: leaving and removing a member (access ends at once) is not drawn in this round. It is a secondary page and does not block the walkthrough.
Review notes · 2
Settled (Q4 roadmap) and first release, item 5: members find what is shared with the network. Resource and need cards here are the member’s view; View opens the existing resource detail.
Before release (T5, model D-c): this page shows network-shared inventory only to members, and the platform enforces it.
Review notes · 2 · 1 ▲ flagged
D18 and first release, item 7: spec section 5’s default (“through the existing flow”) and the decision record agree that members order through the existing offer and cart flow, with the network recorded on the offer or order (section 4 item 7). Not confirmed by GIK, and the roadmap does not mention ordering. Round one left this as a next slice; the repo includes it in the first release, so it is drawn here.
▲ Decision pending (Mike, Shabab): whether the existing resource detail, cart and checkout are reused unchanged, and whether any request or approval step is needed. The detail and cart here are drawn schematically, not as today’s exact screens.
Review notes · 4 · 1 ▲ flagged
What this step shows: proposed network attribution on the cart line only.
Model R5 (implementation requirement, not validated here): offers and orders carry a nullable network_id so the network persists onto the completed order; an order made outside a network has none. Proposed in ERD round 1, not built. This walkthrough stops before checkout and does not show the order.
▲ Decision pending: whether a cart can mix network and public resources, or resources from different networks; where the network appears in cart, confirmation and order detail; and what happens if membership, sharing or availability changes before checkout completes.
Working decision D13: the first release is in-kind; pricing, terms and payments are Later (model round 2).
Review notes · 2 · 1 ▲ flagged
▲ Conflict, D14: how cross-partner orders and active networks are counted. Spec section 5 has no default; the decision record adopts the PRD’s targets. Not shown on any screen.
Not in this round (secondary): leave and remove, a standing-network alternative for D1, email onboarding for D12, and closing a network.
How to read the review notes
- Settled: the signed Q4 roadmap’s text, the only source here GIK has agreed to.
- First release: in Augusto’s proposed first release (spec section 4). GIK has not agreed to it.
- Working decision: answered internally in the 2026-10-07 decision interview with Mike Perry. Not confirmed by GIK; a model that implements it is not approval.
- ▲ Decision pending: still open, with GIK (Shabab, George) or with engineering (Mike).
- ▲ Conflict: repo sources disagree. The note says what is drawn and why; nothing is resolved here.
- Model: ERD round 1 and the ontology’s networks module, proposed and not built. Gap: in the repo, not drawn yet.
Illustrative organizations and records, in-memory state; nothing is sent, saved or shared. Reloading resets the page.