govard.
Discuss a project
AI-first Desktop ERP Shell

GovardOS

Control-plane architecture for AI-assisted operations

Description & Context govardos.init()
Context
SYS>GovardOS is a desktop control plane for AI-first project operations: tasks, files, local agents, memory, budgets, timelines, and Obsidian context are treated as one operational system instead of scattered tools.
Role
USR>Lead Systems Architect / Fractional CTO
Problem
ERR>The project solves the core problem of AI operations: agent output must remain traceable, governed, connected to real files and tasks, and safe enough for daily product work.
Goals and tasks
  • ■ Unify project management, agent sessions, file context, memory, and execution logs in one desktop shell.
  • ■ Keep every AI-assisted action connected to deterministic artifacts, routes, tasks, or reviewable context packs.
  • ■ Expose operational controls for budgets, token usage, timelines, and project status instead of hiding them behind chat output.
  • ■ Bridge Obsidian knowledge, local files, and agent orchestration without depending on a browser-only sandbox.
  • ■ Make the system useful for production teams: visible state, explicit boundaries, manual review points, and recoverable workflows.
Component Topology

Module Architecture

User interfaces, persistent memory, local integrations, and LLM runtime are connected through a strict data and agent-control layer.

UI / Entities Layer

React 19 + Zustand
Projects & Tasks
Agent Dashboard
Scenario Editor
Memory Browser
Analytics & Telemetry

Data Bridge

Node.js + Prisma ORM
SQLite / better-sqlite3
Project
Task
AgentSession
LLMTrace
Pipeline
ActivityLog
VectorCache
InsightEntry
Scorecard
ContextPack

Agent Fabric

AI Core & Context
Context Kernel
Prompt Compiler
Session Orchestrator
MemoryOS (RAG)
Prompt routing, context assembly, and fact extraction are coordinated as one operational core.

External Runtimes

Local Integrations
Obsidian Vault
Local user knowledge base. Reads and writes Markdown files.
OpenCode Server
LLM daemon with access to Bash terminal and Git commands.
Local FS / Worktrees
Isolated Git worktrees and direct local disk read/write access.

AI and agent functions

GovardOS is not just an AI chat window. It creates a controlled environment where agents receive the right context, work inside a specific project, and leave reviewable results.

Section_01

Agent orchestration control

Coordinates agent sessions, routing, tool access, and project-specific execution boundaries.

Section_02

Memory and context kernel

Combines project memory, file context, and previous decisions before agents receive a task.

Section_03

Governed execution loop

Keeps AI work auditable through explicit payloads, telemetry, review gates, and artifact write-back.

GovardOS Agent Plane
ControlCenter.tsx

Agent System V3

The original goal of GovardOS was deep native AI integration across team workflows and operational tools, not only coding. The Agent System acts as the central control plane for that integration.

AI Modules Ecosystem

15 independent but tightly connected modules covering the full AI-agent workflow: task intake, execution, artifact generation, and long-term knowledge capture.

OpenCode GUI

Primary interface for AI conversations and coding sessions, including messages, file context, and history.

Run Center

Execution center for AI processes with visibility into successful, active, and problematic runs.

Inbox / Activity

System event feed and agent notifications that require user attention or approval.

Scenario Engine

Workflow scenario manager that turns scattered AI work into repeatable execution routes.

Agent Monitor

Real-time monitoring for active AI agents, execution states, metrics, and system events.

Session Fabric

Unified management layer for AI sessions with parent-child dependencies and context inspection.

Skill Catalog

Skill library for agents with installation status, health checks, and tool-access configuration.

MemoryOS

Long-term GovardOS memory for facts, rules, and patterns across session, project, and global scopes.

Context Kernel

Context preview and packaging layer that prepares files and knowledge-base slices before agent execution.

Prompt Compiler

Prompt assembly engine that combines task, context, memory, and constraints into one execution payload.

Agent Arena

Safe test area for comparing agents, checking behavior, and scoring output quality.

Analytics / Telemetry

Observability surface for done/next/blockers, execution metrics, and quality indicators.

Artifacts

Storage layer for generated files, reports, code, and documents ready for user review or reuse.

Pipelines

Multi-step processes with gate checks, delays, retries, and deterministic validation for QA flows.

Cron

Scheduled AI scenarios for reports, project audits, and recurring automated checks.

Key Modules

Five foundational GovardOS subsystems provide deep AI-agent integration across daily workflows: from one control panel to context, memory, and scenario orchestration.

Agent System Panel

A unified control center for routing tasks, managing access, and monitoring active AI sessions across OpenCode and Antigravity. It enables coordinated multi-agent teams instead of isolated chats.

