moonly train
a skill of release, inside its node 3, moonly: how the versions the weeks made become one product release of cyberia under its moon's name. the owner, 2026-11-21: the three trains are our train, each its own configuration.
trigger: the full moon: a daily clock that waits for it.
the graph
| node | role | makes | green when |
|---|---|---|---|
| 1 gather · code node | — | the product: every repository of the release culture at its version, and every one outside it with what it lacks | the list is whole: no repository of the organisation is missing from it |
| 2 prove · worker | sensor plays the user | every claim of every product page walked on the listed versions | a receipt per claim |
| 3 prepare · worker | bridge-out | a draft of the release under the moon's name and a decision for the owner, as a card | the card passes the standard of a prepared decision |
| 4 cut · gate | the owner | the release published | the owner's signed word |
| 5 tell · worker | bridge-out | the release beside the moon's report: one changelog a person can be told | the report links the release |
its arguments
| argument | value |
|---|---|
| scope | the whole product |
| takes | the versions as the weekly train left them |
| name | the moon's own, year.moon in lunar machine time: 56.11 |
| gate opened by | the owner |
| carried to | the releases of cyberia |
return edges
- short: a moon the owner skips stays a draft; the next is prepared at the next full moon.
- culture: a repository listed as outside the culture is a unit of deliver to bring it in.