Scheduled Jobs
The recurring background work, described by function — memory, monitoring, backups, synchronisation, and hygiene.
The scheduled jobs fall into a handful of functional groups. Each is described by what it does; identifiers, paths, and hosts are withheld by design (see overview).
Memory and self-improvement
| Job (by function) | Cadence | What it does |
|---|---|---|
| Nightly memory consolidation | Daily, overnight | Merges semantically similar session summaries, prunes redundant entries, re-ranks the memory index, and reconciles the vault with the gateway. The unattended twin of the session-close protocol. |
| Feedback / eval pipeline | Daily, overnight | Aggregates context-feedback and skill telemetry into the signals the improvement machinery reasons over. Feeds the consolidation and analytics layers. |
Monitoring and intelligence
| Job (by function) | Cadence | What it does |
|---|---|---|
| Communication scan | Daily | Sweeps messaging channels to keep the voice-replication and drafting skills primed with current context. |
| Standing situational monitor | Daily | Runs the standing intelligence monitor and files a briefing. |
Backups and infrastructure
| Job (by function) | Cadence | What it does |
|---|---|---|
| Local encrypted backup | Hourly | Encrypted, deduplicating backup of local working state. |
| Server datastore backup | Daily | Encrypted, deduplicating, restore-tested backup of the gateway datastore on the server. |
| Vault index refresh | Sub-hourly | Re-scans the vault so the searchable index stays current between sessions. |
| Message-bridge keep-alive | Always-on | Keeps the local messaging bridge running and restarts it if it dies. |
| Network-heal watchdog | Always-on | Keeps a network control healthy across sleep/wake transitions. |
Hygiene and lifecycle
| Job (by function) | Cadence | What it does |
|---|---|---|
| Settings-permission merge | Daily | Sweeps newly-granted local permissions into the shared settings, paired with the permission-merge skill. |
| Plugin refresh | Weekly | Updates the installed plugin set. |
| Domain data sync | Daily | Pulls a domain data feed into the vault for downstream reporting. |
Vault and skill synchronisation
Two things must stay consistent across the two doors: the vault and the skill set.
- The vault is dual-written — edited locally and synced to a store the server reads. The index-refresh job keeps the server's view current.
- The skill set is kept in parity by a bidirectional synchronisation job that pushes local skill changes to the server and pulls server-side improvements back, so both doors run the same skills. A separate probe periodically verifies that the sync actually round-trips, rather than assuming it.
The reconciliation protocol (operations → reconciliation) is the periodic check that all of this — jobs, skills, integrations, and the map that documents them — still matches reality.
Retired jobs
The registry also records jobs that have been retired — for example a client-specific ingestion job wound down when its retainer ended, and a local service that was superseded when its function moved to the server. Retired jobs are documented rather than silently deleted, so the history of what once ran is not lost.