Orchestration Session Fabric
OpenCode Worker
ACTIVE (PID: 8192)
Review Agent
IDLE

OpenCode GUI

The main workspace for desktop agents. It connects directly to the local file system, terminal, and developer tooling so agents can operate with real project context.

Local FS Access Terminal
$ opencode start --workspace ./
> Indexing workspace... (124 files)
> Agent connection established.
_

MemoryOS

A persistent knowledge base that extracts important facts, decisions, and patterns from AI conversations, stores them locally, and supports hybrid vector and full-text search across project history.

Vector DB Entity Extraction
Extracted Fact

"Project uses strict Flatmedia 2026 design system without purple colors."

Context Kernel

The dynamic context assembly core. It builds context packs before model calls, prunes irrelevant data, and keeps agents focused on only the files and knowledge-base facts required for the task.

Context Packs Pruning
src/components/App.tsx 4.2kb
docs/architecture.md 1.1kb
Context Pack Assembled

Scenario Engine

A DAG-based AI pipeline manager that turns scattered agent work into controlled automation chains. It is designed for QA scenarios, code review, and multi-step documentation generation.

Pipelines Automation
Plan
Code
Review

Classic interfaces

The desktop ERP shell combines familiar management tools with local AI agents inside one operational workspace.

01

Operational dashboard

A familiar ERP-style control surface for project health, status, widgets, and priorities.

02

Project and file workspace

Interfaces for tasks, artifacts, local files, and structured project content in one desktop shell.

03

Command and editor surface

Markdown editing, command palette, notifications, settings, and local tool access for daily work.

2026-04-22-dashboard-pm.png
Mission Control: PM Dashboard
Exec Layer
Customizable Widgets

Mission Control: PM Dashboard

Executive dashboard for portfolio status, priorities, budgets, agent activity, and health signals across active projects.

Technical Specification

Zustand Stores
projectStore agentStore analyticsStore
Prisma Models
Project ActivityLog Scorecard
Architecture Layer: Mission Control / Observability
Agentic Pattern

Agentic pattern: managers see AI work as operational state, not as a separate chat transcript.

2026-04-11-project.png
Project Workspace
Delivery
Data-Dense Layout

Project Workspace

A project-level cockpit that keeps tasks, files, progress, status, and execution context in one place for both humans and agents.

Technical Specification

Zustand Stores
projectWorkspaceStore taskStore
Prisma Models
Project Task FileBookmark
Architecture Layer: Project Control Plane
Agentic Pattern

Agentic pattern: each project becomes a bounded workspace where agents can inspect state and return artifacts.

2026-04-12-project-body.png
Project Body Editor
Editor
CodeMirror 6 Engine

Project Body Editor

Editing surface for project artifacts and structured project content with direct links to the surrounding task and file context.

Technical Specification

Zustand Stores
fileStore projectStore
Prisma Models
Project
Architecture Layer: Artifact & Knowledge Workspace
Agentic Pattern

Agentic pattern: agents can reason over the artifact being edited instead of receiving disconnected snippets.

2026-04-25-govardos-projects-dataview.png
Projects Dataview
Aggregation
Zero-Latency SQLite

Projects Dataview

Dense project overview for scorecards, entities, local state, and status signals assembled from stores and SQLite-backed data.

Technical Specification

Zustand Stores
projectStore uiStore
Prisma Models
Project Scorecard
Architecture Layer: Data Visualization
2026-04-25-govardos-task-board.png
Task Board and Agent Sessions
Execution
DnD Interface

Task Board and Agent Sessions

Delivery workspace that connects draggable tasks, active agent sessions, and execution states inside one visual board.

Technical Specification

Zustand Stores
taskStore agentRegistryStore
Prisma Models
Task AgentSession
Architecture Layer: Delivery Workspace
Agentic Pattern

Agentic pattern: task movement, agent state, and review loops stay synchronized.

2026-04-25-govardos-task-board-dataview.png
Task Audit Dataview
Audit
Batch Operations

Task Audit Dataview

Batch operations and telemetry view for checking task groups, run status, and execution traces at scale.

Technical Specification

Zustand Stores
taskStore telemetryStore
Prisma Models
Task LLMTrace
Architecture Layer: Observability Layer
2026-03-31-resource-library2.png
Resource Library: PKM Environment
Knowledge
DCP Compression

Resource Library: PKM Environment

Knowledge workspace for notes, references, memory entries, and context packs used by local agents.

Technical Specification

Zustand Stores
knowledgeStore memoryStore contextKernelStore
Prisma Models
InsightEntry
Architecture Layer: Memory & Context
Agentic Pattern

Agentic pattern: project memory stays editable and reusable inside the same desktop control plane.

