DOMINANT DIRECTOR
[ STATUS: LOCAL-FIRST ARCHITECTURE IN DEVELOPMENT ]

Direct your AI workforce.

Human-approved AI Operating System for Founders. Dom coordinates specialists. Nothing ships without you.

[ Request Sandbox Invite ] [ Apply for Founder Buildout ]
Local-firstHuman approvalEvidence before assumptionsDesktop app in development
Idle · awaiting owner
DOM / COMMAND CENTER · CINEMATIC PREVIEW · NOT A LIVE CONTROL PANEL
Local-first by defaultHuman approval before executionEvidence before assumptionsDesktop app in development

[ MEET / DOM ]

Dom is a command center, not a chatbot.

Dom coordinates specialized AI across the disciplines a founder actually runs: research, engineering, marketing, operations, knowledge, and evidence. Each specialist has a scope. Each output is inspectable. Nothing ships without you.

  • › Research
  • › Engineering
  • › Marketing
  • › Operations
  • › Knowledge
  • › Evidence
  • › Workflow Packs
  • › Human approval
DOMcommandResearchEngineeringMarketingOperationsKnowledgeEvidenceWorkflow PacksHUMAN APPROVAL[ DOM / COMMAND CENTER v0.1 ]Dom coordinates specialists. Nothing executes without owner approval.

[ PIPELINE / PROOF ]

Live Pipeline Proof

Dominant Director now has a verified founder intake pipeline: public forms, secure webhook processing, confirmation emails, admin notifications, and manual review.

[ View the Proof ]

[ ARCHITECTURE / SCHEMATIC ]

LOCAL VAULT/obsidian/01_Directives/02_MemoryLOCAL LLMollama · hermes-8bread-only contextdrafts & templatesTERMINAL SANDBOXplanned desktop runtimeisolated processscratch dir onlyapproval gate ✓readapprove →[ ARCH / v0.1 ]All three components run on local hardware. No egress by default.Owner controls the flow. Nothing writes without explicit consent.

Our architecture is being designed so AI models can read approved local context, draft templates, and eventually operate inside a sandbox-isolated environment with human approval gates.

[ ORCHESTRATION / CONCEPT MAP ]

The owner sits at the center of every loop.

No agent writes, executes, or syncs without you signing off. Logic, build, media, memory, and storage nodes revolve around the operator — never the other way around.

  • › governance before power
  • › awareness before authority
  • › evidence before assumption
CREATOR | OWNERHERMES (LOGIC)CLAUDE CODE (BUILD)MINIMAX (MEDIA)LOCAL VAULT (OBSIDIAN)GITHUB (SAFE)ZERNIO (PLANNED SYNC)Conceptual Orchestration Map — not a live control panel.

[ WORKFLOW PACKS / MODULAR CAPABILITY ]

Install a discipline. Dom runs it your way.

Concept preview. Packs listed below are conceptual — the auto-installer is on the roadmap. Today they're configured manually in the Founder Buildout.

Creator Pack

Content mapping, script drafting, publishing rituals — approved by you before anything ships.

[ concept · manual today ]

Advertising Pack

Audience research, creative variants, and offer testing scaffolds. Human-signed launch.

[ concept · manual today ]

Research Pack

Structured lead research, competitor snapshots, and evidence-backed briefs.

[ concept · manual today ]

Knowledge Pack

Vault templates, capture rituals, and retrieval patterns that keep Dom grounded in your reality.

[ concept · manual today ]

Client Ops Pack

Discovery notes, proposal drafts, and delivery checklists — private by default.

[ concept · manual today ]

Governance Pack

Approval gates, audit trails, and boundaries for what Dom is allowed to do.

[ concept · manual today ]

[ CURRENT V1 WORKFLOW TARGETS ]

What the Founder Buildout configures today

[ 01 ]Local AI + Obsidian workspace setup
[ 02 ]Campaign research and content planning
[ 03 ]Founder/operator knowledge vault structuring
[ 04 ]Lead research and outreach preparation
[ 05 ]Human-approved workflow mapping

[ APPROVAL LOOP / HUMAN IN THE LOOP ]

AI proposes. You approve. Then it acts.

[ 01 ]

Dom drafts

Specialist AI produces a proposal grounded in your vault and evidence.

[ 02 ]

You review

Diff-style view of what will change, what will send, what will run.

[ 03 ]

You approve

Explicit click. No silent execution. No background writes.

[ 04 ]

It ships

Only the approved action runs. Everything is logged for you to inspect.

No autonomous agents. No background execution. Approval is a design constraint, not a setting.

[ CAPTAIN'S LOG / BUILDING IN PUBLIC ]

What's shipped, what's live, what's next.

This board is the honest state of Dominant Director. It updates as modules move from planned to shipped.

Core Architecture
Completed
Constitution, awareness schemas, config templates
Local AI & Vault Config
Available for Buildout
1-on-1 manual configuration of local Ollama/Hermes-8B models, Obsidian directory structures, guided local setup and manual commands
Desktop Client & Sandbox UI
In Development
Electron desktop application, sandboxed script runtime, click-to-approve execution gates
Zernio Sync & Auto-Installers
Planned
Read-only messaging stream, modular Workflow Pack installers, file watchers

[ ROADMAP / FROM SETUP TO OS ]

Today it's a buildout. Tomorrow it's an operating system.

TODAY

Founder Buildout

Manual 1-on-1 configuration of local AI, Obsidian vault, and human-approved workflows on your hardware.

NEXT

Workflow Packs

Installable capability packs (Creator, Advertising, Research, Governance) with owner-controlled approval gates.

HORIZON

Dominance OS

Desktop client, sandboxed script runtime, and Zernio read-only sync — an operating system for founders directing AI.

[ AUDIENCE / PROFILES ]

Built for operators who direct their stack.

High-Leverage Solopreneurs

Time-saving lead sourcing & content mapping without surrendering context to third-party stacks.

Micro-Agencies & Consultants

Privacy-first configurations for sensitive client workflows and multi-brand orchestration.

Privacy-First Operators

Zero recurring SaaS fees using consumer-grade local hardware you already own.

[ FAQ / OPERATOR QUESTIONS ]

Straight answers, no marketing.

[ NEXT / CHOOSE YOUR ENTRY POINT ]

Configure your sovereign workspace.

[ Apply for Founder Buildout ] [ Read the manifesto ]