The engines
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
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
An open 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
A 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.
The same three pieces, recombined per task.
The engines compose; there is no single run that does all three. A person moves a task through them, carrying each engine's artifact to the next. Some tasks need one engine, some need the set.
Common workflows
Pick a task to see which engine or engines run, in what order, and the artifact that comes out.
Krine prioritizes, Tholo builds, Basano proves. A person carries each artifact to the next engine.
Backlog. A quarter of candidate work goes in: ideas, requests, and open questions, with no order 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.
A full case study, one real site taken through all three, is on the way.