Skip to main content

Seraph Master Plan

Legacy note: this page now lives under /legacy. The canonical roadmap is docs/implementation/00-master-roadmap.md, and the canonical shipped-status ledger is docs/implementation/STATUS.md.

Seraph is an AI guardian that remembers, watches, and acts. This page is preserved only as historical planning context.

Summary

Current docs split:

  • docs/implementation/ for shipped state and delivery tracking
  • docs/research/ for design and product thesis

The old sections / seasons / batches split is not the live planning surface anymore. This page itself is legacy reference material.

Current Status

This legacy roadmap should be read only as background context. For the live source of truth, use docs/implementation/00-master-roadmap.md and docs/implementation/STATUS.md.

Legend for the checklist column:

  • [x] fully shipped on develop
  • [ ] not fully shipped on develop
WorkstreamChecklistNotes
01. Trust Boundaries[ ]Policy modes, approvals, audit logging, secret redaction, and scoped secret references are shipped; deeper execution isolation and narrower secret-use paths are still left
02. Execution Plane[ ]Shell, browser, MCP, discovery, and visible tool execution foundations are shipped; richer process, browser, and workflow execution are still left
03. Runtime Reliability[ ]Ordered fallbacks, runtime-path primary and fallback overrides, local routing across helper/agent/delegation/MCP-specialist paths, runtime audit visibility including embedding, vector-store, soul-file, and filesystem boundaries, and deterministic eval foundations are shipped; richer provider selection, remaining edge coverage, and broader evals are still left
04. Presence And Reach[ ]Browser, WebSocket, proactive delivery, and the native observer daemon are shipped foundations; desktop presence, notifications, channels, and cross-surface continuity are still left
05. Guardian Intelligence[ ]Soul, memory, strategist, goals, daily briefing, and evening review foundations are shipped; the deeper adaptive guardian layer is still left
06. Embodied UX[ ]Guardian cockpit, goals/settings overlays, operator panes, continuity surfaces, and retirement of the village/editor line are shipped; denser workspace composition and deeper step-level operator control are still left
07. Ecosystem And Leverage[ ]Skills, MCP, and delegation foundations are shipped; stronger workflow leverage and extension ergonomics are still left

Delivery Order

  1. Trust Boundaries
  2. Execution Plane
  3. Runtime Reliability
  4. Presence And Reach
  5. Guardian Intelligence
  6. Embodied UX
  7. Ecosystem And Leverage

Current Shipped Slice On develop

  • policy-controlled tool and MCP access with approval gates, audit logging, secret redaction, and scoped secret references
  • shell, browser, vault, filesystem, goals, and web-search tool foundations with live tool execution in chat
  • ordered LLM fallbacks, health-aware rerouting, runtime-path primary and fallback overrides, local helper, agent, delegation, and MCP-specialist runtime paths, and broad runtime audit coverage
  • deterministic runtime eval harness coverage for fallback routing, local routing, embedding/vector-store/soul-file/filesystem boundaries, browser/sandbox/web-search tool boundaries, observer boundaries, and audit seams
  • browser UI, WebSocket chat, proactive delivery, and a native observer daemon
  • soul, memory, goals, strategist, daily briefing, and evening review foundations
  • skills, MCP integration, and recursive delegation foundations

Workstreams

01. Trust Boundaries

  • not fully shipped on develop
  • focus: make Seraph safer and more governable before expanding autonomy further

02. Execution Plane

  • not fully shipped on develop
  • focus: make Seraph better at doing real work, not just reasoning about it

03. Runtime Reliability

  • not fully shipped on develop
  • focus: routing, fallbacks, observability, evals, and degraded-mode behavior

04. Presence And Reach

  • not fully shipped on develop
  • focus: make Seraph reachable outside a browser tab

05. Guardian Intelligence

  • not fully shipped on develop
  • focus: move from retrieval + heuristics toward richer human understanding and adaptation

06. Embodied UX

  • not fully shipped on develop
  • focus: make Seraph feel alive, legible, and motivating without becoming gimmicky

07. Ecosystem And Leverage

  • not fully shipped on develop
  • focus: compound Seraph through reusable extensions without losing product clarity
  1. Read Development Status for the current shipped vs unfinished view.
  2. Read this file for workstream ordering and current scope.
  3. Read the workstream files under Plan for detailed shipped work, active focus, and remaining work.
  4. Treat the legacy phase docs as background material only.