Stackmates
Each venture in the Mycelium follows the Business Ideas Template. This one is the platform the others run on.
Persuasion Loop Status
| # | Asset | Status | Location |
|---|---|---|---|
| 1 | Business Idea | DONE | This page |
| 2 | Pitch Deck | TODO | /pitch-deck |
| 3 | Landing Page | TODO | /landing-page |
| 4 | Sales Pitch | TODO | /sales-pitch |
| 5 | Presenting | TODO | /presenting |
| 6 | Selling | TODO | /selling |
| 7 | Feedback | TODO | /feedback |
1. Title & One-Line Description
- Business name: Stackmates
- Domain: stackmates.io
- One-liner: Enterprise SaaS where humans and AI agents operate through the same business logic — a phygital architecture for coordinating biological and digital workers.
2. Problem & Why Now
-
What system is broken?
- Business tools treat AI as an add-on, not a first-class operator alongside humans
- Internal tools fragment across departments — no shared domain model
- Agent orchestration is ad-hoc scripts, not structured coordination
-
Who feels the pain most?
- Operations teams managing workflows that cross human and AI boundaries
- Founders building AI-native businesses who need structured coordination, not chatbot wrappers
-
Why urgent now?
- AI agents are production-ready but lack infrastructure to operate as team members
- A2A (agent-to-agent) protocols are emerging — first movers define the coordination layer
- The 2027 window — ~2 years before AI + data enters a self-reinforcing loop
-
Why this approach?
- Hexagonal architecture means the domain layer is pure — same business logic serves UI, API, and agent protocols
- Commissioning model from factory engineering gives quantified maturity, not guesswork
3. System Map & Opportunity
-
Universe: AI-native business operations platforms
-
Slot: The coordination layer where human intent meets agent execution
-
Network:
- Digital: AI agent teams, A2A protocol, shared domain model
- Physical: DePIN integration path for real-world asset coordination
3.1 Open Protocol
Stackmates is designed as public coordination infrastructure, not a closed productivity app.
| Requirement | Why It Matters | Implementation Signal |
|---|---|---|
| Shared model | Humans and agents must reason over the same entities | One domain model across UI, API, and A2A |
| Verifiable state | Trades and decisions need auditability | Commissioning stages + measurable maturity |
| Portable context | Teams should compose across ventures | Reusable schemas, repositories, and use cases |
| Question-first operation | Better questions produce better decisions | Links to Questions and Problem Solving |
This makes Stackmates usable as a build substrate for many ventures in the same digital mycelium.
Tight Five Biz Dev Idea
| P | Biz Dev Focus | Stackmates Definition |
|---|---|---|
| Principles | What truth guides demand? | Human + AI operations need one shared business logic to scale safely |
| Performance | How do we know it works? | Commissioning maturity, shipped workflows, and external user outcomes |
| Platform | What do we control? | Shared domain model, APIs, orchestration, and reusable workflow primitives |
| Protocols | How do we coordinate growth? | PRD -> build -> commission -> promote to shared standard |
| Players | Who creates value? | Operators, builders, AI agents, device actors, and venture teams |
Shared PRD Mycelium
Stackmates is the shared PRD execution substrate for all mycelium windows.
| Layer | Source |
|---|---|
| Shared PRD Surface | Open PRDs |
| Primary PRDs | Sales CRM & RFP + Sui Wallet Safety Patterns |
| Window Pattern | Ventures use shared capabilities with different presentation and GTM |
| Reuse Goal | Move validated venture workflows into platform-level primitives |
4. Solution & Product Snapshot
-
Plain-language description: A platform where you define business operations once and both humans (via UI) and AI agents (via API) execute them through identical data paths. One domain model, multiple interfaces.
-
Core job to be done: "When I have operations that need both human judgment and AI execution, help me coordinate them through one system instead of gluing tools together."
-
Key differentiator: Phygital-first — AI agents are not bolted on, they share the same ports, use cases, and data paths as human users from day one.
DePIN to Robotics
The long path is not "software only." It is software + sensors + robots coordinated through one business graph.
| Phase | Device Role | Stackmates Role |
|---|---|---|
| Observe | Fixed DePIN devices collect state | Ingest and structure signals |
| Act | Robots execute physical tasks | Route intent to execution workflows |
| Coordinate | Human + AI + robot teams trade work | Enforce roles, incentives, and feedback |
See Robotics Industry for the market layer and Games for incentive design.
5. Architecture
Nx monorepo. 168K lines. 2,829 files. 50 Nx projects. 390 PRs merged. Solo architect and developer.
10-layer hexagonal architecture — inner layers never import outer:
| Layer | What | Scale |
|---|---|---|
| 0. Orchestrate | AI agent team system — 5 teams, meta-orchestrator, DB-native planning | 17 rules, 12 hooks, 15 plan templates |
| 1. Define | Pure domain types, ports, DTOs — zero dependencies | 86 modules |
| 2. Store | Drizzle ORM schemas across 17 domain modules | 163 schema files |
| 3. Access | Repository pattern with standardised query optimisations | 67 repositories |
| 4. Compose | Use cases + composition root — single wiring point | 78 use cases |
| 5. Think | Client-safe AI algorithms + workflow orchestration | 13 algorithms, 11 workcharts |
| 6. Expose | REST API + A2A intent protocol + server actions | 33 API routes, 49 server actions |
| 7. Render | Next.js App Router with RSC/client split | 71 pages, 287 components |
| 8. Prove | Playwright E2E + A2A contract tests | 78 specs |
| 9. Learn | Validated feedback loops — plan retros feed template improvements | Automated connectors |
The Orchestration System
Designed from dairy factory commissioning — each data entity progresses through 10 discrete states from idea to fully commissioned (schema, migration, data, repository, server action, CRUD UI, ETL pipeline, A2A API, E2E tests, monitored).
- 5 AI agent teams (meta/orchestrator, UI, intelligence-engine, platform-engineering, marketing) operating in isolated git worktrees
- DB-native planning — all plan state lives in PostgreSQL, not files
- 15 plan templates standardise work the way Nx generators standardise code
- Cross-team composition — one plan assigns tasks to multiple teams
- Data footprint analysis algorithm scores all 208 tables by commissioning maturity
Agency Layer
Client-safe library (runs in browser or server, zero infrastructure dependencies):
- 13 algorithms: data-footprint analysis, sales forecasting, RFP type detection, content strategy, decision-making, investment analysis
- 11 workcharts: sales RFP workflow, marketing strategy, marketing loyalty, slide deck generator
- A2A protocol: agent-to-agent intent API through
/api/intents/routes
Tech Stack
TypeScript, Next.js 15 (App Router/RSC), Drizzle ORM, PostgreSQL (Supabase), Nx monorepo, Playwright, Vercel AI SDK, TailwindCSS v4, TanStack Table/Form, Clerk auth, Convex (real-time), Sui blockchain (Move)
6. Commissioning Status
- Current stage: Active development
- 208 tables scored, average maturity 3.29/10
- Top 7 entities at 6.2–6.6 (need UI, ETL, A2A, E2E to reach 7.0+ commissioned threshold)
- 12 plans completed, 4 active, 96% task completion rate
| Maturity Band | What's There | What's Missing |
|---|---|---|
| 7.0+ (commissioned) | Full path: schema through monitored | None yet — top entities approaching |
| 5.0–6.9 | Schema, migration, data, repository, server actions | CRUD UI, ETL, A2A, E2E |
| 3.0–4.9 | Schema, migration, repository | Server actions, UI, everything above |
| 1.0–2.9 | Schema defined | Everything above |
7. Business Model Economics
- Who pays: Teams and founders running AI-native operations
- Who earns: Platform takes margin on coordination, not compute
- Value capture: The domain model is the moat — switching cost is the business logic, not the UI
8. Team & Credibility
- Founder: Matt Mischewski — CV
- Background: Mechanical engineering → factory commissioning → telecom routing → healthcare ETL → crypto/AI platform. Same pattern every time: unify siloed data, build reusable pipelines, surface decisions.
- Key relationships: Mycelium ventures share the platform
9. Key Risks
| Risk | Mitigation |
|---|---|
| Solo developer | Commissioning model makes progress measurable; AI agent teams multiply output |
| Pre-revenue | Platform serves own ventures first — berleytrails, prettymint |
| A2A protocol still emerging | Built on intent-based API that works with or without standardised A2A |
10. The Ask
- Current need: Reach 7.0+ commissioning on top 7 entities, ship first external user
- Not raising yet — proving the coordination layer works on own ventures first
10.1 Fair Trade Game
Every workflow is a repeated game. If incentives are unfair, quality decays. If incentives align, trust compounds.
| Game Question | Stackmates Primitive |
|---|---|
| Who is playing? | Actor model (human, AI, service, device) |
| What is being traded? | Tasks, data, decisions, and outcomes |
| What is proof of contribution? | Commissioning state + execution artifacts |
| How is value settled? | Performance metrics and compensation rules |
| How do players improve? | Closed feedback loop into standards |
Goal: turn collaboration into measurable fair trades that produce both fulfillment and outcomes.
Connection to Mycelium
| Metric | Score | Notes |
|---|---|---|
| PURPOSE | 9/10 | Trains community — building with good people |
| POTENTIAL | 7/10 | Platform serves all other ventures |
| CAPABILITY | 6/10 | Architecture deep, UI coverage is the gap |
| PLATFORM | 5/10 | 168K lines, 208 tables, 3.29/10 average maturity |
| Commissioning | 33% | Average 3.29/10 across 208 entities |
| Target MRR | $10K | |
| Actual MRR | $0 | Pre-launch |