Skip to main content

BIO-QMS Master Track Index

Project: CODITECT Biosciences QMS Platform Tracks: 17 (A-Q) Total Tasks: ~409 Sections: 89 Sprint Plan: 10 sprints (20 weeks) Updated: 2026-02-14


Track Assignment Rules

  1. Extract keywords from your task
  2. Search this index for matching keywords
  3. Use the identified track (highest keyword match)
  4. Consult track owner for cross-track dependencies

Track Overview

TrackNameAgentStatusTasksSprint
APresentation & Publishingfrontend-react-typescript-expertActive34S1-S3
BCompetitive Intelligence & GTMcompetitive-analystIn Progress28 (4/28)S1-S3
CTechnical Foundationsenior-architectPlanned41S3-S6
DCompliance & Securitysecurity-specialistPlanned33S3-S6
EOperations & Deploymentdevops-engineerPlanned20S5-S7
FDocumentation & Trainingcodi-documentation-writerOngoing24S3+
GRevenue & Billing Operationspayment-systems-specialistPlanned24S5-S7
HCustomer Operationscustomer-onboardingPlanned24S5-S8
ISales & Business Developmentsales-workflowPlanned20S4-S7
JProduct Management & Analyticsproduct-analytics-specialistPlanned22S6-S8
KPlatform Reliability & Maintenancesre-on-call-assistantPlanned24S7-S9
LData & Business Intelligencedata-pipeline-specialistPlanned22S6-S9
MSecurity Operationsincident-response-specialistPlanned18S6-S9
NLegal & Regulatory Operationsregulatory-change-monitorPlanned26S5-S8
OPartner Ecosystempartner-onboardingPlanned19S8-S10
PAccessibility & Internationalizationaccessibility-testing-specialistPlanned18S4-S10
QAI & Automation Governanceresponsible-aiPlanned12S8-S10

Keyword Index

Track A: Presentation & Publishing Platform

Keywords: viewer, dashboard, markdown, rendering, remark, rehype, unified, publish.json, manifest, navigation, search, MiniSearch, sidebar, breadcrumb, presentation, fullscreen, slides, keyboard, cloud publishing, deploy, Vite, React, Tailwind, NDA, auth, access control, DocumentViewToken, NDARecord, npm package, reusable, multi-project

Sections:

  • A.1: Viewer Enhancement — Markdown Rendering
  • A.2: Navigation & Search
  • A.3: Presentation Mode
  • A.4: Cloud Publishing Platform (ADR-195)
  • A.5: NDA-Gated Access Control (ADR-196)
  • A.6: Multi-Project Reusable Package

Track B: Competitive Intelligence & GTM

Keywords: competitive, market analysis, TAM, SAM, SOM, ICP, customer segmentation, competitor, battlecard, positioning, moat, GTM, go-to-market, revenue, channel, demand generation, content strategy, customer success, expansion, launch plan, metrics, dashboard, prompt 76, prompt 77, prompt 78, reconciliation, artifact update

Sections:

  • B.0: Pre-Sprint Document Verification
  • B.1: Competitive Market Analysis (Prompt 76)
  • B.2: GTM Strategy Generation (Prompt 77)
  • B.3: Cross-Artifact Impact Register (Prompt 78)
  • B.4: Artifact Reconciliation & Update

Track C: Technical Foundation

Keywords: backend, API, NestJS, Prisma, scaffold, state machine, workflow engine, CAPA, deviation, change control, agent orchestration, AI, LLM, e-signature, cryptography, ECDSA, SHA-256, integration, webhook, ERP, LIMS, MES, REST, GraphQL

Sections:

  • C.1: Backend API Scaffold (NestJS/Prisma)
  • C.2: State Machine Engine Implementation
  • C.3: Agent Orchestration Framework
  • C.4: E-Signature & Crypto Foundation
  • C.5: Integration & API Layer

Track D: Compliance & Security

