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.