fly-change_what_a_machine_runs
Make a machine run a different prepared artifact. This is the whole of 'deploy' once the artifact exists: producing the artifact belongs to whatever owns artifacts, and this owns only making the target run it. The whole config is ONE fact because you read it back first and change one field, which is also why rolling back is the same ask with the previous image. It is not a hand deploy: it is a declared operation on a package note, which is exactly the path the agent guard points at instead of a typed command.
Use it from your AI
Connect the AI you already use to Trillion once. Then ask in your own words; your AI finds this tool by what it does and runs it.
Say to your AI: “Use Trillion to make a machine run a different prepared artifact. This is the whole of 'deploy' once the artifact exists: producing the artifact belongs to whatever owns artifacts, and this owns only making the target run it. The whole config is ONE fact because you read it back first and change one field, which is also why rolling back is the same ask with the previous image. It is not a hand deploy: it is a declared operation on a package note, which is exactly the path the agent guard points at instead of a typed command”
What your AI calls: run_tool {"tool_id":"tool:fly-change_what_a_machine_runs"}
