Organization
Project Structure
Kenate projects are organized strictly. If you put your mission logic in the same file as your hardware pin configuration, you're doing it wrong. I enforce a structure that actually scales.
Standard Layout
Run kenate init and I build this for you, so you don't spend three hours arguing over where to put your config files:
The src/ Directory
The src/ folder is your home. Put your autonomous state definitions and mission scripts here. Do not touch the framework folders unless you actively want to break things.
configs/robot_profile.json
The "blueprint" of your hardware. By separating the Brain Logic from the Body Data, you can run the exact same mission code on completely different robots just by swapping this file. It's almost too easy.
.kenate_logs/
The high-speed Black Box. If your robot crashes (and it will), you check this folder to see the high-frequency telemetry data. It's how you figure out what went wrong instead of guessing.