> For the complete documentation index, see [llms.txt](https://docs.aohwv.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aohwv.dev/core-concepts/philosophy.md).

# Philosophy

AOH Sync's behavior follows from a small set of principles about where truth lives, who decides, and what happens on failure.

## 1. One canonical picture of each person

A person appears in many systems (HR, payroll, Entra, shared mailboxes). AOH Sync collapses those into a single **identity** and keeps every linked record attached to it. See [The identity graph](/core-concepts/the-identity-graph.md).

## 2. Backend-authoritative access

Every permission decision is made on the server, on every request. The UI reflects what the backend permits; it never grants access. When the two disagree, the backend wins, so a revoked permission takes effect immediately. See [Access control](/core-concepts/access-control.md).

## 3. One source of truth, one writer

Each kind of data has exactly one component that writes it. Identity records, secrets, audit entries, and posture scores each have a single owner. Everything else reads from that owner, so there is always a clear answer to "where did this value come from?"

## 4. Long work happens in the background

Full syncs and provisioning runs run asynchronously. The UI returns immediately and you poll for status; the work is queued, not skipped.

## 5. Everything that changes state is recorded

Every mutating action is written to the audit trail with who did it, what changed, and which compliance frameworks care. See [Audit and compliance](/core-concepts/audit-and-compliance.md).

## 6. Risk is measured, not guessed

Anything flagged as risky comes from a defined calculation, not a heuristic. Orphan risk and posture are scored from explicit inputs. See [Orphans and risk scoring](/core-concepts/orphans.md) and [Posture and anomalies](/core-concepts/posture-and-anomalies.md).


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.aohwv.dev/core-concepts/philosophy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.