UpsQuad PRD Registry
Canonical index of all product requirements documents. Updated 2026-04-16.
Master PRD
| PRD | Version | Status | Scope |
|---|---|---|---|
| Master PRD: UpsQuad AI Workforce Platform | 2.3 | Active | End-to-end product |
Markdown mirror: docs/UpSquad_Complete_PRD.md (v1.9)
Sub-PRDs (Delivered)
| PRD | Version | Scope |
|---|---|---|
| Context Engine (#2) | 1.1 | Token optimisation, context assembly |
| Client Portal MVP (#79) | 1.0 | app.upsquad.ai portal |
| Agent Runtime Core (#93) | 1.6 | Hybrid Go + Python runtime |
| BYOA & AI Governance (#231) | 1.0 | Governed MCPs, AI Gateway, HTTP proxy |
| SCM Credentials (#348) | 1.7 | Per-member SCM credential vault |
| Agent Runtime Optimisation (#380) | 1.8 | P4.8.1-P4.8.8 waves |
| Onboarding APIs (#425) | 1.0 | 5 backend API bundles |
Sub-PRDs (Draft — Awaiting Approval)
| PRD | Version | Scope |
|---|---|---|
| Agent Lifecycle & Upgrade (#550) | 1.0 | Version pinning, upgrade, rollback |
| Workspace Persistence (#551) | 1.0 | Git WIP, build cache, spot node |
| Pricing & Packaging (#552) | 1.0 | Tier model, pricing |
| Dashboard Intelligence (#553) | 1.0 | Dashboard + Quad UX |
| Competency Catalogue (#554) | 1.0 | 12 default profiles |
| Platform AI Model Configuration (#558) | 1.1 | UpsQuad-controlled per-function model selection; upsquad-admin operator portal (not tenant-facing) |
| Quad — AI Assistant & Chat Infrastructure (#573) | 1.0 | Persistent chat, lazy pagination, pinned proactive messages, cross-device continuity |
| Sandbox Benchmark Environment (#615) | 1.0 | Isolated registry-pull sandbox for per-component perf + feature-coverage testing (tracker #616, blocked on migration #604) |
| Temporal Adoption — Durable Agent Workflows (#623) | 1.0 | Durable execution for approval chains, SCIM syncs, agent sessions, sub-agent delegation (tracker #624; blocked on migration + Wave I/J/K/L + PRD #558) |
| Pre-Onboarding E2E + Multi-Role Verification (#950) | 1.0 | Behavioral E2E verification across all client-portal surfaces for 5 personas; gates UpsQuad pilot cutover (portal:client, qa-e2e) |
| UX Debt Remediation (#1005) | 1.0 | 5-wave structural UX remediation: guardrails wizard, jargon rename, UUID→picker, ⌘K + tooltips, mobile pass; gates paid-MVP (portal:client, ux) |
Sub-PRDs (Approved — HLD in progress)
| PRD | Version | HLD | Scope |
|---|---|---|---|
| Org Model v2.3 (#549) | 1.0 | HLD #556 | Flexible hierarchy, RBAC, cascading guardrails, SCIM, tool visibility |
Versioning Policy
- Master PRD uses the 2.x track (history: 1.x pre-2026-04-11; 2.0 major rewrite → 2.3 current)
- Each sub-PRD has its own version track starting at 1.0
- Bumps: major = conceptual rewrite; minor = new requirement; patch = typos/clarifications
How to Check Current Versions
Every PRD starts with **Version**: or ## Version in its body. The registry above is the single source of truth. If discrepancy found, GitHub issue body + this registry are authoritative over any standalone markdown file.
Restructure Notes (2026-04-16)
Prior to this date, scope was split between:
docs/UpSquad_Complete_PRD.md(v1.8) — an ~500-item priority-structured PRD- GitHub issue #1 (v2.2) — an org-model-focused PRD with scope creep into P8/P10/P11/pricing/dashboard/competency
The 2026-04-16 restructure:
- Designated GitHub issue #1 as the Master PRD (v2.3). Its body is the canonical master.
- Extracted six component sub-PRDs (#549–#554) carrying detailed requirements that had accumulated in #1.
- Kept existing delivered sub-PRDs (#2, #79, #93, #231, #348, #380, #425) as-is — they already had the right scope.
- Bumped
docs/UpSquad_Complete_PRD.mdto v1.9 with a changelog entry, a top-of-file SUB-PRDs section, and status that points to this registry. The historical priority sections remain as archive context. - Created this registry as the canonical index.
Going forward, any gap or new requirement should be evaluated against sub-PRDs first; new sub-PRDs are created when a coherent new scope emerges.