GovardOS Project View (Interactive)

GovardOS Project View
Task Management

Active tasks and status signals across Project, Task, PR, and completion metrics.

Task Context

Detailed task description, subtasks, and reference links for the AI agent.

Editing Window

Open file or code workspace with direct agent access to the AST and working context.

Agent Interface

Dialog surface where the AI agent accepts commands, analyzes context, and proposes changes.

Project Status

Project breadcrumbs, statistics, and local bridge connection status.

Node 1: Data Aggregation Pipeline
ipc:context-build

Projects Dashboard Phase 01

A portfolio-level workspace for project status, activity, priorities, and operational context.

State Harvesting & Context Compilation

1
STATE HARVESTING
ZUSTAND
Store extraction:
useProjectStore 14 entities
useMetricsStore
sync
useFilesStore
sync
Zustand State 100% Extracted
2
BUILD PACK
ELECTRON IPC
114,204 / 128k
Tokens in context pack assembly
Markdown payload assembly:
<project_state>
  Title: Projects Dashboard
  Tasks: 42 active
  Recent: ...
</project_state>
Format Markdown (LLM Ready)
3
DISPATCH
SSE STREAM
Orchestrator Agent

Receives compressed context, builds an action plan, and streams updates back to the interface for live display.

Live Log
> Establishing connection...
> Chunk received [24kb]
"Analysis indicates a potential optimization in task delegation..."
CONNECTION
ESTABLISHED
IPC TRIGGER: window.api.invoke('build-context', projectId)
Node 2: FS & Vault Sync Pipeline FS Integration Service

Obsidian Knowledge Hub Phase 02

A local knowledge layer where project notes, decisions, briefs, and references stay connected to execution.

Vault Synchronization Topology

1
FS WATCHER /chokidar
POLLING
Disk Event Captured
EventType: change
TargetFile: /docs/architecture.md
Trigger IPC Dispatch
vault:file-changed
2
AST PARSER /unified.js
REMARK
Extraction Rules
1. YAML Frontmatter Tags Indexed
2. [[Wikilinks]] Graph Edges
3. # Headers Chunking Split
Update Graph Index
3
WRITE-BACK /agent_writer
AGENT I/O
fs.writeFileSync()
New File
Agent_Report_14.md
---
type: agent_output
agent: Orchestrator
status: completed
---

# Refactoring Results
- Analyzed `workspace.ts` for context.
- Extracted 3 pure functions.
- Updated `[[System Architecture]]` graph.
Persisted to Vault
Process Flow

From project state to agent execution

GovardOS turns project data, local files, metrics, and knowledge-base context into a controlled execution packet that an agent can use safely.

1

State harvesting

The shell reads project, task, file, and metric stores before any agent receives context.

2

Context pack assembly

Relevant files, notes, decisions, and task metadata are compressed into an explicit context pack.

3

Agent dispatch

The selected agent receives a bounded payload, runs in a controlled workspace, and streams progress back to the UI.

4

Artifact write-back

Reports, code changes, notes, and decisions are returned to the project workspace instead of being lost in chat history.

5

Review and telemetry

Token usage, status, outputs, and review signals remain visible so the workflow can be audited or retried.

Architecture

Scaling and modularity

The system is split into a React client layer, a secure Node.js bridge, and an isolated AI orchestration layer so a large 100k+ LOC workspace can grow without mixing UI, local-file access, and agent execution concerns.

L1

React UI (Client)

Client interface layer, Zustand state management, and visualization surfaces. It keeps the desktop shell responsive and assembles context packs for agent work.

Client Views State Mgmt Dataviews
L2

IPC & Data Bridge

Secure Node.js bridge controlling file-system access, local SQLite state, and background pipelines. It protects the operating system from uncontrolled agent execution.

Node.js SQLite FS Ops
L3

AI Orchestration

Isolated execution layer for LLM agents with vector search over MemoryOS, prompt compilation, and streamed results through server-sent events.

LLM Runners Context Kernel MemoryOS
Project Conclusion

What this proves

Agent-native architecture

AI work becomes operationally useful when agents are embedded into project state, files, tasks, memory, and review loops instead of isolated chat windows.

Local-first control plane

A desktop shell can keep AI execution close to local artifacts while preserving visibility over context, budgets, and decisions.

Layered governance

Deterministic UI modules, explicit context packs, and review gates make AI-assisted workflows auditable and recoverable.

Production integration pattern

The same structure can be adapted for internal tools, engineering systems, and product operations that need AI acceleration without losing control.

Want to implement desktop AI architecture or local agents inside your product?

Native, secure, deterministic AI pipelines instead of browser sandboxes: files, memory, tasks, agents, and project context working as one control plane.