Keywords: compliance, FDA, 21 CFR Part 11, HIPAA, SOC 2, audit trail, validation, IQ/OQ/PQ, encryption, access control, RBAC, PHI, BAA, evidence, gap closure, cryptographic, digital signature, pen test, vulnerability, ALCOA+, crypto-shredding, tenant lifecycle, GAMP 5, re-validation

Sections:

  • D.1: Critical Gap Closure (Crypto/Signatures)
  • D.2: FDA 21 CFR Part 11 Validation
  • D.3: HIPAA Security Controls
  • D.4: SOC 2 Compliance Implementation
  • D.5: Audit Trail & Evidence Package
  • D.6: Multi-Tenancy & Tenant Lifecycle
  • D.7: Validation Execution & Management

Track E: Operations & Deployment

Keywords: CI/CD, pipeline, GitHub Actions, Docker, container, GKE, Cloud Run, GCP, infrastructure, Terraform, monitoring, observability, Datadog, Prometheus, Grafana, alerting, backup, disaster recovery, RPO, RTO, SLA, failover, chaos engineering, runbook

Sections:

  • E.1: CI/CD Pipeline
  • E.2: Infrastructure (GKE/Cloud Run)
  • E.3: Monitoring & Observability
  • E.4: Backup & Disaster Recovery
  • E.5: DR Validation & Automation

Track F: Documentation & Training

Keywords: documentation, user guide, admin guide, API docs, OpenAPI, Swagger, compliance docs, validation protocol, training, onboarding, SOPs, work instructions, inventory, artifact, GxP, qualification, competency, training records, refresher

Sections:

  • F.1: User Documentation
  • F.2: API Documentation
  • F.3: Admin & Compliance Docs
  • F.4: Training Materials
  • F.5: Document Inventory Updates
  • F.6: Training Record Management & Qualification

Track G: Revenue & Billing Operations

Keywords: revenue, billing, subscription, pricing, tier, invoicing, Stripe, payment, metering, usage, overage, MRR, ARR, NRR, ASC 606, deferred revenue, proration, dunning, PCI DSS, quote, CPQ, churn, gross margin

Sections:

  • G.1: Subscription Management
  • G.2: Pricing Engine & Tier Management
  • G.3: Invoicing & Payment Processing
  • G.4: Usage Metering & Overage Billing
  • G.5: Revenue Recognition & Reporting

Track H: Customer Operations

Keywords: customer, onboarding, TTFV, retention, support, ticketing, SLA, escalation, health score, churn prediction, CSM, NPS, CSAT, portal, self-service, API key, notification, email, changelog, knowledge base

Sections:

  • H.1: Customer Onboarding Workflow
  • H.2: Support Ticketing System
  • H.3: Customer Success & Health Scoring
  • H.4: Customer Portal & Self-Service
  • H.5: Customer Communication Engine

Track I: Sales & Business Development

Keywords: sales, CRM, HubSpot, Salesforce, pipeline, lead scoring, MQL, SQL, forecast, battlecard, ROI calculator, demo, case study, compliance assessment, gap analysis, proposal, CPQ, e-signature, DocuSign, contract, partner, channel, co-selling

Sections:

  • I.1: CRM & Pipeline Management
  • I.2: Sales Enablement & Collateral
  • I.3: Compliance Assessment Tool
  • I.4: Proposal & Contract Automation
  • I.5: Partner Channel Management

Track J: Product Management & Analytics

Keywords: product, telemetry, analytics, event tracking, BigQuery, ClickHouse, Pub/Sub, cohort, retention, segmentation, DAU, MAU, stickiness, A/B testing, experimentation, feature flag, guardrail, NPS, CSAT, roadmap, feedback, voting

Sections:

  • J.1: Product Telemetry Infrastructure
  • J.2: Feature Analytics & Adoption
  • J.3: WO Analytics Dashboard
  • J.4: A/B Testing & Experimentation
  • J.5: Feedback & Roadmap Management

