Evaluating scope.

At any given time we have had work moving across Kova, Deriva, Hikaru, PICO, and the rest of our model lineup, alongside everything else that keeps a project like this running. That spread felt productive. In practice, it meant no single thing was getting the attention it needed, and overall progress across the board was slower than it should have been.

We stopped to evaluate that honestly rather than keep pushing on all fronts at once. The result is a clear order of priority across our active projects, instead of an implicit assumption that everything matters equally.

The new order

From most development effort to least:

• 1. KovaOur home agentics platform gets the most development and work done on it. It is our nearest ship and the product everything else feeds into.
• 2. Deriva-1Second priority, and the model Kova is built around. See Deriva-1 in development.
• 3. Hikaru-1Third priority. Still in development, but at a reduced pace: Slowed, not paused.
• 4. PICO-1Last in line. Also continues at a reduced pace: Slowed, not paused.

Why this order

Kova is first because it is the product people will actually use, and because it is close to shipping. Deriva-1 is second because Kova runs on it directly; without Deriva-1 improving, Kova cannot improve either. Hikaru-1 and PICO-1 both continue, because we are not willing to simply drop work that is already underway, but they move at a reduced pace while Kova and Deriva-1 get the bulk of our attention.

This is not a statement that Hikaru or PICO matter less as ideas. It is a statement about sequencing: we would rather ship fewer things well, in a deliberate order, than keep every project crawling forward at the same slow pace indefinitely.

What changes for you

Status labels across the site now reflect this directly. Deriva is marked In development. Hikaru and PICO are marked Slowed: still moving, just not our current focus. Everything else remains a concept, unchanged. We will keep these labels honest as the order shifts.