CASE STUDY · PUBLIC
deployed web
Three production surfaces plus this site, deployed and serving: the portfolio's proof that the full-stack claim ends in a live URL, not a repository.
Status ruling production-grade
Problem
A full-stack claim is easy to make and hard to check. The operation needed deployed surfaces a visitor can open in a browser right now, each tied to a real venture.
Build
- The personal brand surface (ishanparihar.com) and this authority site (tech.ishanparihar.com): SvelteKit, prerendered, on Cloudflare Pages.
- The community surface for the Law of One India group (thelawofone.in), and the Design-Aesthetics practice surface (designaesthetics.co.in): the operator's working ventures, live.
Outcome
- Four production surfaces serving today, each checked from outside before this study was written. This is the operator-ruled production-grade tier: the only class where the claim is simply "open the URL".
- The full stack behind them is the rest of this ledger: the governance tooling, the memory substrate, and the private backends whose gates are reviewable under NDA.
Provenance
| Live surfaces | 4 URLs, all 200 | HTTP-verified 2026-10-26 before publication |
|---|
Reproduce
Open the URLs. A production-grade claim needs nothing else: ishanparihar.com, tech.ishanparihar.com, thelawofone.in, designaesthetics.co.in.
Live surfaces
Private repository: a walkthrough is available on request instead of a link.
From the documentation
Four production URLs are the claim, and each answers 200 for a reader right now, which is the only verification a deployment claim actually needs.
live surface list, verified 2026-10-26
The sites are separate systems on one account, not pages of one site: a personal site, this technical-authority surface, a community project and a client brief.
deployed surfaces register row
The technical-authority surface you are reading is one of the four, which makes it a self-hosting proof rather than a claim about someone else.
same register row