Skip to main content

Kaizen

Architecture-driven modernization. Audit trail ships by default. Decompose legacy codebases into editable Architectural Decision Records (ADRs), recompose to modern stacks — compliance is what good architecture produces, not a feature you bolt on.

The ADR is the product. Every architectural decision is cited to file:line in the source, reviewable as markdown, signable for compliance. The code generation is downstream of the contract — a human reviewer can accept, edit, or reject decisions before any modern code is written.

Install

# Recommended: isolated install, no virtualenv needed
pipx install kaizen-3c-cli

# uv (faster resolver)
uv tool install kaizen-3c-cli

# pip
pip install kaizen-3c-cli

Also available without Python:

winget install Kaizen3C.KaizenCLI          # Windows
npm install -g kaizen-cli                  # any platform with Node
brew tap Kaizen-3C/tap && brew install kaizen-cli  # macOS / Linux

Requires Python 3.10+ (pipx/uv/pip installs only). You will also need:

  • ANTHROPIC_API_KEY or OPENAI_API_KEY in your environment (or a local .env file).
  • Rust toolchain (cargo) if using --recompose for C/C++ → Rust memory-safety work.
  • .NET SDK (dotnet) if using --recompose for framework-migration work targeting .NET 8.

Quick start

Memory safety roadmap (C/C++ → Rust)

For CISA memory-safety roadmap compliance. Produces a CISA-format roadmap markdown + per-module ADR stubs.

kaizen memsafe-roadmap ./my-c-lib \
  --output roadmap.md \
  --adr-dir ./adrs \
  --glob "*" \
  --provider openai

# Plain mode (no --domain schema — sufficient for most cases):
kaizen memsafe-roadmap ./my-c-lib --plain -o roadmap.md

# With Rust code generation:
kaizen memsafe-roadmap ./my-c-lib --recompose --rust-output ./rust-port

Framework migration plan (.NET Framework → .NET 8, AngularJS → Angular, etc.)

kaizen migrate-plan ./legacy-csharp-project \
  --from dotnet-framework --to dotnet8 \
  --output migration-plan.md \
  --provider openai

Supported transitions: angularjs->angular, angularjs->react, jquery->react, dotnet-framework->dotnet8, dotnet-framework->dotnet9, python2->python3, spring4->spring-boot3, java8->java17, java8->java21.

Dry-run first

kaizen memsafe-roadmap ./my-c-lib --dry-run
kaizen migrate-plan ./project --from angularjs --to angular --dry-run

Prints the planned pipeline steps without calling any LLM. Use it to check paths, glob patterns, and provider settings before spending tokens.

Why this instead of one-shot AI coding tools?

Measured on 2 case studies at temperature=0:

Case study One-shot LLM (compiles?) Kaizen plain ADR (compiles?)
inih C → Rust (522 LOC) ❌ 6 cargo check errors ✅ 1 error (minor gap)
Nancy NancyContext.cs .NET Fx → .NET 8 (148 LOC) ❌ 14 dotnet build errors ✅ 0 errors

The ADR-as-contract closes ~83–100% of the "will it compile?" gap that one-shot LLMs leave open. The --domain memory-safe / --domain framework-migration schema flags add enterprise-tier plan-document richness (CISA-format roadmap, API-contract tables, dependency upgrade paths) on top.

The one-shot baseline control is shipped with the CLI — run oneshot_baseline.py on the same source to measure the delta on your own code.

Positioning vs. alternatives

  • vs. LegacyLeap (full-lifecycle enterprise modernization platform) — we ship only the ADR + recompose pieces; cloud-agnostic; developer-led distribution.
  • vs. Amazon Q Developer Transform (Java 8 → 17 auto-upgrade) — we're LLM-agnostic (Anthropic or OpenAI), cloud-agnostic (runs on a laptop or air-gapped), cover broader language pairs, and expose the ADR as editable intermediate.
  • vs. Google Jules / OpenHands / SWE-agent (generic AI coding agents) — we're synchronous + deterministic (temperature=0 default); auditable ADR artifact; different trust model for architecture-driven workflows where compliance is the goal architecture serves.

The ADR-as-contract claim, measured

Three-arm ablation (case study):

  • One-shot LLM (no pipeline): 6 errors on cargo check.
  • Kaizen plain ADR (no domain schema): 1 error. +5 errors closed by the ADR alone.
  • Kaizen + --domain memory-safe: 0 errors. +1 additional error closed by the domain schema.

The plain ADR pipeline captures ~83% of the measurable value. The domain schemas are enterprise polish. Commercially, this is an open-core model: free plain ADR, paid domain schemas + audit-log + air-gapped deployment.

License

Apache-2.0. See LICENSE.

Contributing / Issues

https://github.com/Kaizen-3C/kaizen-cli

Status

1.0.0 — Alpha. CLI subcommands memsafe-roadmap, migrate-plan, run, priors, status are end-to-end. PyPI package bundles the pipeline scripts via sdist for now; Phase C will move them under cli/pipeline/ as a proper subpackage.

Case studies:

See docs/markets/ for the product wedge docs (memory safety + framework modernization) and ARCHITECTURE_VALUE_MATRIX.md for the honest value claims backed by data.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

kaizen_3c_cli-1.0.3.tar.gz (622.3 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

kaizen_3c_cli-1.0.3-py3-none-any.whl (647.4 kB view details)

Uploaded Python 3

File details

Details for the file kaizen_3c_cli-1.0.3.tar.gz.

File metadata

  • Download URL: kaizen_3c_cli-1.0.3.tar.gz
  • Upload date:
  • Size: 622.3 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for kaizen_3c_cli-1.0.3.tar.gz
Algorithm Hash digest
SHA256 860fe3908452709c97a94bcc8c906e3263712180dc7191ca55b3974e1622d284
MD5 2270f8b0069a3a6f2089089baadfe518
BLAKE2b-256 4d4550764caa1b12b1c8b9498f8b373fbd5d1b2dee44d798f854b58111488ebc

See more details on using hashes here.

Provenance

The following attestation bundles were made for kaizen_3c_cli-1.0.3.tar.gz:

Publisher: release.yml on Kaizen-3C/kaizen-cli

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file kaizen_3c_cli-1.0.3-py3-none-any.whl.

File metadata

  • Download URL: kaizen_3c_cli-1.0.3-py3-none-any.whl
  • Upload date:
  • Size: 647.4 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for kaizen_3c_cli-1.0.3-py3-none-any.whl
Algorithm Hash digest
SHA256 4d79a130c86961fb4a542ef63bccb0694dee457898b4bfc66b685ba39710c13b
MD5 96b3a1e02652cd4ea6eaba1d8ceb5597
BLAKE2b-256 19c17d9b74a31651e66d8f859b44c0e399fe39186a3fb407bfa3da7e2208ce7e

See more details on using hashes here.

Provenance

The following attestation bundles were made for kaizen_3c_cli-1.0.3-py3-none-any.whl:

Publisher: release.yml on Kaizen-3C/kaizen-cli

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Release history Release notifications | RSS feed

This release

1.0.3 This release

2 files

1.0.2

2 files

1.0.1

2 files

1.0.0

2 files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page