> For the complete documentation index, see [llms.txt](https://developer.sahamati.org.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.sahamati.org.in/sahamatinet-agent-sna/why-sna.md).

# Why SNA?

Sahamati evaluated two options for how AAs should report SLA metrics. The following comparison, agreed upon with the AA community, guided the decision to build and distribute SNA:

| Option 1: AA Gathers & Reports Independently          | Option 2: AA Uses SNA (Recommended)              |
| ----------------------------------------------------- | ------------------------------------------------ |
| ✔ AA-controlled changes                               | ✔ Uniform interpretation across all AAs          |
| ✘ Interpretations may vary across AAs                 | ✔ Minimal integration effort for AAs             |
| ✘ Each AA must implement all reporting logic          | ✔ Future changes: redeploy SNA, no code changes  |
| ✘ Future schema changes require AA engineering effort | \~ AAs maintain one additional cluster component |

The SNA approach ensures that Sahamati can centrally update calculation logic, definitions, schema, and all AAs benefit immediately by simply deploying the new version of SNA.

This leads to:

* Faster ecosystem-level consistency
* Lower engineering burden on individual AAs.


---

# 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://developer.sahamati.org.in/sahamatinet-agent-sna/why-sna.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.