Aashray Documentation

This site is the verified single source of truth for how Aashray (SRATRC) works — across the member app, the staff admin panel, and the backend that drives both.

It comes in two matched tracks, plus the method that keeps them accurate:

- :material-book-open-variant: **[Business Logic](business-logic/README.md)** Plain-language rules of the system, for anyone — product, design, or engineering — who needs to understand *what happens and why*, with no code detail. - :material-cog: **[Technical Reference](technical/README.md)** The engineering companion. Every rule is traced to backend code with a `[src: file:line]` anchor. Pairs one-to-one with the business-logic files. - :material-shield-check: **[How these docs are kept accurate](DOCS-METHODOLOGY.md)** The verification-first method behind every page. Read this before editing anything.

The one rule for editing

The backend is the source of truth. Every claim in a technical file must carry a [src: file:line] anchor pointing at the code that proves it, and the plain-language business-logic files are derived from the corrected technical files — never written independently. See the methodology for the full workflow, and run the re-audit script (below) after backend changes.

Keeping it current

When backend code changes, only the pages whose anchors point at the changed files need re-checking. The re-audit script finds them for you:

make reaudit                 # docs whose anchors point at files changed in the last backend commit
make reaudit REF=origin/main # ...changed since a specific ref

See the repository README.md for editing, previewing, and publishing instructions.