> For the complete documentation index, see [llms.txt](https://www.umwelten.xyz/dwelling/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.umwelten.xyz/dwelling/approach/communities.md).

# communities

![Image source: http://www.daninolab.nyc/microuniverse](/files/EvHNvkcZjAPyAU0skdvi)

## colleagues

### collaborators, internal 

We’d like our teams to be inclusive and diverse.

<details>

<summary>current</summary>

* [Ishan Shah <img src="/files/nAPzIZg1R0p1hSnMiz7G" alt="" data-size="line">](https://www.linkedin.com/in/ishan-shah-64b72b11a/)
* [Trivik R. Bhavnani <img src="/files/nAPzIZg1R0p1hSnMiz7G" alt="" data-size="line">](https://www.linkedin.com/in/trivik-bhavnani/)

</details>

<details>

<summary><del>desperately</del> seeking </summary>

**Firmware Engineer**

*Us:* Compossible Umwelten Pvt. Ltd. was founded in 2017. We’re currently working on unproven devices to non-invasively interface with human and dog brains through haptic means.&#x20;

*You:* Other than being conscientious and having a sense of what elegant and maintainable code is we hope you’ll have done some of the following:

* Developed firmware and systems using (1) C / C++, (2) an RTOS preferably Zephyr (3) the RP2040 (4) Raspberry Pi’s Compute Module 4 (5) Wi-Fi and BLE stacks (6) I2C, SPI, UART and USB buses.
* Have gone through prototype to production firmware cycle for a product with version control systems, project management tools and documentation.
* Contributed to open-source projects and have geeked out over signal processing.

*What:* You’d be building our codebase (and corresponding documentation) from the ground up and contributing to / reviewing our hardware. As the initial seed you’d be creating your own structure.

*Where:* You’ll be seated at our Nariman Point (Bombay) office along with a hardware and mechanical engineer. Should we still exist in 2023 we expect to add application engineers. While we hope to have a few billion users at no point do we expect to become a large company.

</details>

{% file src="/files/2tFkwRjABkVP5ZFIwJlq" %}
we're happy to be flexible, just our current
{% endfile %}

### collaborators, external&#x20;

It's a privilege to have opportunities to engage with suppliers and consultants whom allow us to be.&#x20;

<details>

<summary>current</summary>

* [Jesal Mehta](https://www.jesalmehta.com/)
* [Naomi Rohilla](https://www.pneume.in/)

</details>

### craftspeople&#x20;

Shop floor conditions (safety, remuneration, skilling, time...) is something we play close attention to. Direct and indirect.

## clusters

### hardware tinkerers

* mechanics (maintenance)
* hobbyists (users)
* researchers (academics)
* developers&#x20;

### developers (of application software | modes)

### content creators (studios)

## consumers (end users)

## investors (cryptoTokens)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://www.umwelten.xyz/dwelling/approach/communities.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.