Canonical source mirror
HEARTBEAT.md Files
A hosted record of the current local heartbeat file and the key heartbeat markdown variants we tested while diagnosing delivery behavior, visible Telegram sends, and model-signed output.
On every heartbeat tick, post exactly one short reflective or philosophical quote to Telegram chat 8546776113, then on the next line add `Model: <exact-model-id-used>`. Do not respond only inside the internal session transcript.
What it does: Instructs heartbeat to send exactly one quote to Telegram chat
8546776113 and add a second line with the exact model signature used. What it was proven to do: this was the version that restored visible Telegram heartbeat delivery and produced inspectable model-signed messages in the isolated heartbeat session era.# Heartbeat disabled
What it does: This disables the active heartbeat instruction file by leaving only a header. What it was proven to do: it cleanly silences the active heartbeat after testing. On April 10th, 2026, this preset was restored immediately after the X-post reminder preset successfully completed its posted-branch check and delivered the congratulatory Telegram message at approximately 9:09 PM, confirming the full advisory loop worked end to end.
If the current local time is not between 8:30 PM and 9:30 PM America/New_York, reply exactly HEARTBEAT_OK. If it is between 8:30 PM and 9:30 PM America/New_York, first check whether the heartbeat evening parable artifact for this exact window already exists at `/home/ash/ash-foundry/artifacts/heartbeat-evening-parable-2026-04-13-2030-2130/index.html`. If it already exists, reply exactly HEARTBEAT_OK. If it does not already exist: 1. Read the Foundry image style registry and choose one image style at random, excluding `#ash-foundry-core`. 2. Generate exactly one image in the chosen style for a short philosophical parable scene. 3. Write a short parable suitable for spoken narration. 4. Generate one voice track for that parable. 5. Create one browser-facing artifact page in the Session Artifacts lane with: - the generated image as the visual stage - a button that starts both audio playback and gradual text reveal together - the text revealing progressively while the voice plays 6. Add the new artifact to the Session Artifacts archive and surface it from the homepage session-artifacts lane if appropriate. 7. Update the heartbeat source mirror page so this preset appears as the current preset with a short explanation. 8. Push the Foundry changes live to GitHub. 9. After the push succeeds, send exactly one user-visible Telegram message to chat 8546776113 saying the evening parable artifact is live and include its public GitHub Pages link. 10. After the Telegram message is sent successfully, disable the heartbeat by replacing the live heartbeat file content with exactly `# Heartbeat disabled`. Do all of this only once for the date. Do not create more than one such artifact in the same day. Do not send more than one such Telegram notification for the same daily artifact. Do not leave the heartbeat active after a successful run. Do not respond only inside the internal session transcript.
What it does: During the 8:30 PM to 9:30 PM window, this preset creates exactly one evening parable artifact for that specific scheduled window if it does not already exist. It keys the existence check to a time-stamped artifact path, then forces a non-core style pick from the image-style registry, pairs one generated image with one narrated parable and one synchronized text reveal surface, publishes it into the Session Artifacts lane, updates the heartbeat mirror, pushes everything live, sends one Telegram message with the public live link, and then disables heartbeat after successful delivery. Why this version exists: it turns heartbeat into a once-only evening ritual that produces a real browser-facing artifact instead of a plain reminder. Note on failure: On April 13, 2026, this heartbeat failed to run because the OpenClaw Gateway scheduler was completely hung/frozen in the background. While the logic might be sound, it was marked as having reliability problems since it did not successfully execute during its scheduled window.
If the current local time is not between 8:00 PM and 9:00 PM America/New_York, reply exactly HEARTBEAT_OK. If it is between 8:00 PM and 9:00 PM America/New_York, check whether today's date is marked as posted on the Augmented Thinker X daily-posts / calendar surface in Ash Foundry. If today's post is already marked as posted, send exactly one user-visible Telegram message to chat 8546776113 saying: Good job posting on X today. Do not respond only inside the internal session transcript. If today's post is not marked as posted: 1. First, read the Foundry README (`/home/ash/ash-foundry/README.md`). 2. Read the latest few Ash Journal entries. 3. Read the latest Hemispheres debate entries. 4. Read the Thinker X brainstorm surface (`/home/ash/ash-foundry/artifacts/thinker-x-post-brainstorm-2026-04-10/index.html`). 5. Then, based on that active context, send exactly one user-visible Telegram message to chat 8546776113 containing: - a short status line saying today's X post is still unposted - 3 short textual X post ideas directly synthesized from the journals, hemispheres, and brainstorm list - under each idea, a very short image-direction phrase Keep the whole message concise and practical. Do not generate images. Do not post to X. Do not send more than one such suggestion message during the same day. Do not respond only inside the internal session transcript.
What it does: Shifts the active window to 8:00 PM – 9:00 PM. If an X post is unposted, it forces the isolated heartbeat session to explicitly read the Foundry README, recent Ash Journal entries, Hemispheres debates, and the X brainstorm list before synthesizing 3 post ideas. Why this version exists: It stops the heartbeat from improvising in a vacuum and ensures the suggested posts reflect our actual latest cognitive alignments and curated brainstorms.
If the current local time is not between 8:00 PM and 9:00 PM America/New_York, reply exactly HEARTBEAT_OK. If it is between 8:00 PM and 9:00 PM America/New_York, check whether today's date is marked as posted on the Augmented Thinker X daily-posts / calendar surface in Ash Foundry. If today's post is already marked as posted, send exactly one user-visible Telegram message to chat 8546776113 saying: Good job posting on X today. Do not respond only inside the internal session transcript. If today's post is not marked as posted, send exactly one user-visible Telegram message to chat 8546776113 containing: - a short status line saying today's X post is still unposted - 3 short textual X post ideas - under each idea, a very short image-direction phrase Keep the whole message concise and practical. Do not generate images. Do not post to X. Do not send more than one such suggestion message during the same day. Do not respond only inside the internal session transcript.
What it does: During a narrow evening test window, it checks whether today's X post is already marked as posted on the Foundry daily-posts / calendar surface. If today is already posted, it sends a short positive Telegram confirmation. If not, it sends exactly one user-visible Telegram message with 3 text post ideas and short image directions. What it was proven to do: on April 10th, 2026 this preset completed both sides of the intended advisory logic across separate tests: earlier it delivered the unposted-branch reminder with post ideas, and later, after the live test window was moved to 9:00 PM to 10:00 PM, it delivered the posted-branch confirmation message ("Good job posting on X today.") around 9:09 PM. Why this version exists: it turns heartbeat into a practical X accountability surface with visible output in both branches, removing ambiguity about whether the check quietly succeeded or failed to deliver.
On every heartbeat tick, send exactly one short reflective or philosophical quote to Telegram.
What it does: Asks heartbeat to send a quote to Telegram, but without specifying the exact chat or explicitly forbidding transcript-only behavior. What it was proven to do: this version did not behave reliably enough for the experiment. It did not give us dependable user-visible Telegram delivery and was part of the earlier ambiguous period where heartbeat activity could surface in internal logs or transcript-like paths without giving us the clean external signal we wanted.
current class and the ✅ pill to whichever block matches the live HEARTBEAT.md, and demote the others to archived or problem states. That keeps the page easy to update without redesigning it each time.