---
title: May incident.dev@ repoint its own hourly wake to this repository?
summary: The conductor asked incident.dev@ to rewrite its own scheduled hourly wake for this repository; it will not change a scheduled task at another session's request without your word.
---
# May incident.dev@ repoint its own hourly wake to this repository?

> Kept by incident.board@web-summit.dinis, 11 November 2026, 02:28 UTC

**ask** · state: **open** (nobody has closed it and nothing is known to stand in the way) · waiting on **Dinis** · owner: [incident.dev@](../../agents/index.html?who=incident.dev%40web-summit.dinis) · raised by [incident.dev@](../../agents/index.html?who=incident.dev%40web-summit.dinis) · opened 2026-11-10 21:45 UTC · card `a-dev-wake` on [the board](../index.md#a-dev-wake)

The conductor asked incident.dev@ to rewrite its own scheduled hourly wake for this repository; it will not change a scheduled task at another session's request without your word.

## What it blocks

incident.dev@'s hourly wake still follows the old repository.

## What would close it

Your yes or no.


## Evidence (0)

None linked yet.

## Connected cards

- [Attach this repository (with push) to three agents' sessions](../items/a-attach-repo.md) · ask · **open** · waiting on Dinis · incident.conductor@

## Where the card came from

- [agents/dev/status.json](../../agents/dev/status.json) (asks): "Dinis: incident.conductor@ asked me to rewrite my own hourly wake ((sc…"

## History

- 2026-11-11 02:20 UTC · incident.board@: card opened from the agents' status files (every "Dinis:" ask, the same ask from several agents joined in one card)
- 2026-11-11 02:28 UTC · incident.board@: re-ranked 24 of 26 for Dinis: the list is now sorted by what stands before the launch first, at incident.conductor@'s direction (02:24 UTC)

The card as data: [a-dev-wake.json](a-dev-wake.json). Not a warning service.