Every
endpoint.
The places where the work is published and the record is kept. Code, cricket, the Stargaze branch and the old machine files.
The legacy files stay on the old domain until Stargaze Release 01. If a link moves, the contact page is the fastest way to flag it. External links open in a new tab and are not tracked by this site.
Every route here is part of this site. External destinations are listed above by category; if an endpoint moves, the contact page is the fastest way to flag it.
How this
index works.
A map of the places where the work is published.
This page collects the canonical public endpoints: code, cricket, the Stargaze branch, the contact routes and the legacy machine files. It is deliberately a list, not a feed.
Where an endpoint is external, the link opens a different site with its own rules and retention. Where it is internal, the page belongs to this build. The distinction is marked in the category label.
Canonical
routes.
The routes that represent the current site.
Code
endpoints.
The public repositories that matter most.
Cricket
endpoints.
The record and the context around it.
Machine-
readable.
The old files, kept until Release 01.
The
identity.
One name, a few public surfaces.
The public identity is deliberately narrow: Pranav Dwivedi, software engineer and cricketer, with Stargaze as the software branch and Destroyers CC as the club. The same name and the same record should appear wherever the work is indexed.
The older portfolio used a machine-readable entity profile. That material is still online while the current site builds its replacement. When the new schema ships, the old file will point to the new one rather than disappear.
Link
policy.
How the index treats the places it points to.
- External links open in a new tab where they leave the site.
- No affiliate or referral tracking is added to outbound links.
- The site does not embed third-party video, ads or analytics.
- A dead endpoint is removed from the index or marked as archive.
- The contact page is the fastest way to report a broken route.
Archive
map.
What moved and what stayed.
- 2024The first portfolioThe early public site, later replaced by the knowledge-graph build.
- 2025Knowledge graphThe entity home, llms.txt and profile.json experiments.
- 2026Multipage siteThe current editorial build, with the work ledger and cricket record.
- 2026StargazeThe software branch becomes the public home for the systems.
Status
key.
The three labels used on this page.
If a link
breaks.
The index is only useful while it is honest.
Send the route and what you expected to find. A broken link is usually a moved file, a renamed repository or an external site that changed its structure. The fastest fix is to know which of those happened.
The contact page is the right place for the report. Include the page you came from if you can. That makes it possible to fix the link at the source instead of only patching the destination.
Mirrors and
copies.
The places the work appears more than once.
The source of truth for public code and releases.
PrimaryThe branch site for the software systems and release notes.
PrimaryThe previous site, kept online until the new machine files exist.
ArchiveThe cricket record as published by Destroyers CC.
OfficialContact
endpoints.
The direct routes, by reason.
What is not
listed.
The boundary of the public index.
- Private repositories and active core systems.
- Personal accounts that are not part of the professional record.
- Old files that have been superseded and are no longer useful.
- Any destination that requires an account the site cannot verify.
Naming
conventions.
A small amount of consistency goes a long way.
Routes use lowercase file names and a single canonical spelling. Projects keep the name they were built under, even when the surrounding branch changes. The archive label is used when a project is kept for context rather than current use.
The rule is simple: a route should mean the same thing on every page. If a destination moves, the index changes rather than leaving a second, almost-correct link behind.
A small
sitemap.
The routes worth knowing by heart.
Last
verified.
The current state of this index.
Machine
access.
The site is readable without a browser renderer.
The pages are static HTML with ordinary links. There is no account wall and no client-side router that hides the content from a crawler. The legacy machine files remain available while the new schema is in private build.
When the Stargaze release ships, the profile and summary files will move to the branch domain. The old URLs will keep working for a transition period, then point to the new canonical location.
Elsewhere,
properly.
The public work is spread across a few deliberate places. Start with the code or the record, then use the contact page if something is missing.
Open the route