Home / Documentation / Automation Manual

Automation Manual

Public-safe guidance for starting MARIA OS Lite autonomous operation. This page intentionally excludes internal deployment topology, secrets, private webhook values, and company-specific rollout procedures.

Required vs Optional

Always-on runtime host
Required

Use a machine or hosted Lite runtime that can stay online for schedules, watchers, and inbound automation.

Authentication
Required

Log in to MARIA-LITE so commands can access the account-bound runtime and integrations.

Notification route
Required

Send failures and escalations to Discord, Slack, or email before enabling unattended loops.

At least one trigger
Required

Choose a schedule, file watch, or inbound webhook trigger so the system has a reason to act.

Custom constitution
Optional

MARIA OS Lite already has a default constitution, so autonomy can start without customization. Add `/constitution` settings when you need organization-specific values and trade-offs.

External GTM SaaS
Optional

The revenue loop can start local-first with `/gtm toolkit`, `/gtm ingest`, and `/gtm autopilot` before HubSpot, Salesforce, Apollo, or Clay are connected.

Public Start Sequence

  1. Bring up a host that can stay online for scheduled and event-driven work.
  2. Log in and set at least one notification route before enabling unattended execution.
  3. Choose one or more triggers: schedule, file watch, GitHub webhook, Slack webhook, or Gmail sync.
  4. Start with self-improvement and observability, then add local-first revenue automation.
  5. Only after the loop is stable should you add external SaaS connectors or higher-risk auto-fix paths.

Quickstart Commands

These examples are public-safe templates. Replace names, queries, and channel targets with your own values.

/login
/notification-router add-discord --name ops-alerts --min-severity error --channel default
/schedule set --name self-improve --cron "0 */6 * * *" --commands "/goal-loop run --source schedule --event-kind schedule.tick --reason \"scheduled self-improve\" --auto-fix"
/watch set --name repo-watch --paths "src-lite,maria-code-lp" --interval 30s --commands "/goal-loop run --source watch --event-kind fs.changed --reason \"repo watch\" --auto-fix"
/gtm toolkit
/gtm ingest --source gmail --query "label:inbox newer_than:14d" --max 25
/schedule set --name revenue-loop --cron "15 */4 * * *" --commands "/gmail watch sync --query \"label:inbox newer_than:7d\" --max 25,/gtm autopilot --dispatch email,/gtm collect remind --dispatch email,/gtm renew draft --lead <leadId>"

What Happens After Startup

Self-Improvement Loop

`goal-loop` dispatches into `self-improve`, which reuses command memory, runs self-recognition, and can attempt low-risk code auto-fix when enabled.

Local-First Revenue Loop

`gtm` can ingest leads, draft outreach, create proposals and contracts, send invoice reminders, and prepare renewals even before external GTM SaaS is installed.