Track K: Platform Reliability & Maintenance

Keywords: SLA, SLO, SLI, error budget, incident, SEV1, SEV2, on-call, escalation, postmortem, MTTR, MTTD, runbook, patching, dependency, Dependabot, Renovate, Snyk, performance, load testing, chaos engineering, Litmus, GameDay, resilience, DR, multi-site, hub-and-spoke, batch traceability

Sections:

  • K.1: SLA Management & Error Budgets
  • K.2: Incident Management Process
  • K.3: Patch & Dependency Management
  • K.4: Performance Testing & Optimization
  • K.5: Chaos Engineering & Resilience
  • K.6: Multi-Site Coordination

Track L: Data & Business Intelligence

Keywords: data warehouse, BigQuery, star schema, CDC, Debezium, data lake, Parquet, GCS, ETL, ELT, dbt, Airflow, pipeline, BI, dashboard, Tableau, PowerBI, data governance, data quality, PII, retention, regulatory reporting, FDA evidence, HIPAA reporting, SOC 2 evidence

Sections:

  • L.1: Data Warehouse Architecture
  • L.2: ETL/ELT Pipeline
  • L.3: BI Dashboards & Reporting
  • L.4: Data Governance & Quality
  • L.5: Regulatory Reporting Automation

Track M: Security Operations

Keywords: SAST, DAST, SCA, Semgrep, CodeQL, OWASP ZAP, Snyk, vulnerability, CVE, CVSS, pentest, SIEM, Splunk, threat detection, secrets, Vault, KMS, HSM, key rotation, incident response, forensics, breach notification

Sections:

  • M.1: Application Security Pipeline
  • M.2: Vulnerability Management
  • M.3: Security Incident Response
  • M.4: Secrets & Key Management
  • M.5: Security Monitoring & Detection

Keywords: terms of service, privacy policy, acceptable use, GDPR, CCPA, DSR, data subject, consent, DPIA, cookie, cross-border, SCC, contract, MSA, BAA, NDA, DPA, regulatory intelligence, FDA, EMA, MHRA, SBOM, license compliance, vendor risk, IP, patent

Sections:

  • N.1: Terms of Service & Privacy Policy
  • N.2: GDPR/CCPA Compliance Engine
  • N.3: Contract Lifecycle Management
  • N.4: Regulatory Change Monitoring
  • N.5: IP & Vendor Compliance

Track O: Partner Ecosystem

Keywords: partner, Silver, Gold, Platinum, tier, certification, deal registration, channel, marketplace, integration, ERP, LIMS, CMMS, SAP, Oracle, developer portal, SDK, TypeScript SDK, Python SDK, API key, webhook, hackathon, co-selling, MDF, JBR

Sections:

  • O.1: Partner Program Foundation
  • O.2: Integration Marketplace
  • O.3: Developer API & SDK
  • O.4: Partner Analytics & Operations

Track Q: AI & Automation Governance

Keywords: AI governance, responsible AI, model versioning, bias audit, explainability, LIME, SHAP, model risk, FDA SAMD, AI testing, A/B testing, human-in-loop, agent monitoring, prompt versioning, automation policy, approval workflow, risk-based

Sections:

  • Q.1: AI Model Governance Framework
  • Q.2: AI Testing & Validation
  • Q.3: Automation Risk Management

Track P: Accessibility & Internationalization

Keywords: accessibility, WCAG 2.1, a11y, ARIA, screen reader, keyboard navigation, contrast, focus indicator, i18n, internationalization, l10n, localization, ICU MessageFormat, RTL, bidirectional, Crowdin, Lokalise, locale, translation, data residency, multi-region, GDPR region

Sections:

  • P.1: WCAG 2.1 AA Compliance
  • P.2: Internationalization (i18n) Framework
  • P.3: Localization (l10n) Pipeline
  • P.4: Regional Data Residency
  • P.5: Accessibility Testing Automation

