Files

T

phptits 0d6cd37579 DevOS v1 + Phase 2: unified resource model, infra ops, website deployment, AI chat ops

- Monorepo: NestJS API (Fastify) + React web (antd/ProComponents) + shared packages
- PostgreSQL/Prisma (unified resources, relations graph, audit, events, jobs)
- Auth/RBAC/workspace isolation, credential vault (AES-256-GCM)
- Servers/SSH, Docker discovery & lifecycle, Job Center
- Websites & deployments (git provider credential clone, env, health verification)
- Domains/DNS (Cloudflare adapter), certificates (TLS probe), monitoring
- Automation (cron/event/webhook HMAC + notifications), AI Gateway, MCP (29 tools)
- AI chat window (LLM function-calling + rules fallback, SSE streaming, approvals)
- Notes: Vditor WYSIWYG markdown editor, non-blocking autosave
- Tests: 35 unit/security tests; UI audit clean (desktop+mobile, deep links)

2026-09-10 06:35:55 +00:00

2.1 KiB

Raw Blame History

DevOS v1 Product Requirements Document

1. Product Definition

DevOS is a Developer Work OS: a unified workspace for servers, websites, domains, code, databases, email, notes, tasks, documents, monitoring and automation, with AI as an operational Agent rather than merely a chat interface.

2. Core Product Model

The platform is organized around four primitives:

Resource + Action + Event + Agent

Resource: everything managed by DevOS.
Action: an operation performed against a resource.
Event: a state change or external signal.
Agent: observes resources, plans actions, executes through tools, verifies outcomes and reports.

The central architectural principle is the Unified Resource Model.

3. Primary Users

Individual developers
Small development teams

4. V1 Scope

V1 focuses on Infrastructure OS capabilities:

Server
Docker / Containers
Website
Domain
Deployment
Monitoring
Authentication, Workspace, Resource, Permission and Audit foundations

5. V2 Scope

Developer OS:

GitHub / GitLab / other Git providers
Projects
Tasks
Notes
Documents
Email

6. V3 Scope

Automation OS:

Event Bus
Workflow Engine
Cron
Webhook
Notifications

7. V4 Scope

AI OS:

Resource Discovery
Planning
Tool Calling
Execution
Verification
Memory
Approval

8. Representative User Journey

“Deploy my blog to the Tokyo server, use Docker, configure blog.example.com and enable HTTPS.”

The intended Agent flow:

Find Project and Repository
Find target Server
Check Docker
Clone repository
Build image
Run container
Configure reverse proxy
Configure DNS
Obtain SSL
Health check
Return an action log and result

9. Non-Goals

Reimplementing Git
Reimplementing SMTP
Building a Kubernetes control plane in V1
Building a full Notion replacement in the first release
Starting with microservices

10. Product Success Criteria

A developer can manage the core infrastructure lifecycle from one workspace, while resources remain related and discoverable enough for later automation and AI operation.

2.1 KiB Raw Blame History