The PM33 platform, end-to-end
A 90-minute walkthrough of how PM33 actually works — governance and trust layer, the Brief lifecycle, harness setup with hands-on commands, outcome attribution, and the structural answer to "what does this buy us." Each module pairs a diagram with a workflow narrative.
This is the technical case. PM33 is named throughout — Briefs, the Pam orchestrator, MCP tools, specific RLS patterns, the AR(1) recalibration model. If you want the vendor-agnostic argument instead, read the PM Track.
The 6-module path
Platform Overview
The full PM33 strategic-execution platform on one diagram — governance, orchestration, work-tracker integrations, the 8-stage execution loop. Includes the Harness Ecosystem section (CLAUDE.md, hooks, skills, plugins, MCP, subagents, LSP).
The Brief Lifecycle
9 states, 9 lifecycle events, 3 human gates. How the AutoDoneVerificationService flips Brief status from observable verification signals — not a human checkbox.
Setting Up Your First Harness
Align on what to build, then five slash commands. The harness handles discovery, planning, review, dispatch, and execution autonomously. Finish with /goal Complete Harness and e2e testing.
Outcome Attribution & Recalibration
The closed loop competitors can't easily copy: AR(1) recalibration, smarter next-sprint priorities, outcomeHook on every Brief tied back to the strategic objective.
Governance & Trust for the Enterprise
Designed compliance-first, not bolted on. Tenant isolation at the database via RLS, 13-role RBAC, append-only audit log, SOC2 alignment.
The Pitch — Why This Matters
Today's pain + PM33's structural answer, row by row. The 60-second elevator + the 90-second platform thesis the founder uses on calls.
Total: ~95 minutes including the hands-on harness setup. Modules are self-contained.
Pick a path
Five common reasons people open this page. Each path is self-contained.
| If you're a… | Why | Read these | Time |
|---|---|---|---|
| First-time evaluator | CEO, CTO, head of product. Just want the thesis. | 25 min | |
| Engineering leader | Evaluating for adoption. Needs governance + harness story. | 70 min | |
| Practitioner / soon-to-be operator | About to use PM33 day-to-day. After this it's operational. | 55 min | |
| Sales engineer prepping a demo | Add the outcome-attribution piece for objection-handling. | 40 min | |
| Compliance / security reviewer | Lead with governance, add audit-trail context. | 30 min |
The whole cycle in 90 seconds
If you read nothing else: PM33 is a closed-loop strategic execution platform. The loop has 8 stages — every transition is a structured event in an append-only audit log.
- 1Customer Signal — A request, bug, idea, or VOC entry enters PM33.
- 2Strategic Alignment — Pam scores the signal against active strategic objectives — the workspace's OKRs / roadmap themes.
- 3Brief Authored — The atomic unit of agent-executable work is created — machine-verifiable acceptance criteria, a TDD plan, and an outcomeHook that defines how success will be measured.
- 4Sprint Planned — Capacity-aware scheduler places the Brief in a sprint that respects dependencies + team availability.
- 5Agent Executes — A specialist agent picks it up, working in a per-agent git worktree. TDD discipline (RED → GREEN → REFACTOR → DELIVERY) enforced by the harness skill.
- 6Validate — Independent review agent inspects the diff. CI runs. Schema-drift gate fires. Security checks pass. Only then does the Brief move to in_review.
- 7Shipped — PR merges. Lifecycle event pr_merged fires. Brief auto-flips to done if all verification signals pass.
- 8Outcome Tracked — The outcomeHook window opens. Metrics get attributed back to the strategic objective. If the metric moved → great. If not → the AR(1) forecast model recalibrates.
The loop is continuous, auditable (every transition is a structured event), and multi-tenant (every row in every table is tenant-isolated via RLS). This is the difference between "AI agents write code" (table stakes now) and "AI-driven strategic execution with closed-loop attribution" (PM33).
The Builder-track thesis
The loop is the product.
Everything else — the MCP tools, the Briefs, the harness, the agents — exists to keep the loop running and the data flowing. Strategy → code → outcome → recalibration, in one system, with one audit trail.
Want the vendor-agnostic argument that doesn't name-drop PM33? Read the PM Track →