Routines and self-repair | Company OS Docs

📄️ Routines and the registry

A routine is a job the box does on its own. Every one has a row in one list, and a job with no row is refused at deploy.

A routine can say what "it worked" looks like. A checker looks every 5 minutes, reports a break once, and flags routines it cannot verify.

Every broken routine reports to one agent. Otto applies known fixes and tells, proposes the rest, and never repairs silently.

Every morning at 8, one job checks 18 things about the box. It emails the owner only when something is wrong.

Every 30 minutes the box clears its own memory and browser buildup, and refuses to touch anything in use.

Every change is made in one folder in git first. A script copies only what changed onto the box. The box never differs from the folder.

Before dawn, the box builds today's page, sorts the mail safely, and drafts what it can. It never sends. An example from the reference install.