Cross-Track Dependencies

DependencyFromToDescription
Viewer foundationA.1A.2, A.3, P.1Markdown rendering before nav/search/a11y
Cloud platformA.4A.5Deploy before auth
Competitive dataB.1B.2, I.2Market analysis before GTM and sales collateral
Backend scaffoldC.1C.2-C.5, G.1, H.1-H.2, J.1, N.2API framework before all backend features
State machineC.2J.3WO engine before WO analytics
IntegrationsC.5O.2, O.3Integration layer before marketplace/SDK
Crypto foundationD.1C.4, M.4Gap closure before e-sig and secrets mgmt
HIPAA controlsD.3N.2, N.3HIPAA before GDPR engine and BAA management
CI/CD pipelineE.1M.1, K.3Pipeline before security scanning and patching
InfrastructureE.2K.1, L.1, P.4GCP before SLA monitoring, data warehouse, regions
MonitoringE.3K.1-K.2, M.3Observability before SLA/incident management
SubscriptionsG.1G.2-G.5, H.3Subscription model before pricing/billing/health
PaymentsG.3H.4, I.4Payment processing before billing portal/contracts
CRMI.1I.3-I.5, H.3CRM before assessment tool, proposals, partner mgmt
TelemetryJ.1J.2-J.4Event tracking before analytics/experimentation
Partner programI.5, O.1O.2-O.4Foundation before marketplace/SDK/analytics
i18n frameworkP.2P.3, P.4i18n before localization and regional data
AI governanceQ.1Q.2-Q.3Model governance before AI testing/risk mgmt
Agent frameworkC.3Q.1Agent orchestration before AI governance
Data warehouseL.1Q.2Warehouse before AI model monitoring data
ValidationD.7Q.2Validation framework before AI validation
Tenant lifecycleD.6H.1, G.1Tenant provisioning before onboarding/billing
DR automationE.5K.5DR validation before chaos engineering
Training recordsF.6D.2Training records for Part 11 compliance
Multi-siteK.6O.1Site management before partner coordination
All tracks*F.*Documentation continuous across all work

Intra-Track Dependencies

Added v3.1: These dependencies exist within individual TRACK files and must be respected during sprint planning.

TrackFromToDescription
AA.1A.2, A.3Viewer rendering before nav/search and presentation
AA.1-A.3A.4Local features before cloud publishing
AA.4A.5Cloud deploy before NDA-gated auth
AA.1-A.5A.6All features before multi-project packaging
BB.0B.1-B.4Document verification before execution
BB.1B.2Competitive data before GTM strategy
BB.1, B.2B.3Analysis before impact register
BB.1-B.3B.4All analysis before reconciliation
CC.1C.2, C.3, C.5Backend scaffold before features
CC.1, C.2C.3Backend + state machine before agents
CC.1-C.4C.5Core features before integrations
DD.1D.2Crypto gap closure before FDA validation
DD.3D.4HIPAA before SOC 2
DD.2-D.4D.5Compliance controls before audit trail
DD.3D.6HIPAA before tenant lifecycle
DD.2D.7FDA validation before validation execution
EE.1E.2CI/CD before infrastructure
EE.2E.3, E.4Infra before monitoring and DR
EE.4E.5DR before DR validation/automation
FF.1-F.3F.4Docs before training materials
FF.4F.6Training before training records/qualification
GG.1G.2Subscriptions before pricing engine
GG.1, G.2G.3Sub + pricing before invoicing/payment
GG.3G.4Payments before usage metering
GG.3, G.4G.5Revenue flows before recognition/reporting
HH.1, H.2H.3Onboarding + support before health scoring
HH.1-H.4H.5All ops before communication engine
II.1I.4CRM before proposals/contracts
II.1I.5CRM before partner channel
JJ.1J.2, J.3, J.4Telemetry before analytics/A-B testing
KK.1K.6SLA management before multi-site
KK.1-K.4K.5All reliability before chaos engineering
LL.1L.2Data warehouse before ETL pipelines
LL.1, L.2L.3Warehouse + ETL before BI dashboards
LL.1L.4Warehouse before data governance
LL.2, L.3L.5Pipelines + dashboards before regulatory reporting
MM.1M.2, M.3AppSec pipeline before vuln mgmt and IR
MM.2, M.3M.5Vuln mgmt + IR before security monitoring
NN.2-N.4N.4GDPR/contracts before regulatory monitoring
OO.1O.2Partner program before marketplace
OO.1-O.3O.4Program + marketplace + SDK before analytics
PP.2P.3i18n framework before localization
PP.1P.5WCAG audit before a11y test automation
QQ.1Q.2, Q.3AI governance before testing/risk mgmt

