01 / OBSERVE
Understand the upstream change
Release notes, migration guides, package releases, API specifications, and source changes can become a concrete change event.
Software change infrastructure
Ziek is building the distribution layer for software changes.
When APIs and SDKs change, Ziek finds affected codebases, determines what actually needs to change, and produces verified migrations.
upstream change
→
impact
→
action
→
verified fix
Thesis
Software changes still ship through documentation.
API and SDK providers publish release notes, changelogs, deprecation notices, and migration guides. Developers then have to discover the change, determine whether their code is affected, interpret what the migration means for their implementation, make the change, and verify that it still works.
Coding agents have made code modification dramatically easier.
The missing layer is connecting an upstream software change to the downstream code that should actually change.
System Architecture
The change distribution pipeline
How a raw upstream library event transitions into a verified downstream repository fix.
UPSTREAM
API / SDK Release
Source event
CHANGE EVENT
What changed?
Symbol & signature diff
DISCOVERY
Who might be affected?
Candidate dependency graph
QUALIFICATION
Who is actually affected?
Baseline vs target check
ACTION
What should happen here?
Smallest targeted change
VERIFICATION
Did the migration work?
Tests, builds, type checks
DOWNSTREAM
Verified Fix
Delivery to repository
Core Differentiation
Not every match needs a patch.
A repository referencing an old API does not necessarily need a pull request. The same upstream change can leave different codebases in completely different states.
UPSTREAM CHANGE
SDK v2 → v3
REPOSITORY A
AFFECTED
Migration required → VERIFIED FIX
REPOSITORY B
RESOLVED
Already migrated → NO ACTION
REPOSITORY C
COMPATIBLE
Intentionally pinned → NO ACTION
REPOSITORY D
UNKNOWN
Cannot independently verify → REVIEW
Detection finds candidates. Qualification determines what should actually happen.
Pipeline Walkthrough
How it works
A continuous technical narrative from upstream detection to verified fix delivery.
02 / DISCOVER
Map the downstream impact surface
Find codebases that may depend on the changed behavior across manifests, imports, and symbol references.
03 / QUALIFY
Prove whether current code is actually affected
Inspect current implementation, dependency state, existing migrations, compatibility constraints, and available verification paths before triggering action.
04 / REMEDIATE
Produce the smallest correct migration
When action is appropriate, generate the repository-specific change scoped strictly to the affected code path.
05 / VERIFY
Prove the result
Use the strongest available repository checks before considering a migration ready: tests, targeted tests, type checking, builds, and static verification.
Evidence Standard
Evidence, not generated patches.
A generated diff is not proof that a migration is correct. Ziek evaluates software changes against real repositories and records what actually happened.
We're testing Ziek against upstream software changes and real downstream repositories. Results and verified migrations will be published as the evidence develops.
Qualification Category
Repositories qualified
Verification Standard
Verified migrations
Upstream State
Already resolved
Classification
Not reproducible
Review Discipline
Maintainer-reviewed
For API & SDK Teams
Ship the change, not just the changelog.
If you maintain an API, SDK, or developer platform, your migration guide explains what changed. Ziek is exploring the next step: determining where that change matters downstream and turning it into verified action.
Accountability
Found a Ziek pull request?
Every submitted change should be traceable to an upstream change, qualified against the repository's current state, and reviewed before delivery. If a migration is unnecessary, incomplete, or wrong, we want to know.
Contact us
pr-review@ziek.dev
Software should be able to absorb the changes it depends on.
We're building the infrastructure to make that possible.