Kalu Kode Journal
Evidence before announcements.
The Journal documents the reasoning, experiments, failures, and measurable boundaries behind KodeBack, KodeProof, and the shared research platform.
What We Are Looking for in Our First Design Partners
Kalu Kode is pre-revenue and has not validated market fit. We are looking for a small number of organizations with real, authorized recovery or AI-refactor problems.
How We Evaluate a Product That Is Supposed to Verify AI
KodeProof cannot use its own verdict as the sole proof that it works. We need frozen campaigns, independent graders, calibrated mutations, and reports that include false blocks.
Six Generations of a Source-Recovery Architecture
Our recovery system evolved by removing one false assumption at a time: permanent opacity, reconstruction from description, recovery-shaped workspaces, and broad agent handoff.
What a Source Recovery Assessment Should Tell You
Before committing to a recovery, an organization should know what evidence exists, which route applies, what can be made independent, and what remains risky.
Honest Uncertainty Is a Product Feature
A recovery or verification system earns trust by separating what it proved, what it inferred, what it could not observe, and what it refused to change.
The Model Should Decide. The System Should Edit.
AI is valuable for semantic judgment. Mutation authority should remain with source-aware, preview-bound, rollback-capable tools.
Build Green Is Not Behavior Green
Compilation is necessary, but it cannot tell you whether a refactor changed initialization order, runtime state, layout, message contracts, or a user journey.
Why AI Agents Rename the Wrong Things
Semantic cleanup is not a global search-and-replace problem. The difficult part is distinguishing local meaning from public contracts, serialized keys, asset identities, and other protected surfaces.
What a Bundler Hides: App Code, Dependencies, and Glue
A production bundle is not one author’s code. Reliable recovery must separate first-party logic, third-party packages, modified vendor code, and bundler runtime before cleanup begins.
Recovery Starts With Capture, Not Code Generation
A raw agent cannot recover behavior it never observed. Reliable source recovery begins by preserving the deployed application as a donor and replayable evidence surface.
Shipped Software Is Not Source Code
A working application can survive while its maintainable source disappears. Understanding the difference is the first step in software ownership recovery.
Why Kalu Kode Exists
Software can keep running after engineering control is lost, and AI can change code faster than teams can safely trust it. Kalu Kode is building the evidence layer for both problems.