A place that holds the record.

Civilizational records — temples, manuscripts, villages, lineages — held to a hundred-year horizon. Three short maps for first arrivals.

Vamshanidhi is an archive for the Indic civilizational record: temple foundations and deities, ancestral villages, manuscript traditions, family lineages, inscriptions on stone and copper. Each row carries a named contributor, a scholar concurrence (or the honest absence of one), and an append-only audit trail. The platform takes a hundred-year horizon: every URN is stable, every claim is citable, every retraction is preserved.

The platform is in soft launch. The Scholar Council is in bootstrap (see /scholar-council/seats). Until the seats are filled, every verified row reads as provisional — the platform does not pretend.

1 · Read the archive.

Eight surfaces, each answering a different shape of question. Start anywhere; every record links to the others it touches.

/explore
Curated landing across every record type.
/atlas
Every record on the map of Bhārata.
/lineages/network
How the verified lineage corpus clusters around shared anchors.
/temples
Browse temples by region, deity, or moderation state.
/manuscripts
Browse digitised manuscripts with IIIF viewer + provenance.
/lineages
Verified public lineages, filterable by anchor.
/kinship
Kinship terms, sapinda checker, marriage-verdict tool.
/timeline
Multi-axis chronology, 6th c. BCE → present.

2 · Trust the record.

The platform earns trust by surfacing its own state. Eight surfaces show how verification works, who holds authority, where the records come from, and what changed when.

/transparency
Platform-wide trust ledger: verification rates, dispute density.
/scholar-council
The body that holds the record. Composition, authority, posture.
/scholar-council/seats
The twelve seats with named holders or vacant badges.
/scholar-council/bylaws
The operating rules. Adopted by the council, binding upon itself.
/federation
Peer institutions mirroring the record.
/provenance
Per-record trail: source → ingestion → verification → publication.
/changelog
Every governance event, audit-chained.
/contributors
Named contributors who opted in to public attribution.

3 · How to contribute.

The archive grows because contributors attest records. Public attribution is opt-in; private family trees are private by design (see ADR-0070).

/contribute
The contribution hub: pick a record type.
/contribute/lineage/new
Submit a family lineage anchor (gotra, kuladevataa, ancestral temple).
/genealogy
Build a private family tree, share via signed link.
/register
Create an account to start contributing.

The /about page tells the longer story. The governance ADR set carries the constitutional documents. The privacy posture documents the Schedule-1 boundary. Welcome.