Built in public view.

Proof, hardening, a nav that fits — and a rebuilt deploy pipeline

A broad pass to turn claims into evidence and make the whole surface pristine, front to back: live proof on the flagship pages, a hardened API edge, a desktop nav that no longer crowds on laptops, mobile performance in the green everywhere — and, under the hood, a build-once deploy pipeline with automatic rollback plus daily off-server backups of the booking data.

• New proof surfaces: a KubeVigil maintenance pulse, a shareable TCO scenario, a fourth (KSPM) case study, a public /changelog, and crawlable per-pillar writing hubs
• API hardening: the availability proxy is now rate-limited, and the anti-spam gate fails closed in production
• Desktop navigation curated to seven core destinations so it stays clean from laptop to wide display; the full set remains in the drawer and footer
• Mobile performance raised to ≥95 on every route by preloading the hero image; warm-cache load is well under a second site-wide
• Build once in CI and deploy by pull — with an automatic local-build fallback and a self-rolling-back deploy script (mandatory proxy reload, cache purge, soak-verify)
• Booking data backed up daily and pulled off-server — the last stateful surface without disaster recovery

Data Sovereignty pillar + the India lens

The sovereignty discipline gets its own page — one geo-agnostic engineering method read against the regulations of India (DPDP Act, RBI localization, CERT-In), the EU (AI Act, GDPR/Schrems II, NIS2, DORA), and the US.

• /sovereignty pillar page with regulation-by-region lenses, India first
• AI-crawler surface rebuilt: /llms.txt regenerates on every build; /llms-full.txt serves the complete article corpus
• Articles now carry a named human author entity; new posts are pushed to search indexes on publish
• Publishing pipeline hardened: enforced word band, retry-wrapped preflight, headless cache purge

NDA/PII content screener

A deterministic confidentiality gate now stands between the autonomous publishing pipeline and production: deny-listed client names and PII patterns hard-fail the run before anything ships. The no-client-names rule stopped being a convention and became a control.

v3.0 — performance milestone

Real-world page load under a second on every page: Lighthouse desktop performance 99–100, LCP 0.6–1.0s; on mobile under Slow-4G throttle, 19 of 19 routes score ≥95 with Accessibility, Best-Practices, and SEO at 100 everywhere.

Dark/light image parity

Every image on the site became a tonal twin pair — the same composition rendered as cinematic obsidian for dark theme and paper schematic for light — so toggling theme never jump-cuts the picture.

The daily auto-publish pipeline

The blog started writing itself: an autonomous pipeline researches, writes, illustrates, gates, ships, and deploys one deeply-technical article per day — dedup gates, quality gates, and a verified production deploy included. It has published daily since.

v2 — the Sovereign Instrument redesign

The full corporate website shipped: thesis, capabilities, anonymized case studies, the KubeVigil showcase, engagement model, interactive tools, and the design system this site still runs on — schematic grid, two-temperature palette, self-hosted everything.

v1 — the landing page

Where it started: a single-page landing. It lasted two days.