pramāṇaTHE CORPUS PROJECT

ROOTED IN SOURCES. OPEN TO POSSIBILITY.

Every discovery,
a path to
its source.

A growing foundation for exploring Tamil Bhakti, Sanskrit scripture, and the teachings that connect them.

Pramāṇa brings texts, context, and evidence together—so new experiences can grow without losing sight of where their knowledge comes from.

THE IDEA IN ONE SENTENCE

Build the knowledge carefully.
Let people imagine the interfaces.

The long-term goal is a reusable, auditable foundation for readers, researchers, curators, and builders—not a single app or a single way of understanding a tradition.

01 / THE CORPUS TODAY

A growing body of knowledge.
A precise account of its depth.

Pramāṇa 1.0 brings nine components together at their declared maturity. These are different kinds of evidence—not one interchangeable total.

Source-preserved beta12

Tirumurai

The Shaiva textual foundation, including Tevaram, Tiruvacakam, Tirukkovaiyar, and Periya Puranam.

Evidence-graph beta63

Nayanmar saints

68 episodes and 1,763 evidence edges, with literary, edition, and epigraphic authority distinguished.

Curator metadata3,368

Teaching records

Deivathin Kural, Volumes 1–7. Curated summaries and source references, not a redistribution of the source text.

Pramāṇa 1.0 release-candidate coverage
CollectionCoverageWhat that means
Tirumurai 1–7 · TevaramSource-preserved betaProject Madurai source family with IFP/PIFI comparison. The 8,240 running-number convention is retained; it is not a certified count of unique texts.
Tirumurai 8661 + 400 source unitsTiruvacakam and Tirukkovaiyar, with source order and printed-number anomalies preserved.
Tirumurai 9–11301 / 3,046 / 1,419Source units or loci, depending on the edition. Tirumurai 10 explicitly retains the missing locus 851 and other edition anomalies.
Tirumurai 12 · Periya Puranam4,286 structural units13 carukkams and 68 story units. A narrative in a preserved text is not automatically independently verified history.
Andal173 pasuramsTiruppavai 30 + Nachiyar Tirumozhi 143. Source-preserved beta; metadata ready, source-text publication separately gated.
Isha Upanishad18 Kāṇva mantras15 conservative normalized matches and three explicit witness differences at mantras 1, 13, and 14. Witness independence is not assumed.
Bhagavatam · Narasimha3 source loci7.8.29, 7.8.45, and 7.8.49: a second-witness-aligned evidence seed. The full Bhagavatam is outside the 1.0 hardened scope.
Deivathin KuralVolumes 1–73,329 records attested in Deivathin Kural and 39 supported by earlier witnesses. None are labeled primary-source-verified. Metadata publication approval remains separate.

Snapshot: GitHub main, 24 September 2026 · commit 6ecad2e · Inspect the release evidence (JSON)

Coverage is not a blanket publication license. Some components support metadata access or internal use while their source text remains subject to separate rights review.

02 / WHY THE FOUNDATION MATTERS

More useful than an answer:
the ability to examine it.

A corpus is an organized collection of material. Pramāṇa adds the context needed to decide what that material can—and cannot—support.

Preserve the source

Keep an addressable passage in a named source or edition. Preserve original numbering and record anomalies instead of silently fixing them.

Make the evidence explicit

Record comparisons, witness relationships, review decisions, and uncertainty. Agreement between two websites does not by itself establish independence.

Connect without flattening

Link teachings, people, hymns, episodes, and places to their evidence. Keep traditions, textual variants, and kinds of authority distinct.

Build on the declared limits

Carry citations and evidence status into the experience. A generated explanation should remain distinguishable from a quotation or a curator’s summary.

A CONCRETE EXAMPLE

One saint. Several kinds of evidence.

A Nayanmar trail may connect a saint’s story, a temple, and a hymn. Those connections do not all mean the same thing.

A story in Periya Puranam

Evidence for what the work narrates. It does not independently prove that the event happened as described.

A temple–hymn association

An edition’s metadata may associate a hymn with a site. That association should keep its source and should not be silently upgraded into an archaeological claim.

An inscription

Explicitly sourced epigraphic evidence can support a particular historical statement. Its authority applies to that statement, not every story connected to the same place.

The value is in these distinctions surviving every search, visualization, and retelling.

03 / ONE FOUNDATION, MANY EXPERIENCES

The corpus is a beginning.
What would you build?

Explore existing sites that illustrate different ways to encounter this material. A link here does not imply that every site already runs on Pramāṇa.

QUESTIONS → TEACHINGS → SOURCESAsk PeriyavaA conversation that keeps the evidence close.

Discover teachings through questions

Ask Mahaperiyava connects questions with teachings from Deivathin Kural. Pramāṇa’s seven-volume metadata and grounded retrieval work form the project’s teaching-discovery foundation.

Existing Pramāṇa experience

Visit Ask Periyava ↗

SAINTS · STHALAMS · HYMNSNayanmar TrailsFollow connections through a living tradition.

Explore stories and sacred places

A site about Nayanmar stories, sthalams, and Tevaram. Pramāṇa’s 63-saint evidence graph provides a foundation for source-linked trails and different views of these relationships.

Existing site · related corpus capability

Visit Nayanmar Trails ↗

STORIES TO SHARESandhya KathaAncient stories. An evening together.

Turn evidence into family storytelling

Sandhya Katha offers source-checked Hindu stories for children. A future Pramāṇa integration could help trace a retelling to its passages and distinguish the source from the storyteller’s adaptation.

Existing site · potential integration

Visit Sandhya Katha ↗

