The story behind Kogen

Origins

Kogen grew out of a practical question: how much of software development can you hand to an agent while keeping the product decisions?

It started with repeated instructions in real project work. Clarify the feature. Keep the change bounded. Run the checks. Review the result. If the review finds a problem, fix it and check again.

From rules to a product

Those instructions became shared Cursor rules. The archived rules repository preserves that stage of the work.

Optimum Codegen took the next step: preparing isolated workspaces, prompts, and the context an agent needed to build a feature. Over time, checks, review, rework, and commit handling became parts of the system itself.

Shaping brought the product decisions into that process. The unit of work became a feature that could be investigated, captured in an Intent, approved, built, and independently reviewed.

Kogen retains the Codegen development history, which begins in June 2025. The Start from clean slate commit marks the boundary between the earlier implementation and the current generation.

A name that stuck

Almir was talking about Codegen in a voice memo. Apple’s transcription kept writing “Kogen,” even when he spelled out the name. The transcription became the name.

A smaller core

The system accumulated answers to real problems, but it also became rigid. Automated checks for context and code drifted out of sync with the rules for writing them, and builds began to fail.

The rewrite aimed to find a better balance: enough structure to make the process reliable, enough flexibility to let it evolve, and the same core concepts. But it tried to carry too much of the existing machinery forward before proving the smallest complete product.

Jumpstart returned to the essential sequence: shape, approve, implement, check, independently review, rework when necessary, and commit an accepted result. One Intent. One Build. One Commit.

That core is still under development. The ambition remains: resolve the feature carefully enough that Kogen can carry the approved Intent through the Build.

Prepared to fit together

The model-kit logo reflects that division of work. Shaping prepares purposeful parts and resolves how they fit. The Build carries that preparation through implementation and verification.

You shape the feature together with Kogen and approve the Intent. Kogen handles the implementation loop. Checks and independent review establish whether the result can become a Commit.