Home/Architecture

How PrismOS works

A software operating system for autonomous feature delivery. Not a code generator — an operating system that loads project memory, understands your existing product, and activates specialized agents across product, design, engineering, and QA.

◈Infrastructure

Stack

Frontend
Next.js · TypeScript · Tailwind
Motion
Framer Motion
Backend
FastAPI · LangGraph
LLM
Qwen3-235B-A22B
Streaming
Server-Sent Events
Storage
Supabase + Alibaba OSS
Hosting
Alibaba Cloud ECS
Auth
None (hackathon build)
◈Agents

The 7-agent roster

0
Context Analyst
Maps your existing product before any planning begins. Detects stack, models, routes, and integration risks.
1
PM Agent
Translates feature requests into structured requirements. Defines scope, user stories, and MVP boundary.
2
Architect
Owns technical design. Selects stack patterns, defines data models, and API contracts.
3
UI/UX Designer
Defines screen hierarchy, layout, component structure, and every interaction state before code is written.
4
Engineer
Writes production-ready code. Pushes back on over-engineered designs. No pseudocode.
5
QA Agent
Intentionally attacks the implementation. Runs frontend and backend checks. Issues a binding verdict.
6
Release Manager
Resolves conflicts between agents. Issues binding decisions with logged rationale.
◈Pipeline

Workflow — steps 0 through 9

00Memory LoadProject memory injected before discovery begins.
01DiscoveryContext Analyst maps your existing product.
02IntakeFeature classified and structured.
03PM PhasePRD and user stories produced.
04DebateArchitect, Designer, Engineer, QA argue independently.
05ResolutionRelease Manager issues binding decisions.
06UX DesignDesigner produces full interaction spec.
07BuildEngineer writes production code against UX spec.
08QATests run. Frontend and backend checks. Verdict issued.
09ShipFinal package: code, tests, conflicts, memory updated.
◈Design

Key mechanics

Project Memory
Architecture decisions, shipped features, and conflict history persist across runs within a project. Loaded automatically before every new run.
Conflict resolution
Agents are designed to disagree. DISAGREES, PUSHBACK, and SECURITY FLAG markers trigger the Release Manager to issue a binding decision with logged rationale.
Context-first planning
The Context Analyst maps your existing product before any agent proposes a design — preventing incompatible stack assumptions.
Frontend QA
QA runs responsive, accessibility, and UI-consistency checks in addition to functional tests before issuing a SHIPPABLE verdict.
Try the live demo →View on GitHub