aesthova / ārk-engine
Built by Aesthova Private Limited · DPIIT-recognised · Startup Odisha-recognised · incubated at IIT Bhubaneswar
The problem
A citation to a verse of scripture is usually a page number in one printer's edition of one translation. Move to a different edition and the citation breaks. Quote the verse online and there is nowhere stable to point. The commentary around a text — centuries of named ācāryas reading the same verse differently — has no shared address at all.
Academic publishing solved this for papers with the DOI. Ārk solves it for śāstra.
What Ārk does
Every node in the corpus — a verse, a sūtra, a passage of commentary — receives a permanent URN. It is a name rather than a location: it says which work, which verse, which layer and whose, and it says nothing about where any of that is kept. So it does not change when an edition goes out of print, when a translation is superseded, or when the platform serving it is rebuilt — and it does not stop meaning anything when a server does. Citing a verse and citing a specific commentator's reading of that verse become the same well-formed action, resolvable by anyone, indefinitely.
Registry precedent
The closest working analogue is Crossref: a nonprofit registry that turned scholarly citation into permanent, resolvable infrastructure, now serving over 24,000 members. Ārk applies the same discipline — reserve the namespace, prove resolver stability, then open it to registration — to a corpus that has never had one.
Surfaces
Register
Ārk is built and written as a precision instrument, not a devotional or wellness product. The comparison the team uses internally is closer to a flight-instrument panel or a well-made lens than to a spiritual app: exact, restrained, and never the subject of its own sentence. Every doctrinal claim on the platform carries a named source — the platform itself asserts nothing.
What this page intentionally leaves out
This is a working project with active architecture, funding conversations, and a build roadmap in motion. What follows is named but not detailed here — ask directly if you need more.
- The corpus data model and how a node's layers are structured internally
- The URN namespace scheme and resolver mechanics
- Build sequence, milestones, and current implementation status
- Revenue architecture and funding sources
- The editorial and voice rules enforced at build time
Corporate structure
| Parent | Āroha Omnis Corp (under formation) |
|---|---|
| Operating entity | Aesthova Private Limited — Bhāratīya branch |
| Product | Sector Ārk — Ārk Engine |
| Publishing imprint | Folio Veda |
| Scope | Śrī Brahma-Mādhva-Gauḍīya Sampradāya corpus only |
Get in touch
For partnership, grant, or press inquiries, reach the team directly rather than through this page. Contact.