# Whose History Gets Written? Documentation Gaps, Caste Memory, and the Limits of AI ## An Open Letter I write this as someone with a personal stake in this question. Decades ago, I was among the students who took part in a hunger strike protesting a caste atrocity in Andhra Pradesh — the kind of event that, when it happened, was lived and witnessed directly by people who had no institutional power to write their own account of it into the historical record. Recently, I had a long conversation with an AI system while trying to get information about that period. It surfaced a widely cited detail about the community of the victims that does not match what I know firsthand, from being there. That mismatch is what prompted this piece — not because one detail on one page is, by itself, a crisis, but because it's a small, concrete example of a much larger problem. ## The Documentation Gap Here is the structural issue: written history is not a neutral mirror of what happened. It is wri...
From Zero to HTTPS: Deploying the Spices App on Google Kubernetes Engine A hands-on journey from a crashing pod to a secure, production-ready SPA + API stack on GKE, powered by spices.polakams.com. This post is a practical end-to-end walk-through of deploying a real application, Spices (an Angular frontend with a REST backend) on Google Kubernetes Engine (GKE) , served securely at https://spices.polakams.com . Along the way we'll cover DNS (with the domain registered at GoDaddy), SSL via Google-managed certificates, a single Ingress that routes both frontend and backend, and every troubleshooting rabbit hole I fell into so you can skip them. 1. The Starting Point The goal was simple to state and deceptively involved in practice: Two Kubernetes Deployments — an Angular frontend ( spicesui-app ) and a REST API backend. Domain polakams.com registered with GoDaddy. Expose everything at https://spices.polakams.com with a trusted SSL cert...