Handbook · 6 min
A handbook for quiet tools
Documentation should read like a floor plan, not like a launch post. How we write the Hikari handbook.
Naomi Ellis
April 28, 2026
If the studio is a house, the handbook is the floor plan. It should be possible to walk it without being sold to.
One stone, one line of water
We keep handbook chapters short on purpose. A chapter that needs a metaphor for every heading is a chapter that does not yet know the room.
Installation is installation. Configuration is configuration. The lamp is explained as a margin, not as a personality.
What we will not document
We will not document growth loops. We will not document prompts that “unlock” a hidden agent. There is no hidden agent. If a capability exists, it has a door and a name.
How to read it
Start at Introduction. Open a studio. Install if you are bringing the house to your own roof. Then pick a room. The keyboard chapter is for people who already live here.
The stone in the photograph is not a logo. It is a reminder that a quiet tool can still be heavy.
