<commit_before>* project title
* one sentence description
* paragraph description
* one or more floor plans to show the key elements and how they interact
* 2 collages or renderings to illustrate key moments in the experience
* diagram of how your objects will connect
* images of each of the objects you will use showing how you plan to integrate the Raspberry Pi, Arduino, sensors, actuators, wiring and any other technical elements (can be custom drawings, collages with photos from the internet, or whatever best describes the object and how you will wire it up)
* one or two images or videos from 2-3 reference projects that you are drawing inspiration from
* inventory of parts (a simple list in text is fine)
<commit_msg>first pass of edits / scenario 1<commit_after>---
layout: base
style: lecture
title: Site to Site | Presentation
menu: project
project: object-oriented-office
---
## Object-Oriented Office (OOO)

### Collaborative Intelligence.

![OOO - Network of Objects](https://github.com/site2site/object-oriented-office/blob/master/docs/images/ooo_network-01.png)

True innovation in architecture arises not from the hours spent hunched over a desk, but rather in the moments of shared respite -- the smoke breaks, coffee runs, and shared distractions we relish to reconnect and retain our sanity.

![Cigarettes, Coffee, and Cats](https://github.com/site2site/object-oriented-office/blob/master/docs/images/distractions-01.png)

This is nothing new to architecture -- office design has been slowly moving away from the language of corner offices and the cubicles to foster spaces of chance encounters and impromptu social gatherings. Similarly, the software and tools we use to generate our work has also seen a shift to the collaborative, moving from the confines of our desks to the cloud, allowing us to work in new ways and across physical divides.

Despite these advances, space making and software are not a complete panacea. Situated in the space between the software and the architecture are a milieu of objects we interact with everyday that aren’t capitalizing on their latent potential. By embedding the everyday furniture and appliances with inexpensive technology, we can turn these “dumb objects” of the office into an ad-hoc network of intelligence, capable of interpreting, translating, and responding to our habits into even more opportunities for collaboration.


## Scenario 1: Unoccupied Opportunities

*	![Chair_rendering1](http://google.com/)

### The chair is the common platform of the office, a fairly pedestrian object designed for ergonomics, but an untapped resource.

A "smart" chair becomes an object for gathering information about it’s occupants behavior and conduit for physical communication. The way we sit conveys a lot about our actions, whether we are leaning in and focused on our work, hunched over in a power nap, or leaning back to take a mental break. Embedded sensors detect heat, motion, and orientation, helping us focus when we are in the zone, and--with the assistance of integrated actuators--subtly directing us to productive opportunities for collaboration when we are in need of distraction.

*	![Chair_sleeper](https://github.com/site2site/object-oriented-office/blob/master/docs/images/seat_activity-01.png)
*	![Chair_worker](https://github.com/site2site/object-oriented-office/blob/master/docs/images/seat_activity-02.png)
*	![Chair_daydreamer](https://github.com/site2site/object-oriented-office/blob/master/docs/images/seat_activity-03.png)

RFID sensors allow our furniture to know who we are (name tags for the digital realm), in addition to what we are doing, and, when employed in appliances of social gathering (like the coffee pot), can remotely inform and direct us to potential opportunities for collaborative socialization. Remote access to the cloud also allows for personalization, providing the smart chair with data to make intelligent suggestions, tailoring its recommendations for interaction to our mood, social desires, and personal interests.

*	![Chair_floorPlan](https://github.com/site2site/object-oriented-office/blob/master/docs/images/92113_studioxplan1-01.png)

*	![Chair_rendering2](http://google.com/)

###Component Elements
*	![Chair_components](http://google.com/)

###Reference
*	__![Braincoat - HumanInput](https://github-camo.global.ssl.fastly.net/8efef98c183286c846ec2953829bfc13def51714/687474703a2f2f6473726e792e636f6d2f70726f6a656374732f426c7572427261696e636f61742f30382d76697375616c2d636f6d6d756e69636174696f6e732d636f2e6a7067)__
*	__![Braincoat - Interaction](https://github-camo.global.ssl.fastly.net/ccff3d5ac3c230585521aa9bfde44ce289fd6167/687474703a2f2f6473726e792e636f6d2f70726f6a656374732f426c7572427261696e636f61742f31382d2d7472616e736d697373696f6e2d7a6f6e65732d636f70792e6a7067)__
*	__![RefProject2](http://google.com)__
*	__![RefProject2](http://google.com)__

## Scenario 2: Cross-Office Feeds

### Scenario description goes here...

*	![Image1](http://google.com/)
*	![Image2](http://google.com/)
*	![Image3](http://google.com/)
{'fraction_non_alphanumeric': 0.07483666600673133, 'fraction_numerical': 0.06176994654523857, 'mean_word_length': 5.460358056265985, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 8, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2433504', 'n_tokens_mistral': 1608, 'n_tokens_neox': 1395, 'n_words': 554}