Sprint Dependency Map

Per-sprint dependency verification. Each section's Depends On is cross-referenced against sprint assignments to verify all prerequisites are satisfied before the section's sprint begins.

Legend: ✅ = dependency in earlier sprint | ⚠️ = dependency in same sprint (sequence matters) | ❌ = dependency in LATER sprint (violation)

S1 (Weeks 1-2): Presentation + Doc Verification

SectionDepends OnDep SprintStatus
A.1None
A.2A.1S1⚠️
A.3A.1S1⚠️
B.0None

Sequencing: A.1 must complete before A.2 and A.3 can start. B.0 is independent.

S2 (Weeks 3-4): Cloud Publishing + Competitive Analysis

SectionDepends OnDep SprintStatus
A.4A.1-A.3S1
B.1None
B.2 (start)B.1S2⚠️

Sequencing: B.1 competitive analysis must produce artifacts before B.2 GTM can begin.

S3 (Weeks 5-6): Auth + GTM + Foundation Start

SectionDepends OnDep SprintStatus
A.5A.4S2
A.6A.1-A.5S1-S2
B.3B.1, B.2S2, S2-S3⚠️
B.4B.1-B.3S2-S3⚠️
C.1 (start)None
D.1None

Sequencing: B.3 and B.4 depend on B.2 completing within this sprint. C.1 and D.1 are independent entry points.

S4 (Weeks 7-8): Backend Core + Sales Enablement

SectionDepends OnDep SprintStatus
C.1-C.2C.1 (S3-S4)S3
C.4C.1, D.1S3-S4, S3
D.2C.1, C.4, D.1S3-S4, S4, S3⚠️
I.1None (external tool)
I.2B.1, B.2S2, S2-S3
P.1A.1, C.1S1, S3-S4

Sequencing: D.2 needs C.4 from same sprint. C.4 should complete before D.2 starts.

S5 (Weeks 9-10): Agents + Integrations + Billing

SectionDepends OnDep SprintStatus
C.3C.1, C.2S3-S4, S4
C.5 (core)C.1-C.4S3-S4
D.3C.1S3-S4
D.6C.1, D.3S3-S4, S5⚠️
G.1C.1S3-S4
G.2G.1S5⚠️
H.1C.1, C.5S3-S4, S5⚠️
N.1None

Sequencing: D.6 needs D.3 (same sprint). G.2 needs G.1 (same sprint). H.1 needs C.5 core (same sprint). Three intra-sprint chains — schedule D.3→D.6, G.1→G.2, C.5→H.1.

S6 (Weeks 11-12): Ops + Payments + Data Warehouse

SectionDepends OnDep SprintStatus
C.5 (healthcare)C.1-C.4S3-S4
D.4C.1, D.3S3-S4, S5
D.7D.2S4-S5
E.1C.1S3-S4
E.2E.1S6⚠️
G.3G.1, G.2S5, S5
H.2C.1S3-S4
I.3C.1, D.1S3-S4, S3
J.1C.1S3-S4
L.1C.1, E.2S3-S4, S6⚠️
M.1E.1S6⚠️
M.4D.1, E.2S3, S6⚠️
N.2C.1, D.3S3-S4, S5
P.2C.1S3-S4

