Lifebase Automation
Lifebase onboarding includes one required recurring job: daily maintenance. Journal wrap-up and automatic day planning are additional workflows you opt into separately.
Required daily maintenance
Section titled “Required daily maintenance”The default job runs at 04:00 every day in the detected IANA timezone. It first archives eligible completed Task Notes, then applies routine cleanup rules to the active Task Board. Items that require judgment remain for review.
Onboarding checks for an existing job before registering one. It must verify registration, the next run, and a dry run or equivalent safe test. The job must be scheduled and tested, not just saved as a prompt.
Check the Lifebase daily maintenance job. Confirm its vault, timezone, schedule, next run, and safe test result. Repair duplicate or missing registration only for this vault.The job runs through the automation capability of your agent environment. The CLI does not supply a universal background scheduler, and skill files do not execute themselves. The chosen runtime must be able to access the vault when the job runs. Model usage and provider charges depend on that runtime and your provider arrangement.
If your environment cannot register recurring work, onboarding leaves the required item incomplete and identifies what is missing. Choose a scheduler and a device that can run the job, then verify it before finishing setup.
Optional scheduled workflows
Section titled “Optional scheduled workflows”| Workflow | What to decide before enabling it |
|---|---|
| Journal wrap-up | Which completed days it may process and when your writing is finished |
| Day planning | Which date to prepare, confirmed commitments, and reusable schedule preferences |
Keep these jobs at separate times. Additional day planning should run after maintenance finishes; wrap-up should run only after its target day is over. You can use cron for these optional jobs if your environment supports it; cron itself is not required. These jobs must preserve your diary and use only routines you have agreed to.
Check changes to your setup
Section titled “Check changes to your setup”Recheck the vault path and timezone when you move the vault, change devices, or travel. Inspect the registered job and recent result rather than assuming synchronization moved the scheduler too.
Git is optional and is disabled for automation unless explicitly configured. Synchronization, selected text history in Git, and independent backup have different purposes. Choose the relevant setup skills if you need them; none is a substitute for verifying that a recurring job actually runs.