Chapter 07 · Operational Blueprint · 2026-04-25

AI Management-Suite

11 AI agents + Nova AI L0 conductor + Petro (human). AI generates, humans decide. The team that runs Nova AI Ventures — and the productized offering Nova AI Ventures sells (Line 04).

1. What AI Management-Suite IS

🤖 AI MANAGEMENT SUITE · OVERVIEW

Collective name: AI Management-Suite (nie “C-Suite” · nie “Heads” · nie “AI team” — ten conflict resolved w delta doc 2026-04-20). Individual titles: “Head of [domain]”.

Composition

11 AI agents — named individuals, each owning a domain
Nova AI (Layer 0 conductor) — master orchestrator in Nova AI Stack Layer 04
Petro Polishchuk (human) — full-stack engineer, contract (joined Feb 24, 2026, ~15k PLN/mo)

Four EAs · one per founder: Klara for Bart · Nina for Maciek · Aurelia for Vincent · Patrycja for Mikołaj. Every founder now has a dedicated executive assistant — plus domain-specific agents on top (Brian for Finance, Dora for Legal, etc. in Mikołaj’s case).

Core principle (non-negotiable #5 from §03):

AI generates. Humans decide.

Every output touching the outside world passes through a human founder. This is the HITL (Human-in-the-Loop) rule — it’s the governance layer that prevents the “taste gap” Willison and Steinberger both identified.

The productized twin (Line 04 · see §04)

Nova AI Ventures’ internal AI Management-Suite is the same system we productize as Line 04 “AI Management Suite” offering. We run ourselves on the system we sell. First visible proof the model works.

2. The 10 Agents · Roster

Each agent has: name · role · reports to · primary stack domain · email. Emails follow first_name.last_name@novaai.ventures convention — agents check mail and respond under HITL supervision.

🤖 AI MANAGEMENT SUITE · 10+1 AGENTS

Reports-to structure · 4 chains, one per founder

Bart’s chain — CEO · strategy, architecture, platform Nova AI L0 (conductor) · Klara Fields (EA)

🌟 Nova AI (Layer 0 conductor)

Not an “agent” but the orchestrator above them

Role: Master orchestrator · cross-agent coordination · routing intent to right agent
Reports to: Bart (strategic direction)
Stack domain: Layer 04 AI Orchestration (§06)
Function: routes incoming work · initiates multi-agent workflows via LangGraph · maintains cross-product context · triggered at handoffs

Klara Fields

Head of Executive Operations (Bart’s EA)

Brzmi: spokojnie · organizacyjnie · “grounded”
Role: Calendar · meeting prep · email drafting · task tracking · weekly summaries · investor & partner relations support
Reports to: Bart
HITL: All external communications reviewed by Bart before send
Email: klara.fields@novaai.ventures

Maciek’s chain — CTO + CISO · architecture, engineering, QA, delivery, security Nina Bridge (EA) · Ada Stone (Arch) · Dexter Forge (SWE) · Vera Cross (QA) · Petro Polishchuk (human)

Nina Bridge

Head of Engineering Operations (Maciek’s EA)

Brzmi: łączy ludzi i tematy (bridges people and topics)
Role: Maciek’s calendar · tech meeting prep · engineering operations · vendor/partner coordination (GCP, Cloudflare, Apple, Google Play)
Reports to: Maciek
HITL: External communications reviewed by Maciek
Email: nina.bridge@novaai.ventures

Ada Stone

Head of Architecture

Brzmi: solidna technicznie · architektura · stabilność
Role: Technical direction · platform decisions · architecture standard · service boundaries · tech stack choices · Nova AI Stack integration points
Reports to: Maciek
Stack domain: Layer 01-06 (architectural authority across entire stack)
HITL: Architecture decisions reviewed by Maciek; all code PRs reviewed before merge
Email: ada.stone@novaai.ventures

Dexter Forge

Head of Software Engineering

Brzmi: builder · hands-on execution
Role: Implementation · hands-on delivery · runtime · deployment · verification · fixing QA-reported defects · adding tests for learned defects
Reports to: Ada → Maciek (engineering chain)
Stack domain: Layer 02 (Docker, Traefik) + Layer 04 (PI, OpenClaw, GitHub) + Layer 06 (Playwright, app surfaces)
Works with: Petro (human) on complex implementations
HITL: All PRs reviewed by Ada before merge; Vera QA before deployment
Email: dexter.forge@novaai.ventures

Vera Cross

Head of QA

Brzmi: QA · checking · verification
Role: Browser validation · Playwright regression · defect surfacing · truth-check real product behavior · GitHub issue creation (even in greenfield)
Reports to: Maciek
Stack domain: Layer 04 (Playwright MCP) + Layer 06 (browser) + Layer 02 (runtime probes)
HITL: Vera can sign off non-blocker issues; blocker defects surface to Maciek decision
Email: vera.cross@novaai.ventures

Petro Polishchuk

Human · Full-Stack Engineer

Role: Complex feature implementation · infrastructure · bridging AI output to production · handling edge cases AI doesn’t
Reports to: Maciek (direct)
Type: Human contract developer, not AI
Joined: Feb 24, 2026
Email: petro.polishchuk@novaai.ventures

Vincent’s chain — CGO · growth, product, marketing, BD Aurelia Chase (EA) · Mira Lane (PM) · Iris Bloom (Mkt)

Mira Lane

Head of Product

Brzmi: product direction · wyznaczanie ścieżki
Role: Product metrics · user feedback · feature prioritization · roadmap · translates POC fields into delivery-ready narrative · tracks product gates
Reports to: Vincent
Stack domain: Layer 05 Admin UI + product-specific dashboards
HITL: All roadmap decisions reviewed by Vincent
Email: mira.lane@novaai.ventures

Iris Bloom

Head of Marketing

Brzmi: marketing · brand · wzrost
Role: Content drafting · ad copy · social posts · SEO · competitor monitoring · brand creation (landing pages, pitch decks)
Reports to: Vincent
Stack domain: Layer 05 + Layer 06 (email, social surfaces)
HITL: All published content approved by Vincent before publish
Email: iris.bloom@novaai.ventures

Aurelia Chase

Executive Assistant for Vincent (Vincent’s EA)

Brzmi: growth · momentum · commercial drive (her flavor channels into supporting Vincent’s growth domain)
Role: Executive Assistant — Vincent’s calendar · meeting prep · email drafting · task tracking · weekly summaries · growth & BD coordination support
Reports to: Vincent
Stack domain: Admin & Platform UI · external integrations (LinkedIn, email, CRM, Gmail, Calendar)
HITL: All external communications reviewed by Vincent before send
Email: aurelia.chase@novaai.ventures

Mikołaj’s chain — CLO + CFO · legal, finance, governance Patrycja Cross (EA) · Brian Grant (Finance) · Dora Hale (Legal)

Patrycja Cross

Executive Assistant for Mikołaj

Brzmi: methodical · precise · legal-aware · detail-oriented
Role: Mikołaj’s calendar · SKS-to-Nova AI handoff coordination · legal/finance meeting prep · document cross-referencing · accounting-office relationship support · weekly summaries · correspondence drafting
Reports to: Mikołaj
Stack domain: Admin & Platform UI · external integrations (Gmail, Calendar, accounting software, document management)
HITL: All external communications reviewed by Mikołaj before send
Email: patrycja.cross@novaai.ventures

Brian Grant

Head of Finance

Brzmi: finance · funding · money logic
Role: Financial reporting · invoice tracking · budget monitoring · compliance checks · token economy pricing · margin structure per product · cost metering · SPV financial modeling · buyout calculations
Reports to: Mikołaj
Stack domain: Layer 05 admin + Layer 03 cost metering + Layer 01 GCP billing
HITL: All financial documents signed off by Mikołaj
Email: brian.grant@novaai.ventures

Dora Hale

Head of Legal

Brzmi: legal · rozsądek · porządek
Role: Platform License legal structure · SPV agreements · IP assignments · per-product legal compliance · T&C/Privacy/Refund templates · regulatory review
Reports to: Mikołaj
Stack domain: Layer 03 license mechanics + Layer 05 admin
HITL: All legal instruments reviewed and signed by Mikołaj
Email: dora.hale@novaai.ventures

3. Reports-to Matrix

🏠 REPORTS-TO · 4 CHAINS

                                   BART (CEO)
                                      │
                                      ├── Nova AI L0 (conductor) — orchestrates all
                                      └── Klara Fields (EA)

              MIKOŁAJ (CLO + CFO)               VINCENT (CGO)              MACIEK (CTO)
                      │                              │                          │
            ┌────────├────────┐            ┌────────┼────────┐            ┌────┼────┬────┐
            │        │        │            │        │        │            │    │    │    │
       Patrycja    Brian    Dora        Aurelia    Mira     Iris         Nina   Ada  Vera Petro
         (EA)    (Finance)  (Legal)      (EA)     (PM)     (Mkt)         (EA)       (QA) (human)
                                                                                     │
                                                                                  Dexter (SWE)

Founder load: 4 founders · 11 AI agents · 1 human engineer + Nova AI L0 = 16 entities total.

4. HITL Rule · Human-in-the-Loop

🕵️ HITL · HUMANS DECIDE

The governance layer. Non-negotiable #5 made explicit:

AI generates. Humans decide.

Every output touching the outside world passes through a human founder. This is the HITL (Human-in-the-Loop) rule — it’s the governance layer that prevents the “taste gap” Willison and Steinberger both identified.

Philosophy: AI is a force multiplier on human judgment · not a substitute. Per Willison: “You own the output. AI doesn’t.”

5. How to Work with the AI Management Team

⚙️ WORKING MODEL · HITL

The end goal is automation, speed, and leverage. We want an ecosystem where humans interact with the AI Management Team sitting on the orchestration layer (OpenClaw). Each AI agent has skills. Skills connect to MCP servers or product APIs. Effective and efficient delivery.

There are two stages for working with the AI Management Team — different scenarios, different rhythms, different expectations.

Stage 1 · Nova AI Ventures Operational Work

Day-to-day running of Nova AI Ventures itself. The AI Management Team supports the four founders on operational matters:

Finance reporting — Brian surfaces weekly P&L, margin analysis, token economy dashboards, anomaly alerts. Mikołaj signs off on financial documents.
Email activity reporting — what happened across Nova AI Ventures inboxes · what needs a human reply · what can be drafted · what can be auto-handled.
Personal assistant support for each founder:
- Klara supports Bart — calendar, meeting prep, drafting replies, weekly summaries, investor/partner relations follow-up.
- Nina supports Maciek — engineering operations, vendor coordination (GCP, Cloudflare, Apple, Google Play), tech meeting prep.
- Aurelia supports Vincent — growth and BD coordination, outreach tracking, meeting prep, content approval cycles.
- Mikołaj does not have a dedicated EA — Brian and Dora cover finance and legal support directly.
Draft responses · suggest replies · summarize threads — each EA reads inbound messages, proposes a draft, surfaces the decision needed from their founder. Human approves or edits, then sends.

Scenario type: mostly human-to-agent — founder asks, agent delivers. Plus trigger scenarios where an agent receives an email addressed to them (e.g., brian.grant@novaai.ventures receives an invoice question) and proactively drafts a response for human review.

Rhythm: daily · asynchronous · low-ceremony · always HITL.

Stage 2 · Project-Related Work

Every active project — from any of our business lines (§04) — gets its own AI team setup. Projects include:

Platform & Tools (L01)
Apps (L02a Nova AI-initiated · L02b co-founded with expert)
Productized SMB Implementation (L03)
AI Management Suite deployment (L04)
Venture R&D (L05)

Project setup

For each active project, we:

Create a dedicated project group chat — typically Slack or Telegram, e.g. #product-snapsell, #product-lumen, #rd-softiq.
Invite relevant AI agents into the channel based on project needs. Common project roster:
- Finance — Brian (pricing, margin, token economics modeling)
- Legal — Dora (SPV, compliance, contracts)
- Project Management — Mira (scope, roadmap, metrics, prioritization)
- Marketing — Iris (brand, copy, assets, campaigns)
- QA — Vera (browser validation, regression, defect surfacing)
- Software Engineering — Ada (architecture) + Dexter (implementation, delivery, runtime)
Human founders join the channel — the sponsor founder plus any other founder whose domain is relevant.

What the project team supports

Inside the project channel, the AI Management Team handles:

Updating the Management Nova AI Ventures platform about project steps — gate progression, evidence captured, blockers, next decisions (auto-surfaced to portfolio dashboard).
Working inside Product Builder — driving the 7-stage pipeline (§05), populating the 11 folders of the product family, managing the gate system G0–G6.
Branding — logo, tone, positioning, brand guidelines, pitch decks, social assets (Iris leads, Vincent approves).
Delivery of greenfield features — brand-new product builds · Product Builder handoff · trio Ada/Dexter/Vera on wave-based execution (see bottom of this section).
Delivery of brownfield features — feature additions on existing products · same trio, same discipline, tied to the product’s GitHub backlog.

Scenario type: team-to-project — multiple agents, multiple founders, one product. Threads, not one-offs.

Rhythm: continuous while project is active · cadence synced with weekly (Wed + Fri) and monthly strategic reviews per §12.

Delivery discipline (wave-based · inside Stage 2)

For Stage 2 work that includes actual building (greenfield or brownfield features), the delivery trio applies wave-based discipline:

Ada — architecture direction, service boundaries, execution standard, resolves technical ambiguity
Dexter — implementation, delivery, runtime, fixes QA-reported defects, adds tests for learned defects
Vera — browser QA via Playwright, regression, truth-checking real product behavior

Unit of execution: Wave → Tasks → Verification → QA → Feedback → Fixes → Next wave.

Required inputs from Product Builder (§05): family definition · build brief · task graph · verification spec · domain/runtime map.

Wave closure criteria (7 requirements): code implemented · local verification passed · staging reachable · Playwright suite passes · no critical regression · Vera signs off · PR/issue trail current.

Full delivery doctrine lives in notes/dexter-delivery-doctrine.md.

End Goal · The Orchestration Stack

The vision that pulls everything together: automate, speed up, leverage. Humans don’t leave the system — they sit at the top, delegating and approving. The AI Management Team sits on an orchestration layer (OpenClaw) that threads skills, procedures, and external tools into a coherent working system.

The 4 Human Founders

Bart · Mikołaj · Vincent · Maciek

delegation · HITL · channel-based

Product Idea

new product · new feature · research task

AI Management-Suite

Klara · Nina · Aurelia · Patrycja · Ada · Dexter · Vera · Mira · Iris · Brian · Dora
+ Nova AI L0 conductor

OpenClaw

orchestration gateway · skills · processes

Skills library reusable capabilities

Procedures & playbooks codified workflows

Product Builder

External LLMs

Claude Design

Stitch MCP

MCP Servers

Product APIs

What this means in practice: when a founder delegates something in an operational context (Stage 1) or a project channel (Stage 2), the request routes through the AI Management Team. An agent picks it up based on domain. The agent uses OpenClaw to access the skills, procedures, and external tools needed (MCP servers, product APIs, etc.). Work happens. Outputs return. Human review per the HITL rule. Iterate.

Every agent carries their own skills, procedures, and MCP integrations. OpenClaw is the common substrate — not a bottleneck. Each agent owns their empowerment domain and grows it over time.

6. Future Extensions

🚀 FUTURE AGENTS · PLACEHOLDERS

Two placeholder agents we plan to activate when the tool-based coverage hits its limits and the portfolio size demands dedicated specialists.

6.1 · Luna Pixel — Head of Design

Status: Placeholder for future 12th agent. Not created yet.
Role (when activated): Head of Design — UX/UI · branding execution · wireframes · design system coordination across products
Reports to: Iris (marketing chain, Vincent final)
Current coverage: MCP Stitch from Google + Claude Code design capabilities handle design at Product Builder stage 4 (Design Generation per §05).
Re-evaluation trigger: Q4 2026 · when tool-based approach hits limits OR when portfolio size demands dedicated designer agent.

6.2 · Theo Lens — Head of Research

Status: Placeholder for future 13th agent. Not created yet.
Role (when activated): Head of Research — heavy-duty researcher agent. Scope includes:
- Market research — competitive landscapes, market sizing, TAM/SAM/SOM analysis, buyer personas, pricing benchmarks
- Feature research — user demand signals, feature competitive analysis, UX pattern research, retention studies
- Domain research — deep dives into specific industries when exploring new L02b co-founded ventures (e.g., wealth management for Lumen, children's publishing for My Story Machine)
- Technology research — emerging tools, MCP ecosystem scans, LLM capability benchmarks, new platforms worth integrating
- Trend research — surfacing signals from external sources (Substack, Twitter, academic papers, industry reports)
Reports to: Bart (research feeds vision + platform strategy) · outputs consumed by Mira (product) and Iris (marketing) in project channels
Current coverage: ad-hoc — research is currently done by founders directly or via one-off Claude/Gemini sessions. No systematic research agent with memory, recurring briefs, or curated sources yet.
Tool empowerment (planned): Perplexity MCP · web scraping MCPs · academic paper MCPs · RAG over curated research corpus · report generation templates · Mira and Iris handoff protocols
Re-evaluation trigger: when new venture ideation rate exceeds founder capacity to research properly · likely Q4 2026 or once 5+ products are active

Why these two specifically: Design (Luna Pixel) and Research (Sage Archive) are the two functions that the current AI Management Team cannot systematically cover. Iris can draft ad copy but she is not a design authority. Mira tracks product metrics but she is not a heavy-duty researcher. Both are upstream functions that feed the whole portfolio — so a weak upstream = a weak portfolio. Adding them closes the biggest coverage gaps.