AI-assisted product management
Three engines on one runtime.
Krine decides what to build, Tholo builds it, Basano proves it. They are independent tools that compose. Some tasks use one engine, some use all three.
At a glance
Decide, build, prove.
Each engine is its own tool with its own page. Open one to read how it works on its own.
- Decide
Krine
Krine AI Engine is an AI product manager. It does the convergent product work, research, specs, roadmaps, and experiment analysis, and stops at the decisions that need a person.
Open Krine - Build
Tholo
Tholo AI Engine is an AI orchestrator. It reads the skills catalog, plans a task, and selects only the skills the task needs, then prepares the build to hand off.
Open Tholo - Prove
Basano
Basano AI Engine is an AI critic. It scopes a review, selects the verification skills per area, and returns a prioritized verdict of what holds and what fails.
Open Basano
The substrate
What the three share.
The engines are separate tools, so the real unity is underneath them, in what they stand on. Three things are shared, and that is where the system is one.
One runtime.
The three engines run on the same Cogent runtime. It is the shared ground they stand on, not three separate stacks that happen to share a name.
One catalog.
Each engine selects from the same open Claude Skills catalog. Krine, Tholo, and Basano pick the few skills a task needs from one library, so the same skill means the same thing across all three.
Consistent artifacts.
The engines emit artifacts with published shapes you can build against: Krine's stop package, Tholo's plan, and Basano's verdict. One engine's output is the next one's input because the shapes are stated.
One idea, through all three and back.
The engines compose; there is no single automated run that does all three. A person moves the work from one engine to the next, carrying each engine's artifact across. This is the shape across a full lifecycle. What each engine does on its own lives on its own page.
From an idea to a live, verified product, the path one founder runs.
The lifecycle
An idea, traced through all three engines and back. Hover, focus, or tap a stage to read what it does.
One idea, traced through all three engines and back. The operator carries the work across each seam.
An idea. A new idea or request enters the lifecycle. It has no order and no plan yet.
Run one today.
Basano is the engine you can watch work right now. See a real verdict on a sample page, holds and fails and all.
Deploying the engines inside a team's pipeline? Read the deployment reference.
A full case study, one real site taken through all three, is on the way.