News
Bot Extension Substrate ships — one automation engine for HORUS twin, PRM, marketing, insurance and intelligence bots
P0 built and deployed: a twin sensor flows through propose → inbox end-to-end live, and the twin-signal cron is running in production.
The automation engine that has driven medOS background jobs is now a universal substrate. Rather than hand-coding each new automation, teams compose bots from three reusable seams: trigger sources, the medos.* SDK namespaces, and a cowork plane identity that gives every bot a real audit trail.
The linchpin is medos.propose() — bots never write to clinical or operational records directly. They draft a proposal that lands in the human inbox, where a reviewer accepts, edits, or rejects it. That accept/edit/reject decision is itself the training label, so the system gets sharper with use while a human always stays in the loop.
P0 is built and deployed. A twin sensor now flows through propose → inbox end-to-end in production, and the twin-signal cron is live. The same engine extends without new code to PRM, marketing, insurance, and intelligence bots — each is a set of data rows, not a fork.