openvibers/openvibe.bot Commits

README first screen and CITATION.cff (#369)

OP OpenVibers committed 3 days ago · 5532233f1b · 2 files, +21 −0

Changes

ddiff --git a/CITATION.cff b/CITATION.cff
nnew file mode 100644
iindex 0000000..0ff277b
---- /dev/null
++++ b/CITATION.cff
@@@ -0,0 +1,18 @@
++cff-version: 1.2.0
++message: "If you use OpenVibe.Bot in research or a product, cite it as below."
++title: openvibe-bot
++type: software
++authors:
++ - name: OpenVibe
++ alias: OpenVibers
++ website: https://openvibe.network
++repository-code: https://github.com/OpenVibers/OpenVibe.Bot
++url: https://openvibe.bot
++license: AGPL-3.0-only
++abstract: "Pair a robot in minutes and drive it safely from a browser, from anywhere, at openvibe.bot."
++keywords:
++ - openvibe
++ - control-panel
++ - iot
++ - nodejs
++ - raspberry-pi
ddiff --git a/README.md b/README.md
iindex ea9179b..1a35af9 100644
---- a/README.md
++++ b/README.md
@@@ -2,6 +2,9 @@
The open control panel for robots (openvibe.bot). Design: OpenVibe.Contracts docs/adr/ADR-043-bot-devices-and-control.md; plan track T15.
++**Live site:** https://openvibe.bot · **API docs:** https://openvibe.services · **For AI:** https://openvibe.bot/llms.txt
++**Run it:** `npm ci && npm run dev` (Node 22 or newer) · **Tests:** `npm test`
++
## Purpose
OpenVibe.Bot pairs a robot's machines, keeps their state and gates every operator command. A device opens one outbound WebSocket to `/device`; a person drives it from `/control` or the REST API, through the same gate — roles, per-robot limits, cooldowns and the turn budget — over a panel built from the robot's profile rather than per-robot code.