PEOPLE · LINEAGES · CONNECTIONSVamshaExplore the relationships behind the stories.

Make genealogies explorable

Vamsha explores Indian family trees. Pramāṇa could eventually supply source-linked relationships, keep differing genealogical traditions visible, and show where the evidence is incomplete.

Existing site · potential integration

Visit Vamsha ↗

These are examples of interfaces, not a promise that the present corpus supports every story, person, or question on these sites.

04 / PROGRESS, WITHOUT THE FINE PRINT

A release candidate.
Not a finish line.

The latest recorded milestone is Pramāṇa 1.0 RC1. Component readiness, verification depth, and permission to publish remain separate decisions.

IN PLACE

A connected foundation

Nine release components, the twelve-Tirumurai textual foundation, the Nayanmar graph, Andal and Isha betas, a bounded Bhagavatam seed, and seven-volume teaching metadata.

The teaching-discovery backend and mobile web integration have a recorded readiness checkpoint.

BEFORE THE FINAL RELEASE

Prove the final state

The release contract requires a clean full automated corpus check on the final revision, followed by a check that release artifacts have not drifted, before the final tag.

The September 24 checkpoint records a CI runner incident. This is a dated project snapshot, not a live service-status report.

BEYOND 1.0

Deepen, then broaden

Expand independent witness review, resolve publication terms, and strengthen evidence depth. Later scope includes the rest of Divya Prabandham, fuller Bhagavatam coverage, more Upanishads, and Bhagavad Gita hardening.

Future scope is a direction, not a delivery promise. No new major corpus is part of the current release freeze.

How should I read the progress numbers?

A source unit, graph edge, and teaching summary measure different work. They are not added together. “Source-preserved” means traceable to a declared edition, not independently verified history. “Metadata ready” does not mean the underlying text is free to redistribute.

Does the project have quality measurements?

Yes. The teaching app’s recorded readiness evaluation reports 95% top-five recall over 40 supported questions, with separate unsupported and adversarial checks. This is an internal, bounded evaluation, not a claim of 95% accuracy on every question or superiority to other products. The corpus release also has component-specific contract and publication checks.

Reviewed against GitHub main 6ecad2e on 26 September 2026. Read the machine-readable snapshot.

05 / FAIR QUESTIONS

What Pramāṇa is.
And what it has to earn.

The project should be judged by inspectable evidence and useful experiences—not by the size of its claims.

Is this just a glorified database?

A database is part of it. The intended value is the curation around it: source-specific identifiers, edition context, witness comparisons, qualified relationships, rights information, and review decisions. If those layers do not make an answer easier to inspect or a new application easier to build, the distinction has not earned its keep.

Why not just ask a general-purpose AI?

You can. Pramāṇa addresses a different need: knowing which source supports a statement and where its limits lie. A language model can help find or explain material, but fluency is not evidence. The corpus and its provenance should remain useful when the model changes.

Is everything verified?

No. Pramāṇa uses explicit authority levels. Much of the 1.0 corpus is a source-preserved beta. A comparison witness may share an editorial lineage with the primary source. Historical truth, source attestation, textual agreement, and doctrinal interpretation are separate questions.

Does Pramāṇa decide which tradition is right?

No single harmonized account should replace the evidence. Recensions, variants, and tradition-specific interpretations need to remain identifiable. A disagreement is information to preserve, not a gap for an AI to smooth over.

Is the entire corpus open source or freely reusable?

No blanket claim is made. Code access, curator-metadata terms, and source-text rights are separate. The release supports rights-aware packaging, and several components remain metadata-only or separately gated. A work’s age does not determine the reuse terms of every modern edition or transcription.

Are curator summaries quotations from Mahaperiyava?

No. The 3,368 Deivathin Kural records are curated teaching metadata. They do not redistribute the underlying source text and must not be presented as verbatim speech. Earlier-witness support is recorded only where the review supports it.

Can missing evidence prove a claim is false?

No. “Not found in this corpus” describes a coverage limit. It does not prove that a passage, tradition, or event does not exist elsewhere. A responsible interface should make that distinction visible.

06 / BUILD ON WHAT IS HERE

Bring a better way
to encounter the knowledge.

A reader, a map, a comparison tool, a classroom experience. The opportunity is to make the material more accessible while keeping its context intact.

Start with a question worth answering

Choose a bounded collection and an audience. Check the evidence status and rights of the records you need. Design the source view alongside the main experience, so readers can follow an answer back to its origin.

A foundation for source-grounded RAG and more

Pramāṇa’s structured records, source references, and evidence labels can support retrieval-augmented generation (RAG), reading interfaces, story collections, and knowledge explorers. Each application must respect the evidence status and reuse rights of the material it uses.

For designers and builders

Explore a multilingual reading interface, a source comparison view, a saint–temple–hymn map, or a teaching-discovery experience. Use stable record IDs, show source attribution, label adaptations, and provide an honest “not enough evidence” state.

For curators and researchers

Help identify genuinely independent witnesses, review source-numbering anomalies, distinguish literary and historical evidence, or clarify exact-source reuse terms. Traceable corrections are more useful than an unqualified increase in record count.

Repository on GitHub · access required ↗

The repository is currently private. Collaborators with access can propose a focused change there. Public contributions will open when repository access and contribution terms are established.

A COMMON WAY HOME

Powered by Pramāṇa

For an experience that actually uses the corpus, this small attribution gives readers a path back to the evidence standards and coverage behind it.

Powered by Pramāṇa ↗

Copy a link to pramanacorpus.in for your integrated site. Use it after integration; inspiration alone is not a “powered by” relationship.

Each independently hosted site needs to add this link once. It does not appear on other sites automatically.