No violations. K.1 and N.3 moved to S7 in v3.2.

Sequencing: E.1→E.2, E.1→M.1, E.2→L.1, E.2→M.4. Heavy intra-sprint dependency chain on E.1/E.2.

S7 (Weeks 13-14): Analytics + Monitoring + Reliability

SectionDepends OnDep SprintStatus
D.5D.2-D.4S4-S6
E.3E.2S6
E.4E.2S6
E.5E.4S7⚠️
G.4C.1, G.3S3-S4, S6
G.5G.3, G.4S6, S7⚠️
H.3H.1, H.2, G.1S5, S6, S5
I.4G.2, I.1S5, S4-S5
I.5I.1, G.1S4-S5, S5
J.2J.1S6
J.3C.2, J.1S4, S6
K.1E.3S7⚠️
K.2E.3S7⚠️
L.2L.1S6
M.3M.1, E.3S6, S7⚠️
N.3I.4S7⚠️
N.4D.2-D.4S4-S6

No violations. K.1 and N.3 moved here from S6 in v3.2; F.6 moved to S8 in v3.2.

Sequencing: E.4→E.5, E.3→K.1, E.3→K.2, E.3→M.3, G.4→G.5, I.4→N.3. Multiple chains off E.3 — complete early in sprint.

S8 (Weeks 15-16): Docs + BI + Marketplace + AI Governance

SectionDepends OnDep SprintStatus
F.1A.1-A.3, C.1-C.2S1, S3-S4
F.2C.1, C.5S3-S4, S5-S6
F.3D.2-D.5S4-S7
F.4F.1-F.3S8⚠️
F.6F.4, C.1S8, S3-S4⚠️
H.4C.1, G.3S3-S4, S6
H.5H.1-H.4S5-S8⚠️
J.4J.1S6
K.4C.1, E.2S3-S4, S6
K.6K.1, E.2S7, S6
L.3L.1, L.2S6, S7
L.4L.1S6
O.1I.5S7
O.2C.5, O.1S5-S6, S8⚠️
P.3P.2S6
P.4E.2, N.2S6, S6
Q.1C.3S5

No violations. F.6 moved here from S7 in v3.2.

Sequencing: F.1→F.2→F.3→F.4→F.6 is a 5-step chain within S8. H.4→H.5. O.1→O.2. Start F-chain and O-chain early.

S9 (Weeks 17-18): Patching + Resilience + Vulnerability

SectionDepends OnDep SprintStatus
K.3E.1S6
K.5K.1-K.4S6-S8
L.5L.2, L.3S7, S8
M.2M.1S6
N.5None
O.3C.5, F.2S5-S6, S8
Q.2Q.1, C.3S8, S5

No violations. All dependencies satisfied from earlier sprints.

S10 (Weeks 19-20): Final Polish

SectionDepends OnDep SprintStatus
F.5All tracksOngoing
J.5C.1S3-S4
M.5M.2, M.3S9, S7
O.4O.1-O.3S8-S9
P.5P.1S4
Q.3Q.1, L.1-L.2, C.3S8, S6-S7, S5

No violations. All dependencies satisfied.

Dependency Violations Summary (v3.2 — All Resolved)

#SectionWasDepDep SprintFixStatus
1K.1S6E.3S7Moved K.1 to S7✅ Fixed
2N.3S6I.4S7Moved N.3 to S7✅ Fixed
3F.6S7F.4S8Moved F.6 to S8✅ Fixed

v3.2 result: Zero dependency violations remaining. All 89 sections have dependencies satisfied by earlier or same-sprint sections. Load impact: S6: 42→33 (-9), S7: 30→35 (+5), S8: 34→38 (+4). Max sprint: S8 at 38 tasks. Range: 12-38.


Sprint Allocation (10 Sprints, 20 Weeks)

