GAP Stores as Network repeaters where data is composed of shirts, jeans and belts

Nodes or Points of Change: GAP stores as Network Repeaters

In a network, repeaters regenerate signals. They're needed in many networks because data transmissions can only span a limited distance before signal quality degrades. Repeaters are used to extend the distance over which data travels. I wanted to create a system where Gap Stores were the original data source and the repeating modules in the system. The data was to be a shirt, jeans and belt.

The Plan/Transport:

• Follow the google maps list of the 7 GAP stores on the path between ITP and my apartment.
• 
• Buy an outfit at the GAP closest to ITP (Astor place).
• Stop in every GAP between the Astor Place GAP and the GAP across the street from my apartment in Chelsea.
• During every stop, the outfit in possession will be returned and a new one, hopefully identical to the one returned, will be bought to replace it. A set of rules on how to deal with lack of identical replacement data will be followed (see rules/protocol below).
• The data will be transported by gap bags. The contents of the data are passed from one node to another when a return and then a purchase is made.

Addresses:

Each node in the network is addressed via US postal service address and then secondarily by the order in which I arrive at the location.

The Rules/Protocol:

• If the cost of the item is more that what you paid you at the previous store, you may not buy it. (no added resources). You may pay less for it (if it's on sale), but these costs won't be recovered into the system.
• Each item of clothing acts as it's own packet. If, at the 2nd store, the jeans are on sale, but the shirt cost more, you may not buy the shirt with the savings from the jeans.
• If there is a twin item (identical cut, size, and color) to what you returned at the current store at the same price or less than what you previously paid, buy it.
• If the twin item is not available but there is one with the only difference being color, buy one in the color closest to the immediate previous color. (size and cut are more important to the data's fitness than color)
• If the twin item is not available in a different color, buy one 1-size larger (lose data's definition)
• If the twin item is not available in a larger size, trying finding an item with a similar cut. (Probably really far off)
• Once you've switch one attribute value, you may not switch back to it unless the cut of the item has changed. For example, if I have a blue type- z shirt, then a green type-z shirt, I cannot have a blue type- z shirt again. (this would restore data that wouldn't randomly happen)
• If there are no replacement items meet any of the above criteria, stop shopping for that item (drop the packet)
• Don't ask for help or if there are clothing in the store room.
• Don't spend more the 15 minutes looking for items. If you haven't found identical items at this time, begin looking for replacements as written above.

The Predictions:

1) Data Fidelity - The shirt will stay the same, or will maybe go up in size. I plan on choosing a very simple t-shirt that should potentially be in stock in all gaps. The jeans will change a lot. I wear a very common pant size and it's often sold out at stores. Also Gap carries lots of different kinds of jeans so it may be hard to find in the store even if it's there. The belt will also change a lot. Every time I've been to a Gap, they seem short on belts.

2) Network Congestion - this will be reflective of the larger congestion in NYC. If I go to the stores at peak times, the network will slow down. I plan to go after rush hour to keep the flow going.

3) It's possible for some content never to reach its destination, although it's far more likely that an item bearing low resemblance to the original will be in its stead vs. losing the packets.

Realty/outcome:

google did not give an accurate listing of gap stores here's what i found of the original 7 on the sheet:

1- 1 Astor Place	2. 66 3rd Avenue	3 - 23rd 8th Avenue	4- 91 7th Avenue (didn't exist)	5- 625 Ave of Americas	6 - 675 Ave of Americans	7 - 258 8th Ave
the Astor place gap	an empty lot

After wasting 3 hours, I configured a new path:

gap outfit 1	gap outfit 2	gap outfit 3	gap outfit 4	gap outfit 5

Shirt Story

shirt 1	shirt 2	shirt 3	shirt 4	shirt 5
flutter twisted scoop, black, small $24.50	flutter twisted scoop, black, small $12.25	SS, Raw Cut open, red, small $9.99	LBO sleeve, blue, small $9.99	LBO sleeve, green, small $9.99

Jeans Story

Jeans 1	Jeans 2	Jeans 3	Jeans 4	Jeans 5
Flare "long and lean" stretch, size 6R, wash 4 (darkest) $58	Flare"long and lean" stretch, size 6R, wash 1 (lightest) $58	Flare"long and lean" stretch, size 8R, wash 1 (lightest) $58	Flare"long and lean" stretch, size 8R, wash 2 $49.50	Flare"long and lean" stretch, size 10R, wash 2 $49.50

Belt Story

belt 1	belt 2	belt 3	belt 4	belt 5
Grommet Belt, Medium, Brown $22.12	Leather braided, Medium, Brown $22.12	Classic round, Medium, Brown $18.37	Classic round, Medium, Brown $18.37	Classic round, Medium, Brown $18.37

Outcome:

• outfit (data) degraded much more radically and quickly than i anticipated.
• cost differences (a sale priced item at one gap, not at another) caused way more damage to the system, as i designed it, than i anticipated. I thought that all gaps would be on one page regarding sales. This is the way it's supposed to be, but it seems that cashiers control some of this.

What I would change if reimplementing system:

keep it simpler. Might be easier to see changes if i just used one element, either a shirt, pants, or belt rather than all three.