Skip to content

jamesoleinik/launch-control

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

104 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

🚀 Launch Control

A Product Launch Coordinator built with Microsoft Dataverse — from data model to agents to dashboard.

This repo is the companion to the Launch Control LinkedIn series by James Oleinik, Product Director for Microsoft Dataverse. Over 15 episodes (3/week for ~5 weeks), we build a complete product launch coordination system from scratch — and open-source every line of code.

The Problem

Engineering teams are automating code reviews, DRIs, and incident response. But up the stack? Executives still want status. Cross-team projects still mean passing spreadsheets around. What if we applied the same agentic thinking to project coordination?

The Solution: Three Layers

┌──────────────────────────────────────────────────────┐
│  LAYER 3: MANAGEMENT & OPERATIONS                    │
│  Power App Dashboard  │  Python SDK/pandas  │  CLI   │
│  Admin Skills (agentic administration at scale)      │
├──────────────────────────────────────────────────────┤
│  LAYER 2: INTELLIGENCE                               │
│  Business Skills  │  Agents (Copilot Studio, Claude) │
│  Agent Flows  │  Custom Actions  │  BYO MCP Servers  │
│  MCP Server (universal) │ CLI │ SDK (coding agents)  │
├──────────────────────────────────────────────────────┤
│  LAYER 1: BUSINESS SYSTEM OF RECORD                  │
│  Dataverse Tables & Relationships │ Prompt Columns   │
│  Virtual Entities (real-time, no data replication)   │
│  Dataverse Intelligence (native M365 Copilot)        │
└──────────────────────────────────────────────────────┘

Episode Guide

Full series index with links to each episode's README, preflight, and scripts: episodes/README.md.

# Episode Hero capability
1 AI-Powered Data Modeling Official Dataverse plugins for Copilot & Claude Code → first Dataverse tables
2 Your Playbook & Ingestion Business skills + mapping-driven CLI ingestion
3 Promoting the Staging Layer Python + pandas; staging → unified
4 Extending & Enforcing the Model Virtual entities (custom GitHub Issues) + a server-side business rule the coding agent authors — guardrails every future agent must honor
5 Custom Tools Custom API + two BYO MCP custom connectors registered with paconn
6 Roles & Reach Four flat roles (Member / Owner / Viewer / Admin) over Eps 1–5 data + tools — same query, four lenses
7 The Agent Declarative Launch Coordinator + knowledge substrate
8 Autonomous Agents Launch Sentinel — event-triggered autonomous agent
9 The Code-First Agent Same skills, different runtime — Python agent that pulls skills from Dataverse
10 The Dashboard Generative Power Apps page deployed via pac model genpage upload
11 Copilot Just Knows Native Copilot intelligence over Dataverse — no agent needed
12 Agentic Administration The management plane is agent-driven — capacity, audit, cleanup, blast-radius
13 Full Orchestra + Your Turn Six surfaces in 60 seconds + open-source CTA

Each episode is also tagged in git: git checkout ep-09 to see the repo as it was at that episode's ship.

Quick Start

Prerequisites

  • Python 3.10+ with pip install PowerPlatform-Dataverse-Client
  • Node.js 18+ with npm install -g @microsoft/dataverse
  • PAC CLI
  • A Microsoft Dataverse environment with System Administrator role

Setup

git clone https://github.com/jamesoleinik/launch-control.git
cd launch-control
cp .env.example .env
# Edit .env with your Dataverse environment URL and credentials
pip install -r scripts/python/requirements.txt

To verify any episode is set up correctly, run its preflight:

python episodes/ep-11-the-dashboard/preflight.py

Repo Structure

launch-control/
├── episodes/                  # 13 per-episode folders (READMEs + preflights + scripts)
├── datamodel/                 # Table definitions, mappings, sample data
├── solutions/LaunchControl/   # Exported managed solution
├── business-skills/           # Launch readiness, escalation, status rules
├── data/knowledge/            # Sanitized KB articles for RAG
├── agents/
│   ├── launch-coordinator/    # Declarative Copilot Studio agent (Ep 8)
│   ├── launch-sentinel/       # Autonomous agent (Ep 9)
│   ├── launch-coordinator-py/ # Code-first agent (Ep 10)
│   └── agent-flows/           # Agent flow configurations
├── apps/launch-command-center/# Generative Power Apps page (Ep 11)
├── plugins/                   # Custom Dataverse plugins & actions
└── scripts/                   # auth.py + shared Python utilities

Key Themes

Skills All the Way Down

  • Build skills — AI creates your data model, plugins, and agents
  • Process skills — Business knowledge agents follow at runtime (portable across agent platforms)
  • Operate skills — Scripted automation and agentic administration at scale

Master the Process in Dataverse

The launch spans GitHub, SharePoint, email — but mastering the business process state in Dataverse (think dynamic programming) means every agent, app, and Copilot reads the same truth.

Contributing

See CONTRIBUTING.md for how to fork and adapt this for your own scenario — customer onboarding, release management, incident response, or anything else.

See also

License

MIT


Built by James Oleinik | Product Director, Microsoft Dataverse

About

Launch Control — a 12-episode LinkedIn series building a launch-management system on Microsoft Dataverse: data model, agents (declarative + autonomous + code-first), generative Power Apps page, and agentic administration. Open-source companion repo.

Topics

Resources

License

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Packages

 
 
 

Contributors