Rebalanced v3.2: Dependency-verified sprint plan. v3.2 fixed 3 forward-reference violations from v3.1: K.1 S6→S7, N.3 S6→S7, F.6 S7→S8. All 89 sections now have dependencies satisfied by earlier or same-sprint sections. Zero violations remaining. Sprint range: 12-38 tasks (max S8). Original v2 max was 32 (S7). Peak S6 reduced from 42→33.

SprintWeeksSectionsEst. TasksGoal
S11-2A.1, A.2, A.3, B.0~19Presentation-grade local website + doc verification
S23-4A.4, B.1, B.2 (start)~12Cloud publishing + competitive analysis
S35-6A.5, A.6, B.2-B.4, C.1 (start), D.1~22Auth + GTM + foundation start
S47-8C.1-C.2, C.4, D.2, I.1-I.2, P.1~24Backend core + sales enablement + a11y audit
S59-10C.3, C.5 (core), D.3, D.6, G.1-G.2, H.1, N.1~38Agents + integrations + billing + tenant lifecycle
S611-12C.5 (healthcare), D.4, D.7, E.1-E.2, G.3, H.2, I.3, J.1, L.1, M.1, M.4, N.2, P.2~33Ops + payments + data warehouse + pipelines
S713-14D.5, E.3-E.5, G.4-G.5, H.3, I.4-I.5, J.2-J.3, K.1-K.2, L.2, M.3, N.3-N.4~35Analytics + monitoring + SLA + contracts + reliability
S815-16F.1-F.4, F.6, H.4-H.5, J.4, K.4, K.6, L.3-L.4, O.1-O.2, P.3-P.4, Q.1~38Docs + training + BI + marketplace + AI governance
S917-18K.3, K.5, L.5, M.2, N.5, O.3, Q.2~29Patching + resilience + vulnerability + vendor + SDK
S1019-20F.5, J.5, M.5, O.4, P.5, Q.3~14Final: security monitoring + feedback + partner ops + a11y

Sprint Load Analysis

SprintOriginal (v2)v3.0v3.1v3.2Notes
S115151919B.0 doc verification
S212121212Unchanged
S322222222Unchanged
S420242424C.2 change governance
S528383838D.6 tenant lifecycle
S624424233v3.2: K.1, N.3 out (dep violations)
S732383035v3.2: K.1, N.3 in; F.6 out
S824423438v3.2: F.6 in
S912162929Unchanged from v3.1
S107111414Unchanged from v3.1

v3.0 rebalancing moves (from v2):

  • K.1 (SLA Management): S7→S6 — only needs E.3, available in S6
  • L.1 (Data Warehouse): S7→S6 — only needs E.2, available in S6
  • N.3 (Contracts): S7→S6 — contract templates independent
  • O.1 (Partner Foundation): S7→S8 — low priority, no S7 dependents
  • C.5 split: core (C.5.1-C.5.6) in S5, healthcare (C.5.7-C.5.10) in S6

v3.1 rebalancing moves (from v3.0):

  • K.3 (Patch & Dependency): S7→S9 — depends on E.1 (S5), no S7 dependents
  • M.2 (Vulnerability Mgmt): S7→S9 — depends on M.1 (S6), no S7 dependents
  • M.5 (Security Monitoring): S8→S10 — depends on M.2/M.3 (S9/S7-S8)
  • N.5 (IP & Vendor Compliance): S8→S9 — no blocking deps

v3.2 dependency violation fixes (from v3.1):

  • K.1 (SLA Management): S6→S7 — depends on E.3 (S7), was forward-referencing
  • N.3 (Contract Lifecycle): S6→S7 — depends on I.4 (S7), was forward-referencing
  • F.6 (Training Records): S7→S8 — depends on F.4 (S8), was forward-referencing
  • Result: Zero dependency violations. Max sprint: S8 at 38 tasks. Range: 12-38 (was 12-42)

Compliance: CODITECT Track Nomenclature Standard (ADR-054)