Collect authorized facts
Measure source kind, size, branch scope, binary volume, LFS use and rewrite intent through an approved discovery process.
INTERACTIVE TOOL / MIGRATION READINESS
Classify the path
before the calendar.
Supply six repository facts. The assessor applies a visible policy and explains whether the work belongs on a standard, review or transformation path.
Planning boundary: this browser tool does not scan a repository, estimate duration or select a migration utility. Values stay on this device and are not uploaded.
Repository migration assessment workspace
METHOD / EVIDENCE BOUNDARY
A decision with
its assumptions exposed.
Provider-neutral evidence.
Deterministic classification.
Classify before scheduling
Use the highest triggered path. Unknown evidence remains review work instead of becoming a convenient zero or false.
Rehearse and verify
Follow with Git-ref reconciliation, LFS checks, platform metadata review, pipeline smoke tests and an agreed recovery plan.
INSPECT THE IMPLEMENTATION
The browser experience mirrors the public Python policy.
The source project retains the classifier, synthetic input and generated JSON. Its current local test suite contains 63 passing tests; this page is a separate browser implementation of the documented rules.
LET’S TALK
Bring me the
interesting migrations.
I’m looking for Senior DevOps and Platform Engineering opportunities where I can improve cloud delivery, build useful automation and help teams make risk visible before cutover.
bailey.n.fitchett@gmail.comAPPLY THE APPROACH TO YOUR ENVIRONMENT
Migration Ritual
Turn the local readiness exercise into an agreed review of selected repositories and pipelines.
Separate consulting assessment. The evidence and limitations above remain specific to the original project or demonstration.
Email WitchOps Explore the assessment ↗