What people need
- Supported environments and clear boundaries around what is still experimental.
- One obvious first workflow that actually works.
- Commands and outputs that match the maintained product surface.
Docs
Good docs make the product feel faster.
The job of documentation is not to sound thorough. It is to get someone from curiosity to a working result without making them feel lost.
What to avoid
- Turning internal experiments into public promises too early.
- Using benchmark shorthand that hides artifact assumptions or unsupported paths.
- Making users guess which tier or checkpoint is the sane default.