flyto-modules-robotics
Optional robot-control modules for Flyto2 workflows. Install this only on installations that drive a robot:
pip install flyto-modules-robotics
Without it, Flyto2 is pure software automation. With it, the workflow builder gains three steps — move, turn and stop — so a command like "advance forty centimetres" is authored on the canvas like any other workflow.
Why this is a separate package
flyto-core is the software execution engine and does not know what a robot is.
This package is discovered through flyto-core's existing
flyto.modules entry point, so hardware arrives as an install decision rather
than as a dependency everybody carries.
What a step actually does
A step builds a flyto.robotics.plan.v1 and posts it to the robot's own gateway
over loopback. It never names a machine: the job was already dispatched to a
device, so the module is running on the robot it is driving. That is what lets
five identical robots share one authored workflow instead of five copies.
The gateway — not this package — owns safety. It validates the plan against a frozen capability registry, refuses one that moves without ending in a safe stop, runs one mission at a time, and still sends the final zero-velocity stop if the caller dies mid-mission. Running out of process is the whole point.
Configuration
| Variable | Default | Meaning |
|---|---|---|
FLYTO_ROBOTICS_GATEWAY_URL |
http://127.0.0.1:8766 |
the local robot gateway |
FLYTO_ROBOTICS_DELIVERY_TOKEN |
— | bearer token, required |
FLYTO_ROBOTICS_ROBOT_ID |
— | must match the gateway's job |
Releasing
Published the way flyto-core is: push a v* tag and the workflow builds,
tests the built wheel, and uploads through PyPI Trusted Publishing. No token
lives in this repository.
git tag v0.1.0 && git push origin v0.1.0
The first release needs a pending publisher on PyPI, because Trusted Publishing has nothing to trust until then. The project is not created by hand: a pending publisher is what creates it, on the first successful upload.
The form lives under the account sidebar rather than a project's, since the project does not exist yet — https://pypi.org/manage/account/publishing/, "Add a new pending publisher":
| Field | Value |
|---|---|
| PyPI project name | flyto-modules-robotics |
| Owner | flytohub |
| Repository name | flyto-modules-robotics |
| Workflow name | publish-pypi.yml |
| Environment name | pypi |
workflow_dispatch publishes to TestPyPI instead, which needs the same entry
on test.pypi.org.
A pending publisher does not reserve the name — it only becomes a project on the first upload that uses it.
1 maintainer
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file flyto_modules_robotics-0.1.1.tar.gz.
File metadata
- Download URL: flyto_modules_robotics-0.1.1.tar.gz
- Upload date:
- Size: 22.9 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via:
twine/7.0.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
4c88f7cf13aa9497a13b494c6bd2ded1a377ea30a0ab65b8c8add59d4b121cd4
|
|
| MD5 |
fb7ed3ac7b86bfa87e41a340ce7dedd7
|
|
| BLAKE2b-256 |
aca3f6aa9226b1c378eed8869613e5b8107f290c4ad884344e853638d2bf27c3
|
Provenance
The following attestation bundles were made for flyto_modules_robotics-0.1.1.tar.gz:
Publisher:
publish-pypi.yml on flytohub/flyto-modules-robotics
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
flyto_modules_robotics-0.1.1.tar.gz -
Subject digest:
4c88f7cf13aa9497a13b494c6bd2ded1a377ea30a0ab65b8c8add59d4b121cd4 - Sigstore transparency entry: 2372212541
- Sigstore integration time:
-
Permalink:
flytohub/flyto-modules-robotics@fd7efc6cce544aedd647aa4b716982b9a6d11e2f -
Branch / Tag:
refs/tags/v0.1.1 - Owner: https://github.com/flytohub
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
publish-pypi.yml@fd7efc6cce544aedd647aa4b716982b9a6d11e2f -
Trigger Event:
push
-
Statement type:
File details
Details for the file flyto_modules_robotics-0.1.1-py3-none-any.whl.
File metadata
- Download URL: flyto_modules_robotics-0.1.1-py3-none-any.whl
- Upload date:
- Size: 17.9 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via:
twine/7.0.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
379e44b3dda0a955efa12a1914496defc33a163560706b07ab38c4b0c4dd078a
|
|
| MD5 |
0e5f73d5db6635d570bd0aad3637b5a5
|
|
| BLAKE2b-256 |
830770fa790f7d04e405e83f5b1ed43037a238cf45341d39094a65efddefaa4f
|
Provenance
The following attestation bundles were made for flyto_modules_robotics-0.1.1-py3-none-any.whl:
Publisher:
publish-pypi.yml on flytohub/flyto-modules-robotics
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
flyto_modules_robotics-0.1.1-py3-none-any.whl -
Subject digest:
379e44b3dda0a955efa12a1914496defc33a163560706b07ab38c4b0c4dd078a - Sigstore transparency entry: 2372212554
- Sigstore integration time:
-
Permalink:
flytohub/flyto-modules-robotics@fd7efc6cce544aedd647aa4b716982b9a6d11e2f -
Branch / Tag:
refs/tags/v0.1.1 - Owner: https://github.com/flytohub
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
publish-pypi.yml@fd7efc6cce544aedd647aa4b716982b9a6d11e2f -
Trigger Event:
push
-
Statement type:
