# Ziek

> Software change infrastructure: the distribution layer for software changes.

## Overview
Ziek finds codebases affected by breaking API and SDK changes, determines what actually needs to change, and produces verified migrations.

## Pipeline
upstream change → candidate consumers → actual impact → appropriate action → verified fix

## Core Principle: Qualification Matters
A matching old API call does not automatically mean a pull request should be generated.
Candidate codebases can be:
- Genuinely affected (migration required → verified fix)
- Already migrated (no action)
- Intentionally pinned to a compatible version (no action)
- Cannot independently verify (review)

## Verification Standard
Evidence over generated diffs. Tests, builds, type checks, and static verification are recorded before delivery.

## Why now
Teams already give coding agents repository access; editing code is no longer the hard part. What is missing is the application layer that routes an upstream change to the downstream code it affects and proves the result.

## Where Ziek sits
Version bots (Dependabot, Renovate) move version numbers. Coding agents edit code when prompted. Ziek is the neutral layer between them: it notices a change, qualifies who is actually affected, says "no action" with evidence when appropriate, and is built to hand the right work to the right agent. It can run as a neutral multi-vendor layer or as a provider's own update agent. Qualification is benchmarked today; generating and verifying fixes is in development. Roadmap: routing additive (non-breaking) changes to the codebases that would benefit.

## Verdicts (every candidate ends in exactly one)
- QUALIFIED_CURRENT_DEBT: baseline green, same tests red under the new version, attributable to the change, candidate-source provenance verified -> migrate
- RESOLVED_UPSTREAM: current source already adopts or accommodates the change -> no action
- NOT_REPRODUCIBLE: the package or affected API is not used by the relevant code -> no action
- WEAK_CANDIDATE: old API present, but no attributable failure under the new version -> human review
- BLOCKED: verification cannot be constructed (typed blocker, e.g. missing credentials) -> reported, not guessed

## Evidence (development benchmark)
10 real open-source repositories x 5 upstream breaking changes, labelled by manual investigation. Correct decisions: 2/10 (v0), 4/10 (v1), 6/10 (v1.1). Qualified-debt claims correct: 2/2 (v1.1). Small development set; next test is on unseen repositories.

## Founder
Sai Teja Mutchi, technical founder and AI engineer (Columbia MS Business Analytics; IIT Dharwad B.Tech). Previously Co-Founder & CTO of MindCap.io, AI Engineer at Everest Re, and Software Engineering Specialist at Dassault Systemes. LinkedIn: https://www.linkedin.com/in/sai-mutchi

## Contact
- Website: https://ziek.dev
- Contact and booking: https://www.ziek.dev/founder#talk