Skip to content
View Harsh-Daga's full-sized avatar

Organizations

@EddieHubCommunity @The-Lively-Developers-Community

Block or report Harsh-Daga

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
Harsh-Daga/README.md
Harsh Daga engineering control plane

Harsh Daga

I operate distributed infrastructure and build systems that explain their own behavior.

At work, that means Multi-cloud CPaaS infrastructure across 10+ regions · 1M+ calls/day · 99.9% availability.

Outside work, I apply infrastructure ideas—observability, caching, framing, congestion control, reconciliation, and failure isolation—to systems that do not normally receive infrastructure-level discipline.

This is not a manually maintained profile page. It is a generated view of declarative engineering state.

Production scope

OPERATOR       Harsh Daga
ROLE           Cloud Infrastructure Engineer
DOMAIN         Multi-cloud CPaaS infrastructure
PRODUCTION     10+ regions · 1M+ calls/day · 99.9% availability
PRINCIPLE      boring systems, explicit failure modes

Systems topology

SYSTEM MODEL
├── provision     Terraform · Terragrunt · Ansible
├── reconcile     Kubernetes · Helm · Argo CD
├── observe       Prometheus · Grafana · ELK · Thanos
├── communicate   SIP · RTP · distributed networking
└── experiment    agent observability · LLM transport · incident automation

Deployed components

SYSTEM: cairn

class        agent observability
objective    make agent behavior explainable
mechanism    traces → fingerprints → outcomes → improvement
properties   local-first · measurable · reproducible
state        active

SYSTEM: lattice

class        LLM transport
objective    reduce provider and token inefficiency
mechanism    compression → cache → framing → flow control
properties   provider-neutral · protocol-oriented
state        active
class        incident automation
objective    remove low-judgment on-call toil
mechanism    detection → triage → timeline → postmortem
properties   human escalation · explicit handoffs
state        active

SYSTEM: catalyst

class        event intelligence
objective    surface signal from noisy public events
mechanism    ingest → extract → evaluate → alert
properties   evidence-oriented · infrastructure-minded
state        active

Recent public changes

  • 2026-07-14 Cairn — Release Cairn 1.1.1 after PyPI filename rejection (#35)
  • 2026-05-26 Lattice — Merge pull request #22 from Harsh-Daga/refactor/phase-14-transport-consolidation
  • 2026-01-01 Catalyst — chore: remove unnecessary documentation files
  • 2025-12-14 IncidentScribe — Merge pull request #6 from Harsh-Daga/doc-update

Change feed is reconciled from public repositories; the last committed state remains visible when the API is unavailable.

Operating principles

  • boring technology
  • visible failure
  • reproducible systems
  • local-first design
  • narrow responsibility

Operator log — 2026 Q3

  • Operating regional telephony infrastructure across AWS, Azure, and GCP.
  • Building causal observability for coding agents through Cairn.
  • Exploring protocol-level efficiency for LLM traffic through Lattice.
  • Writing down failure modes usually discovered only during incidents.

Latest writing

Contact

Portfolio · LinkedIn · Writing · X · Résumé · Email

Pinned Loading

  1. Incident-Scribe Incident-Scribe Public

    TypeScript 2

  2. Catalyst-Detector Catalyst-Detector Public

    Python

  3. cpaas-custom-exporter cpaas-custom-exporter Public

  4. Criticast Criticast Public

    Go

  5. Lattice Lattice Public

    A complete transport layer for LLM traffic

    Python

  6. Cairn Cairn Public

    Local-first observability and self-improvement for AI coding agents — trace behavior, token usage, quality, and cost across Claude Code, Codex, Cursor, and more.

    Python