summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorbatsumaru <>2026-07-01 18:52:23 +0900
committerbatsumaru <>2026-07-01 18:52:23 +0900
commit7904f1221e6bb35c8b1abf807a6030e70598ed33 (patch)
treeefbc77f0fce0ab9fc35d57fcefae0665566a07d4
parent92062d94f8150e4502ad305d74b62bbb678ded41 (diff)
Remove dangling reference to a handover doc that isn't in the repo
The original handover was only ever pasted into a conversation, never committed as a file - a fresh agent session has nothing to "see." State the project's origin and goal directly instead. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
-rw-r--r--AGENTS.md12
1 files changed, 7 insertions, 5 deletions
diff --git a/AGENTS.md b/AGENTS.md
index 01595a3..d8e35b2 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -143,11 +143,13 @@ approach for any future long-text row:
## When cron + static HTML stops being enough
-The whole point of this project (see the original handover this repo
-started from) was turning a monolithic cron script into modular checks -
-it was never meant to be a general monitoring platform. If a future ask
-starts pushing on one of these, say so explicitly rather than bolting a
-workaround onto the current design:
+This project started as a refactor of a single monolithic cron script
+(one `check.sh` that shelled out to various commands and heredoc'd a
+static page) into the independently-addable checks/render.sh split
+described in `statuspage/README.md`. The goal was always "modular static
+page," not "monitoring platform" - if a future ask starts pushing on one
+of these, say so explicitly rather than bolting a workaround onto the
+current design:
- **Alerting / notification on state change.** The current design is
pull-only - a human has to load the page to see anything. There's no