> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/policies/policies/internal-policies/workplace-safety-policy.md).

# Workplace Safety Policy

## Company Structure

Nested Knowledge is a remote software company with a web-based software for use in medical research. Nested Knowledge has fewer than forty employees and contractors. All work is completed remotely except for sales activities at sales conferences.

**Scope:** This policy applies to employees and contractors of Nested Knowledge.

## Remote Work

Occupational hazards associated with remote work may include, but are not limited to:

* Vision strain
* Tendinitis
* Repetitive strain (e.g. carpal tunnel)
* Back and postural issues

### Sales Conferences

Occupational hazards associated with sales conferences may include, but are not limited to:

* Dehydration and overheating
* Vehicle safety
* Pedestrian safety

### Preventative Measures

Remote workers can take steps to prevent health issues from work, such as:

* Get up and move often
* Set monitor to eye level to avoid neck and eye strain
* Choose the right chair, where knees are not higher than your hips.
* Clear the floor of obstacles
* Inspect eletrical cords and extension cords. Unplug any cord that is overheating.
* Keep a fire extinguisher nearby.

Workers facing physical health ailments related to excessive screen use should consult a medical professional. Nested Knowledge always allows personnel to take a break from their screen when necessary. Personnel are encouraged to take walks, get sunlight, stretch, and stand. Nested Knowledge does not and will not use eye-tracking or other employee monitoring programs.

Sales professionals attending in-person event can take preventative measures such as:

* Staying hydrated and taking steps to avoid overheating in crowded venues.
* Avoiding driving in life-threatening settings, such as driving in severe weather or driving under the influence.
* Remain vigilant of unsafe drivers when walking.

### Incident Tracking

Nested Knowledge Tracks Workplace Safety Incidents in centralized spreadsheet. No incidents have occurred as of December 2025.

## Enforcement

Due to the low risk of physical and occupational harm, Nested Knowledge does not currently require employees to complete workplace safety training. Our policies are distributed to employees and evailable for review at any time.

## Revision History

| Author     | Date of Revision/Review | Comments                         |
| ---------- | ----------------------- | -------------------------------- |
| K. Cowie   | 12/16/2025              | Revised                          |
| K. Cowie   | 01/24/2024              | Revised to add incident tracking |
| K. Kallmes | 12/22/2023              | Approved                         |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nested-knowledge.com/policies/policies/internal-policies/workplace-safety-policy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.