📘 Concept guide · Not a released product
Timer by Rose: how the concept could work
These are proposed steps for a future authorised preview. They do not activate a schedule or send a message.
🌹 Read the Timer by Rose overview →
Before you begin
Status: Concept. Scheduled chat delivery, recurrence, pause/stop, restart recovery and consumer installation have not been verified. No working Timer by Rose controls are offered on this page.
A possible simple schedule
- Write the instruction you want Rose to use.
- Choose when it should run: once, after a delay, daily, on weekdays or at an available interval.
- Choose the timezone so the intended local time is clear.
- Select a specific existing chat only if an authorized delivery method verifies its identity, ownership and consent.
- Choose whether to receive a notification. Silent mode would reduce unnecessary alerts or focus changes; it would not hide activity or bypass a human approval.
- Review the instruction, target and timing before saving or activating a schedule.
- Check a delivery receipt afterwards. A schedule being queued is not proof that a prompt was sent, acknowledged or completed.
Optional advanced ideas
CRON expressions, multiple target chats, conditions, dependencies, retries, expiration and delivery history are ideas for a hidden Advanced mode. They are not available functions and no sub-hourly cadence is promised.
Keep Loop separate
Loop by Rose is a separate concept for continuing eligible work through a governed job sequence. Timer by Rose is the scheduling concept. Related names in project notes—including Cron Timer by Rose, Advanced Timer by Rose, Loop Timer by Rose and Prompt Timer by Rose—do not mean there are extra released products.
Back to the Timer by Rose concept overview →
Installation, compatibility and availability
Release status: Concept · unreleased / availability unverified. No installation steps or supported platform are provided unless a verified release is announced. This guide records the intended workflow, not an available control.
Setup: no verified installer, prerequisites, configuration or permission flow is documented here. Do not follow speculative installation steps.
Compatibility and requirements: not verified.
Troubleshooting
No release-specific faults or recovery steps are verified while this Petal remains unreleased. Check its availability first; if you think this page is wrong, contact support.
Frequently asked questions
Can I use this Petal now?
Availability is not verified; the status above describes the current evidence.
Does this page promise a release date?
No. It records the intended workflow and known evidence gaps.
Privacy, permissions and safety
Do not provide secrets or sensitive data to a concept workflow. Data handling, storage and permissions must be confirmed from an implemented build before release.
Release status and evidence
Status: Concept · unreleased / availability unverified. This guide is not release evidence. Confirm availability on the Petal overview; no supported release is asserted here.
Support and feedback
Send a question, correction or suggestion to support@kingding.co.uk.