Skip to content

Project Structure

Document ID: GOV-PS-001
Status: Active
Owner: Maya (Operations)
Reviewer: Simon (CEO)
Approver: Simon (CEO)
Last Edited: Maya, 2026-02-24
Review Due: 2026-05-24

Overview

COOWN uses a multi-project GitHub organization structure to manage operations, compliance, development, and strategic initiatives. This document defines the repository folder structure, purpose, scope, and access controls.

Dev-Ops Repository Structure

Repository: coown-box/Dev-Ops
Type: Private operations repository

Current Structure (as of 2026-02-24)

Dev-Ops/
├── archive/                    # Historical backups and migrations
│   ├── ai-swarm-backups/       # Agent configuration backups
│   └── notion-migration/       # Legacy Notion export data
├── cold-email-system/          # Email automation system
│   ├── database/               # Lead/contact databases
│   └── email-templates/        # Template library
├── incidents/                  # Incident reports and post-mortems
├── projects/                   # Active project workspaces
│   ├── MotoClaw/               # MotoClaw product (ICP canisters)
│   ├── backoffice-vps/         # VPS infrastructure configs
│   ├── ims-alignment-2026-q1/  # IMS documentation alignment
│   ├── ims/                    # IMS process documentation
│   ├── infrastructure/         # Infrastructure projects
│   ├── leo/                    # Leonardo (design) projects
│   ├── local-swarm-improvements/  # Agent swarm enhancements
│   ├── polyreg/                # PolyReg membership project
│   ├── uni-notebook-swarm-test/   # Experimental notebook
│   └── work-structure/         # Process structure experiments
├── reports/                    # Operational reports
└── templates/                  # Project templates
    └── project-charter.md

Migration Note

Previous structure (deprecated 2026-02-24): Used categorical subfolders under projects/: - development/ — Software & infrastructure projects - compliance/ — Regulatory & audit projects
- business/ — Marketing, sales, partnerships - operations/ — Day-to-day operational projects - strategic/ — Executive-level initiatives

Rationale for change: Project-based organization provides clearer ownership, reduces cross-category ambiguity, and aligns with GitHub Projects board structure.

GitHub Projects

The Dev-Ops repository is linked to 5 GitHub Projects for kanban-style workflow management:

Project Purpose Board #
🚀 Development Software development & infrastructure #2
⚖️ Compliance & Legal Regulatory compliance & audit prep #6
🎯 Business Development Sales, marketing, partnerships #5
👥 Operations Daily operations, incidents, training #7
📊 Management Strategy, OKRs, board materials #8