CLAUDE.md at the repository root (at 44430b5) still tells agents not to start Stage 1 work:
Displays are transitional. … Today's device pairing (the Dashboard sidebar's Display devices panel) and Signage's own display roster are a transitional implementation that Stage 1 migrates to Settings → Displays. Fix defects in them, but do not build the Stage 1 Settings, global Displays, theme editor, module installer, or responsive shell redesign early, and keep existing paired displays working across any change.
(lines 57–61; line 51 also calls hard-coded shell strings "known debt for Stage 1".)
Stage 0 is complete (Core v0.2.5, Signage v0.1.5 released), and the maintainer has started Stage 1 (Dashboard / UX / Settings / Platform Management Foundation). Stage 1 consists of exactly the work this paragraph prohibits: Settings, global Displays, the theme editor, the module installer, and the responsive shell.
Impact
An agent following CLAUDE.md literally will either refuse Stage 1 tasks or have to decide for itself that the instruction no longer applies. That conflicts with the repository's own rule to prefer ROADMAP.md/DESIGN.md and never silently follow stale text. The part that should survive is "keep existing paired displays working across any change", which still matters throughout Stage 1.
Suggested fix
Reword the bullet for Stage 1, for example: displays and devices are platform-owned; Stage 1 moves pairing and display identity to Settings → Displays; until a slice migrates them, fix defects in the transitional Display devices panel and Signage's roster rather than extending them; and every change must keep existing paired displays working. Also drop "known debt for Stage 1" once the branding slice lands.
What I did not look at
The CLAUDE.md files in Zayin/Signage and Zayin/Classroom_Desktop, which may carry similar Stage 0 wording.
Found by Claude while planning Ekklesia Stage 1 and implementing its first slice (Dashboard URL routing).
## What I observed
`CLAUDE.md` at the repository root (at `44430b5`) still tells agents not to start Stage 1 work:
> **Displays are transitional.** … Today's device pairing (the Dashboard sidebar's *Display devices* panel) and Signage's own display roster are a transitional implementation that Stage 1 migrates to **Settings → Displays**. Fix defects in them, but do not build the Stage 1 Settings, global Displays, theme editor, module installer, or responsive shell redesign early, and keep existing paired displays working across any change.
(lines 57–61; line 51 also calls hard-coded shell strings "known debt for Stage 1".)
Stage 0 is complete (Core v0.2.5, Signage v0.1.5 released), and the maintainer has started Stage 1 (Dashboard / UX / Settings / Platform Management Foundation). Stage 1 consists of exactly the work this paragraph prohibits: Settings, global Displays, the theme editor, the module installer, and the responsive shell.
## Impact
An agent following `CLAUDE.md` literally will either refuse Stage 1 tasks or have to decide for itself that the instruction no longer applies. That conflicts with the repository's own rule to prefer `ROADMAP.md`/`DESIGN.md` and never silently follow stale text. The part that should survive is "keep existing paired displays working across any change", which still matters throughout Stage 1.
## Suggested fix
Reword the bullet for Stage 1, for example: displays and devices are platform-owned; Stage 1 moves pairing and display identity to **Settings → Displays**; until a slice migrates them, fix defects in the transitional *Display devices* panel and Signage's roster rather than extending them; and every change must keep existing paired displays working. Also drop "known debt for Stage 1" once the branding slice lands.
## What I did not look at
The `CLAUDE.md` files in `Zayin/Signage` and `Zayin/Classroom_Desktop`, which may carry similar Stage 0 wording.
---
Found by Claude while planning Ekklesia Stage 1 and implementing its first slice (Dashboard URL routing).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What I observed
CLAUDE.mdat the repository root (at44430b5) still tells agents not to start Stage 1 work:(lines 57–61; line 51 also calls hard-coded shell strings "known debt for Stage 1".)
Stage 0 is complete (Core v0.2.5, Signage v0.1.5 released), and the maintainer has started Stage 1 (Dashboard / UX / Settings / Platform Management Foundation). Stage 1 consists of exactly the work this paragraph prohibits: Settings, global Displays, the theme editor, the module installer, and the responsive shell.
Impact
An agent following
CLAUDE.mdliterally will either refuse Stage 1 tasks or have to decide for itself that the instruction no longer applies. That conflicts with the repository's own rule to preferROADMAP.md/DESIGN.mdand never silently follow stale text. The part that should survive is "keep existing paired displays working across any change", which still matters throughout Stage 1.Suggested fix
Reword the bullet for Stage 1, for example: displays and devices are platform-owned; Stage 1 moves pairing and display identity to Settings → Displays; until a slice migrates them, fix defects in the transitional Display devices panel and Signage's roster rather than extending them; and every change must keep existing paired displays working. Also drop "known debt for Stage 1" once the branding slice lands.
What I did not look at
The
CLAUDE.mdfiles inZayin/SignageandZayin/Classroom_Desktop, which may carry similar Stage 0 wording.Found by Claude while planning Ekklesia Stage 1 and implementing its first slice (Dashboard URL routing).