Human Founders and Roles
Four founders, four chains, four superpowers. Who owns what, who doesn’t touch what, who they work with, and where the lanes stop.
§01 introduced who we are (founder cards). §07 introduced each founder’s AI chain. §08 defines what each founder actually does — with explicit ownership, non-ownership, and shared-responsibility rules.
1. Overview
Four founders · four ownership chains · one company:
👥 FOUNDER ROLES · LOCKED
- Bart · CEO & Chief Architect · 30%
- Nova AI L0 · Klara (EA) — Vision, strategy, platform architect, AI Management-Suite accountability
- Mikołaj · CLO + CFO · 25%
- Patrycja (EA) · Brian (Finance) · Dora (Legal) — Legal, finance, taxation, SPV mechanics, operator equity
- Vincent · CGO + CMO · 22.5%
- Aurelia (EA) · Mira (PM) · Iris (Mkt) — Launch + growth, brand, PRDs, PMF validation
- Maciek · CTO + CISO · 22.5%
- Nina (EA) · Ada (Arch) · Dexter (SWE) · Vera (QA) · Petro (human) — Nova AI Stack, technical delivery, engineering standards, security
| Founder | Role | Stake | AI chain (from §07) |
|---|---|---|---|
| Bart | CEO & Chief Architect | 30% | Nova AI L0 · Klara (EA) |
| Mikołaj | CLO + CFO | 25% | Patrycja (EA) · Brian (Finance) · Dora (Legal) |
| Vincent | CGO + CMO | 22.5% | Aurelia (EA) · Mira (PM) · Iris (Mkt) |
| Maciek | CTO + CISO | 22.5% | Nina (EA) · Ada (Arch) · Dexter (SWE) · Vera (QA) · Petro (human) |
Each 50k PLN capital. Details in §01 section 1 (founder cards) · full governance in §13.
Anti-resentment principle (§03 Value 06): Roles are explicit. Once decided, not renegotiated mid-quarter. “Who did what for which money” conversation never happens — the structure prevented it.
Anti-Resentment Principle + June 2026 Fallback Clause
The Blueprint exists to avoid the situation where we “look into each other’s hands” — who did what for which money. The structure eliminates the conversation before it happens.
June 2026 fallback clause — every founder has a right to exit:
- Anyone can resign in June 2026 (commitment declaration — details in §13)
- Payout = 2× capital contribution
- 50k contribution → 100k payout on resignation
- Clean exit — the person is no longer part of the endeavor
Cross-ref: §13 Governance — June 2026 Commitment Declaration · full legal mechanics.
2. Founder Profiles
🌟 FOUR FOUNDERS · DEEP DIVES
Bart · CEO & Chief Architect
Nova AI L0 · Klara Fields (EA) · 30% stake
Superpower: Vision · AI strategy · platform architect. 15 years building Codibly. Fifteen years identifying opportunities, building companies, designing systems. Sees AI-native era’s shape before others do. Brought the original Nova AI Ventures vision and the venture-building thesis.
Owns
- Nova AI Ventures — overall company direction, narrative, vision
- Prototyping — lots of POCs built via Claude Code + Product Builder (Bart is a heavy prototyper)
- Market ideas — identifying new venture opportunities, spotting patterns
- Nova AI Stack strategy (§06 — architecture, technical direction)
- AI Management-Suite accountability — Bart is responsible for the AI Management Team (§07) · gathers feedback from all 4 founders on how agents perform in their domains · coordinates improvements · new skills · new MCP servers · new procedures · across the full suite
- Product Builder — methodology, gate decisions via 4-founder consensus
- Strategy for launching new companies — new SPV opportunities
- Working with other people to open new adventures — partnership, co-founding exploration
- Investor & partner relations — Google partnership, future funding
- Creates processes, procedures, and toolings — implementing AI Management processes and procedures · building the substrate that makes the AI Management-Suite and OpenClaw orchestration layer (§07) actually work together as a coherent system
- Keeper of non-negotiables — enforcing the 7 principles from §03 across every decision (not only the consulting boundary but the full set: leverage test, operators-from-day-1, humans-manage-AI, frameworks over execution, etc.)
Works with
- Works with Maciek on delivery and all technical platform topics and aspects — Product Builder, architecture, Nova AI Stack, infrastructure, engineering standards
- Works with Vincent on PRDs, products, marketing, growth strategy, brand direction
- Works with Mikołaj on finance, legal, SPV structures, governance, financial modeling
Does NOT do
- ❌ Write code (AI writes code; Bart does prototyping/POCs)
- ❌ Day-to-day operations of any child company (but happy to consult — open to advisory role on SPVs)
- ❌ Legal paperwork
- ❌ Marketing execution
- ❌ Growth execution
Other obligation
Codibly earnout throughout ~Q1 2027 · silent partner on paper until early 2027 (see §01 + §13)
Mikołaj · CLO + CFO
Patrycja (EA) · Brian Grant (Finance) · Dora Hale (Legal) · 25% stake
Superpower: Legal + network + finance. Partner at SKS (one of Poland’s largest law firms). Corporate & company law specialist. Structures deals, governance, operator frameworks, IP, SPV mechanics. Network opens doors.
Owns
- All legal matters — shareholder agreements, HoT, SPV creation, legal templates, IP assignment, compliance, risk reviews
- All financial matters (CFO) — financial reporting, budget oversight, financial modeling
- Taxation & tax optimisation — corporate tax strategy, VAT handling, cross-border tax considerations (SPVs in different jurisdictions), R&D tax credits, founder/operator tax structuring
- Relationship management with accountant’s office — external accounting partner coordination
- Operator equity structures — sweat-equity, phantom shares, buyouts, non-performance/Alignment Review procedures
- Continuous improvement of his AI team (Patrycja + Brian + Dora) — expanding capabilities, new legal and finance MCP servers, regulatory updates, EA coverage
- Platform License Agreement negotiation (§06) — per-SPV license terms
- Silent-partner mechanics — Bart’s Codibly earnout period governance
- Financing structures — deal negotiations support
Does NOT do
- ❌ Build products
- ❌ Run marketing campaigns
- ❌ Manage AI infrastructure
Other obligation
SKS partnership (day job as senior law-firm partner)
Vincent · CGO + CMO
Mira Lane · Iris Bloom · Aurelia Chase · 22.5% stake
Superpower: Growth hacking · brand design · D2C · GTM execution. Two-time founder (ex-CEO Lucky Duck, Cobojo). Finds demand before product exists.
Owns
- Launch + growth of every child company — SPV go-to-market motions
- Initial operator for internally created brands — Vincent is the default day-1 internal operator for Line 02a Nova AI-initiated apps, holding the product through the early launch phase until an external operator is signed at G4–G5 (§05 · §09)
- Brand positioning — Nova AI Ventures + per-product (brand design shared with Bart — both contribute)
- Product Requirements Documents (PRDs) (shared with Bart — both Bart and Vincent draft PRDs)
- Acquisition funnels — paid media, content, referral loops
- PMF validation — “demand side” — proving people pay
- Portfolio-wide sales motion — commercial coordination
- Marketing AI agents feedback loop — communicates with Bart on how to improve Mira + Iris + Aurelia from a marketing/growth perspective · feedback flows into Bart’s AI Management-Suite accountability cycle (§07)
Does NOT do
- ❌ Write code
- ❌ Structure legal entities
- ❌ Manage AI infrastructure
Other obligation
Lucky Duck wind-down
Maciek · CTO + CISO
Nina Bridge · Ada Stone · Dexter Forge · Vera Cross · Petro (human) · 22.5% stake
Superpower: Technology + very high technical expectations, especially in the agentic area. CEO Yameo.eu. Cloud, enterprise architecture, hands-on engineering.
Owns
- Nova AI Stack (§06) — architecture, technical standards, implementation chain
- Overseeing technical delivery — code quality, architecture decisions (oversight role, not doing)
- Executing delivery — long-running delivery execution via Ada (architecture) + Dexter (implementation) + Vera (QA) based on deliverables from Product Builder (Bart’s domain, §05)
- Overseeing human software engineer(s) — ensuring Petro (and any future engineers) deliver by effectively managing their AI agents team
- Engineering team — Petro (human) + AI chain (Ada, Dexter, Vera) via Ada
- Docker/Kubernetes infrastructure — new SPV spin-up in 1-2 weeks
- Engineering non-negotiables — security, observability, deployment, testing, code quality (§06.4)
- Reusability discipline — every product more reusable over time
- Continuous improvement of his engineering team (Nina + Ada + Dexter + Vera + Petro) — new engineering MCP servers, patterns, tools
- Next real technical hire — when/if needed
Does NOT do
- ❌ Design marketing campaigns
- ❌ Handle legal or financial structuring
Other obligation
Yameo sale (active sale + earnout) — currently most operationally committed of three invited shareholders
3. RACI Matrix · 13 Activities
R = Responsible · A = Accountable · C = Consulted · I = Informed · S = Shared
🎯 RACI · RESPONSIBILITIES
| Activity | Bart | Mikołaj | Vincent | Maciek |
|---|---|---|---|---|
| Identify new venture opportunity | S | S | S | S |
| Validate market demand | S | S | S | S |
| Build POC (shared · anyone can prototype · Mikołaj on-paper) | S | S | S | S |
| Build MVP · Product Builder (outputs PRD + engineering plan) | S | I | S | S |
| Build MVP · software delivery (execution) | C | I | C | R |
| Launch & acquire first users | C | I | R | C |
| Recruit external operator / CEO | S | S | S | S |
| Structure SPV & legal docs | C | R | I | I |
| Maintain Nova AI Stack | C | I | I | R |
| Manage AI Management-Suite (Bart R overall, all consulted) | R | C | C | C |
| Financial reporting & compliance (all 4 shared) | S | S | S | S |
| SMB subscription sales (Line 03) | S | I | I | S |
| Design · branding (part of MVP build) | I | I | C | C |
Notes on RACI interpretation:
- Identify opportunity · Validate demand — shared across all 4. For Validate Demand, the person bringing the product owns the call; others are consulted.
- POC building — shared + optional. Anyone can build POC. Bart does lots of prototyping. Mikołaj can build on-paper POCs (legal structures, financial models, operator frameworks).
- Build MVP · Product Builder — shared Bart/Vincent/Maciek because the Product Builder methodology (§05) drives the PRD + engineering plan. This is the front-of-the-delivery, not the execution.
- Build MVP · software delivery — Maciek is Responsible; his AI team (Ada architecture · Dexter implementation · Vera QA) executes against the PRD + engineering plan from Product Builder.
- Manage AI Management-Suite — Bart is Responsible overall (he owns suite strategy); Mikołaj, Vincent, Maciek all Consulted on chain changes.
- Maintain Nova AI Stack — Maciek is Responsible for execution; Bart is Consulted on architecture direction.
- Financial reporting — all four founders Shared. Mikołaj primary (CFO), but visibility is portfolio-wide.
- SMB subscription sales (Line 03) — Bart + Maciek Shared (technical + platform-driven motion); Mikołaj + Vincent Informed.
- Design · branding — driven by the operator running the project. All 4 founders are advisors only.
- Operator recruitment — all 4 founders Shared (S) because networks differ; sponsor Responsible for coordination (see section 4).
Agree to disagree · support the owner. When an activity is Shared or when one founder owns a call that others disagree with, we default to supporting the person closest to the decision. Per Jeff Bezos: “I can disagree with you, but if I am disagreeing with you, I will do everything I can to make sure you’re successful — because I am trusting your guts in making this decision.” If a founder takes ownership of a call we disagree with, we still support it. This belongs in our core values (§03) — flagged for addition.
RACI legend reminder
- R — Responsible: does the work, owns the deliverable
- A — Accountable: final sign-off authority (one A per row, usually)
- C — Consulted: two-way input before decision
- I — Informed: one-way update after decision
- S — Shared: multiple founders co-own (Nova AI-specific extension to classic RACI for founder-level work)
4. Shared Responsibility · Operator Recruitment
🌐 NETWORKS · WHO WE KNOW
Finding external operators is NOT Vincent’s isolated job. It is a mutual superpower — all 4 founders leverage their networks.
Networks per founder
| Founder | Network strength |
|---|---|
| Bart | Tech operators · founders · Codibly alumni · investor network · corporate connections across tech industry |
| Mikołaj | Corporate operators · C-suite executives · SKS clients · corporate legal and finance networks · accounting firms · regulatory contacts |
| Vincent | D2C operators · growth leaders · Lucky Duck + Cobojo alumni · marketing agency corporate contacts · media buying networks |
| Maciek | CTO-type operators · technical co-founders · Yameo alumni · enterprise IT corporate contacts · cloud vendor networks |
Per-product ownership: Sponsor founder owns coordination (usually Bart or Vincent depending on line). But sourcing, qualifying, and selling candidates happens across all 4.
Shared CRM · backed by MCP
A simple shared CRM — backed by MCP servers — maintains the portfolio-wide operator longlist, candidate pipeline, and corporate contact network. Aurelia (Growth/BD coordination via Vincent’s chain) and each founder’s EA (Klara · Nina · Aurelia · Patrycja) feed updates into it. Everyone sees the same pipeline state. No more silos · no more “who was talking to whom” confusion.
Mechanism
- Weekly scoreboard (§12) includes operator longlist status per product
- Monthly strategic review reviews pipeline · adjusts ICPs if gaps appear
- Shared CRM / outreach tracker — Aurelia (AI growth agent) maintains candidate database across portfolio
Cross-ref: Operator-Search Template (§05 — 4 day-1 artifacts) must be completed before G4 MVP Build approval.
5. Consulting Contradiction · Resolved
📝 CONSULTING · RESOLVED
None of the 4 founders does bespoke client work. This is the resolution of the “consulting contradiction” flagged in external feedback (2026-04-20 delta doc).
How it works
- Any external engagement must pass Venture R&D Filter (§03 section 5 — 4 tests)
- Max 2 concurrent engagements (§04 Line 05)
- Bespoke client code with no reusable asset = fail = NO
- If an engagement passes the filter, it’s Venture R&D (Line 05), not consulting
Who runs Venture R&D engagements
- Typically Bart + Maciek (technical depth)
- Mikołaj for legal engagements
- Vincent only if GTM/brand-aligned engagement
- Billing structure: Venture R&D engagements can be billed hourly or project-based — whichever structure fits the engagement. What makes it Venture R&D (not generic consulting) is the filter: the engagement must pass at least one of the 4 tests in the Venture R&D Filter (§03) — extract a reusable tool, validate a product hypothesis, deploy something productized, or plant an equity seed. The asset that flows back to Nova AI Stack is the non-negotiable, not the billing structure.
6. Role Ownership Rule · Anti-Resentment Structure
🤝 AGREE TO DISAGREE · HOW WE ALIGN
Once decided, roles are not renegotiated mid-quarter.
Why this matters
- 4 founders with overlapping talents will drift into each other’s lanes without discipline
- “I did X, Vincent did Y, but we got paid the same” = the resentment trigger
- Explicit ownership eliminates the conversation before it starts
Review points
- Roles may be revised at quarterly strategic review (§12 Cadence)
- Non-performance triggers Alignment Review procedure (§13 Governance — renamed from “non-performance”)
- June 2026 commitment declaration (§13) locks roles for the next stage
If something’s off: raise at weekly scoreboard · decide at monthly strategic review · formalize at quarterly.