Scheduled jobs from Chat (v1 — gated)

Status

Enabled on this fabric (ops dogfood): MCP schedule gate ON + minute tick timer.
Ask in OmniLore mode (not Auto alone). The agent should call schedule_create and return a schedule_id and next_run_at.

Broader multi-tenant member policy is still maturing — treat this as gated and confirm with your operator if you are unsure you are allowed to schedule.

What you can ask

> “Every day at 2:00 AM America/Chicago, leave me a short fabric status note.”

The agent should call schedule_create and return:

• schedule_id (looks like sch_ + hex)
• next_run_at (UTC)
• Confirmation of job kind and timezone

Job kinds (v1)

| Kind | Result |
|------|--------|
| workspace_note | Markdown under your workspace schedules/<id>/ |
| personal_brief | Personal daily brief script for you only |
| agent_prompt_capped | Short Ollama answer (allowlisted model, no tools) |
| frontier_digest_capped | Timed FRONTIER DRAFT (live web cites + quality gate). Not automated deep research; not product SoT. Ops-only create during member beta. Members who want deep research: use a personal Deep Research Chat agent (tools + challenge dual), not this job kind. |

Honesty (frontier digests)

• Output is labeled FRONTIER DRAFT — NOT Source of Truth · NOT tribal.
• schedule_run_now ok means the run finished (an artifact may exist).
• quality_ok means enough relevant citations after the quality gate.
• Thin web results → fail closed (quality_ok=false); still a draft for review, never fabric truth.
• Never market timed digests as automated deep research.
• Prefer narrow queries with distinctive cores (e.g. local-first multi-agent fabric) over long marketing bags; the system may rewrite SERP to core terms but does not lower the quality bar.

Not available (v1)

• Free-form shell, forge write, or unrestricted ops on a timer
• Guaranteed message popup inside Chat at fire time
• Asking the model to “remember” without a successful schedule/tool write
• Arbitrary Mattermost channels for every member (notify is ops-oriented / allowlisted)
• Uncapped autonomous agents with full MCP tool bags on a timer
• Member self-serve create of frontier_digest_capped while ops-only beta is on

Delivery

| Path | Notes |
|------|--------|
| Workspace files | Always: workspaces/<you>/schedules/<schedule_id>/ (and LATEST when produced) |
| Optional notify | Mattermost-style notify only when policy allows (ops allowlist) |
| Chat thread popup | Not yet — open Chat does not auto-ping at 2 AM |

List / pause / cancel

| Ask | Tool (under the hood) |
|-----|------------------------|
| “List my schedules” | schedule_list |
| “Pause / resume …” | schedule_pause / schedule_resume |
| “Cancel schedule sch_…” | schedule_cancel |
| “Run this one now” | schedule_run_now (when allowed) |

Schedule ids must look like sch_ + 16 hex characters. Odd paths or free-form ids are rejected.

Related

• Features: FEATURES_USER.md
• Project continuity: PROJECT_INTENT_POSTURE_AND_CONTINUITY.md
• Limitations: KNOWN_LIMITATIONS.md
• Chat guide: USER_GUIDE_CHAT_OMNILORE_AI.md

End.