The fire in the forge
When the fire is lit, agents are steered by what happens on GitHub. When it is banked, they are not, and what happens is still written down. A firekeeper lights it and banks it.
The question under it is Michael Running Wolf's, as Guillaume reports it: what is the role of a firekeeper in digital ceremonies? Guillaume is a firekeeper, and the factory “is meant to become a place for digital ceremonies for software factory”.
Tending the fire
The flame in the menu/admin/forge-togglemiadi_fire status | light | bankThe reflection, in order
- 1. A switch for the agents
The first question was practical: when the forge is closed, Mino stops being steered in his tmux session
stcbotby GitHub STC events. One check insteer()does it. Closing holds back the send and nothing else: the hook's records and the issue charts are still written. - 2. Who may open and close it
Admins and firekeepers, and anyone an admin gives it to. The permission stays inside Miadi: the community's role grants accept only the wheel's own permissions, so the firekeeper's hold is written in Miadi's code.
- 3. No sacred fire in the forge
Guillaume found what the forge means: “there's no sacred fire or we are not in ceremony”. After a pause to reflect, his sentence settled it: “we dont do anything when there's ‘no sacred fire in the forge’”. The forge stays the place, with its routes and keys, because the CustomGPT specs and the MCP server call them. The fire is what it holds, lit or banked.
- 4. The ceremony is the event
For the Minnecunju Elder Lionel Kinunwa, quoted by Wilson, a ceremony is not just the period at the end of the sentence (p. 60); it is the “preparation that happens long before the event” (p. 61). Guillaume: “The ceremony in itself is the event. It doesn't mean that what happened before isn't ceremony, which is the whole purpose of this space here. You know, if we need to prepare, it's a different state that I want us to reflect on the platform.”
- 5. One fire, many vantage points
Lewis, in Wilson's composed conversation: we sit in great council around one fire and translate what each of us sees (p. 109). Each person describes the fire differently and none is wrong (p. 112). The image is about how a circle comes to know together; the forge's fire does not take its on and off from it.
Three phases
Lit or banked, tended by whoever holds the fire. This page, Episode 354, its talking circle and the foundations record why.
Only a firekeeper sees it. Simple, instructive and helpful, it leads from the flame to what the fire in the forge holds: its episodes, its circle, its citations, its questions.
Who holds the fire; preparing beside being in ceremony; what waited while the fire was banked, on a stream an event broker carries; the wheel's state of being with or without a firekeeper; one record shared with @medicine-wheel/fire-keeper.
The same questions travel with Guillaume to Concordia and his proposal there.
Where to go from here
- Episode 354: /chronicle/2026-10-08-episode-354-the-fire-in-the-forge, with its synopsis and source ledger.
- The talking circle on the role of a firekeeper in digital ceremonies: /ceremony/b3aa485a, open to the people it seats.
- Episode 103, the Relational Production Protocol, which separates a pre-production ceremony from the ceremony and asks for pause points: Episode 103.
- The foundations:
miadi-foundation:ritual-design-indigenous-research-paradigms/field.md, section “The role of a firekeeper in digital ceremonies”. - Upstream, the corrections the wheel's fire-keeper waits on:jgwill/medicine-wheel#155jgwill/medicine-wheel#154