Organization
Project Structure
Kenate projects are organized to separate mission logic from hardware configuration. This ensures consistency across all robotic platforms.
Standard Layout
When you run kenate init, the system scaffolds this structure:
my_robot/
configs/Robot Profiles (.json)
drone_v1.json
src/Mission Logic
patrol.py
main.pyEntry point
examples/Reference Templates
python/Framework Libraries
.kenate_logs/Mission Telemetry
build/Hardware Bridge Binaries
The src/ Directory
The src/ folder is where you live. Place all your autonomous state definitions and mission launcher scripts here. Engineers should never write mission logic in the framework folders.
configs/robot_profile.json
The "blueprint" of your hardware. By separating the Brain Logic from the Body Data, you can run the same mission code on different robots just by swapping this file.
.kenate_logs/
The high-speed "Black Box." This directory stores high-frequency telemetry data for post-mission analysis. If a robot crashes, you can "rewind" this data to see exactly what happened.