This file is the single source of truth for booting, running, and understanding the Origin OS development environment.
See the CHANGELOG for release history.
Origin OS is a modular platform for creating, managing, and publishing digital artwork through a structured creative pipeline.
It combines a dashboard-based creative interface, a Node.js + MongoDB backend, and an AI-powered generation system to help creators produce and distribute digital work from a single environment.
Origin OS is designed to function as a creative operating system rather than a single-purpose application.
Origin OS currently provides several foundational systems:
Secure session handling using access and refresh tokens with HTTP-only cookies.
Artwork creation automatically saves draft state so creative sessions can continue across logins.
Images are generated through the backend API and stored through the media pipeline.
User dashboards hydrate from live backend data rather than static placeholders.
Origin OS is designed to support multiple creator workflows including artwork generation, collections, publishing, and branding.
origin_os/
│
├─ css/ # UI styles (per module)
├─ js/ # Frontend logic & shell
├─ img/ # Icons, avatars, branding
├─ md/ # Notes & internal docs
│
├─ origin-os-api/ # Backend API (Express + MongoDB)
│ ├─ src/
│ │ ├─ routes/ # API routes
│ │ ├─ models/ # MongoDB models
│ │ ├─ middleware/ # Auth + guards
│ │ ├─ Utils/ # JWT, cookies, helpers
│ │ └─ server.js # API entry point
│ └─ package.json
│
├─ *.html # Frontend pages (dashboard, create, etc.)
├─ Dockerfile
├─ docker-compose.yml
└─ package.json # Root tooling / future scripts
Origin OS follows a layered architecture designed to keep the system modular, inspectable, and evolvable.
┌──────────────────────────┐
│ Frontend │
│ Origin OS Shell (HTML) │
│ CSS + JavaScript UI │
└────────────┬─────────────┘
│
│ HTTP Requests
▼
┌──────────────────────────┐
│ Express API │
│ origin-os-api server │
│ │
│ Auth Routes │
│ Artwork Routes │
│ Image Routes │
│ Stats Routes │
└────────────┬─────────────┘
│
│ Middleware Layer
▼
┌──────────────────────────┐
│ Auth Middleware │
│ JWT verification │
│ Cookie handling │
│ Request guards │
└────────────┬─────────────┘
│
▼
┌──────────────────────────┐
│ Data Layer │
│ │
│ MongoDB Database │
│ Artwork documents │
│ User accounts │
│ Media file references │
└────────────┬─────────────┘
│
▼
┌──────────────────────────┐
│ Media Storage │
│ Generated images │
│ Stored assets │
└──────────────────────────┘
Frontend
- HTML
- CSS
- JavaScript
- Live Server (development)
Backend
- Node.js
- Express
Database
- MongoDB
Authentication
- JWT
- HTTP-only cookies
Future Platform
- React / Vite
- Cloudflare Pages
- Docker deployment
Origin OS uses an asynchronous workflow for image generation and retrieval.
- User requests image generation from the frontend
- API creates or updates a draft artwork record
- Image generation service produces the image
- Image is stored in the media layer
- Artwork record is updated with the image reference
- Frontend retrieves the image through the protected media API
Example retrieval:
const imgRes = await fetch(`${API_BASE}/api/images/${imageFileId}`, {
headers: { Authorization: `Bearer ${token()}` },
credentials: "include",
});
const blob = await imgRes.blob();
img.src = URL.createObjectURL(blob);Origin OS functions as a headless CMS and publishing engine for creators like Dream Agent.
This means Dream Agent website content can be updated through Origin OS without directly editing the website codebase itself.
- Artwork publishing
- Collection updates
- Release descriptions
- Website content updates
- Future creative asset management
Origin OS serves as the content management layer between internal creator workflows and the external Dream Agent website.
Project documentation is organized as follows:
| File | Purpose |
|---|---|
| README.md | Project overview |
| DEVELOPMENT.md | Local development setup |
| ARCHITECTURE.md | System architecture and internal design |
Active development is currently focused on:
• asynchronous AI artwork generation
• modular dashboard systems
• persistent creative workflows
• scalable media pipelines
Upcoming evolutions include:
- React / Vite frontend
- Async generation worker pipeline
- Plugin-style module architecture
- Cloud deployment
- creator publishing workflows
- collection systems
GitHub
https://github.com/courthub74/origin-os
Origin OS is intentionally:
- Modular
- Inspectable
- Evolvable
Origin OS is currently in active development.
Core authentication, image generation workflows, and modular dashboard architecture are functional.
Future iterations will expand the platform toward a full creative operating system for digital creators.
Origin OS is designed as a modular system and will continue evolving.
Upcoming architecture improvements include:
- React / Vite frontend
- Cloudflare Pages deployment
- API versioning strategy
- Role-based dashboards
- Plugin-style module system
If something breaks → start with this README.
If something grows → update this README.
This file defines the current architecture and development expectations for Origin OS.
