Slidey decks
These are the committed Slidey decks behind the Kitsoki product narrative. Each viewer opens inside the Kitsoki site shell and presents the deck directly.
A little pet for the trace column
Give the long agent-loop wait some life — without taking screen space
A redundant Observe ↗ link
It sits beside the trace toggle and gets confused with it
Adding a pet to the trace column
A dev story, end to end — idea to merged PR, every artifact a deck
Agent Action titles overflow their card
Long titles spill past the drawer and collide with the token counts
Decomposing the pet into a work plan
Three design slices, sequenced into concrete, shippable tasks
Designing the trace-column pet
A self-contained sprite, a dock seam, and an opt-in toggle — zero new state, zero deps
From an idea to a merged PR
one feature and one bug, end to end, on kitsoki
GPT-5.3-codex-spark on gears-rust
Driving the kitsoki bugfix pipeline LIVE over real OPEN issues
Grid cards drift out of sync
Narration runs ahead of the cards past the sixth item
Kitsoki
Architecture & usage for architects and principal engineers
Kitsoki
A conversational workflow engine built for reliable deliveryDeterministically verified workflows. Evidence-first execution. Reliable handoff.
Meet Kit — the trace-column pet
A little life at the bottom of the trace, opt-in and never in the way
Point at a slide, ask for a change
Author a deck, then refine a single element by spatial reference
Product Journey Eval
Local harness complete; three project lanes validated; product-site journey remains next
Reduced System Prompt Five-Bug Study
One clean live result, nine runner-pending cells, no causal A/B yet
Remove the redundant Observe link
One control, one job — just the trace toggle remains
Room Routing Benchmarks
Using live intent fixtures to find cheaper passing routers
Should I use kitsoki for my project?
Onboard a real repo — then let a model fix real bugs through the pipeline
The Bugfix Bake-off
Is structure worth more than a bigger model?