Skip to content

Sinergy Solutions LLC - Repository Standardization Adaptation Plan

Generated: 2025-09-30 Purpose: Adapt the monorepo template to Sinergy's multi-repo organization structure for repeatability, quality, and consistency.

Executive Summary

This plan establishes production-grade standards for CORTX Platform - Sinergy Solutions' AI-powered compliance and orchestration platform. CORTX operates as a multi-repo microservices architecture (9 repos + org infrastructure) with:

  • Platform Services: Core orchestration, AI broker, validation, compliance, workflow engine
  • RulePacks & WorkflowPacks: Version-controlled JSON/YAML compliance artifacts
  • Domain Suites: FedSuite, CorpSuite, MedSuite, GovSuite (vertical applications)
  • Design Tools: BPM Designer with AI assistant for visual workflow creation
  • Marketplace Vision: GitHub-like Pack economy with certification tiers

The goal is to create consistent standards across all repositories while maintaining microservices independence and enabling the compliance-first, multi-tenant platform architecture.

Current State Analysis

Organization Structure

sinergysolutionsllc/
├── cortx-platform      # Core Platform: 7 microservices (Gateway, Identity, AI Broker, etc.)
├── cortx-designer      # BPM Designer: Visual workflow builder with AI assistant + RAG
├── cortx-sdks          # Client Libraries: TypeScript & Python SDKs for platform APIs
├── cortx-packs         # Pack Registry: RulePacks & WorkflowPacks (JSON/YAML schemas)
├── cortx-e2e           # Integration Testing: E2E tests, pack validation, smoke tests
├── fedsuite            # Federal Suite: GTAS reconciliation, Treasury compliance
├── corpsuite           # Corporate Suite: PropVerify (title), Greenlight (opps), InvestMait
├── medsuite            # Medical Suite: HIPAA audit, claims verification
└── govsuite            # Government Suite: State/local operations

Technology Stack by Repo

  • cortx-platform: Python 3.11, FastAPI, PostgreSQL, Redis (event bus), Docker, GCP Cloud Run
  • cortx-designer: Next.js 14, React Flow (canvas), FastAPI (compiler), LangChain + Gemini (AI/RAG)
  • cortx-sdks: TypeScript (pnpm, Node 20), Python 3.11, GitHub Packages publishing
  • cortx-packs: JSON Schema validation, RulePack/WorkflowPack schemas, check-jsonschema
  • cortx-e2e: Docker Compose orchestration, pytest, requests, pack execution tests
  • Suites (4): Python/FastAPI services, Next.js frontend, module-based architecture

Current Common Elements

✅ Each repo has: .claude/, .github/workflows, docs/, specs/, README, CODEOWNERS ❌ Missing: Standardized Makefiles, CHANGELOG, .env patterns, agent definitions, QA spine, test harness

Adaptation Strategy

Level 1: Organization-Wide (Shared Infrastructure)

Apply to ~/Development/sinergysolutionsllc/ root:

A. Enhanced .claude/agents/

Purpose: Define team roles that work across all repos

New structure:

.claude/
├── settings.local.json (existing)
└── agents/
    ├── tech-lead-architect.md       # Architecture decisions, contracts
    ├── tech-architect.md             # Technical design, patterns
    ├── backend-services-dev.md       # Service implementation (Python/Node)
    ├── ui-frontend-developer.md      # Frontend/dashboard work
    ├── functional-lead.md            # Requirements, user stories
    ├── gcp-deployment-ops.md         # Cloud Run, Terraform, CI/CD
    └── quality-assurance-lead.md     # Testing, QA spine, coverage

Variables to inject:

  • ORG_NAME: "Sinergy Solutions LLC"
  • PLATFORM: "CORTX - AI Orchestration & Compliance Platform"
  • CLOUD: "GCP (Cloud Run + Pub/Sub + Cloud SQL + Cloud Logging)"
  • INFRA_IAC: "Terraform"
  • REPOS: [cortx-platform, cortx-designer, cortx-sdks, cortx-packs, cortx-e2e, fedsuite, corpsuite, medsuite, govsuite]
  • ENVIRONMENTS: [dev, staging, prod]
  • PACK_TYPES: [rulepacks, workflowpacks]
  • AI_MODELS: [gemini-1.5-pro, gemini-1.5-flash, claude-3.5-sonnet (planned), gpt-4-turbo (planned)]
  • COMPLIANCE_FRAMEWORKS: [FedRAMP, HIPAA, NIST-800-53, SOC2, FISMA, OMB-A-136]
  • DEPLOYMENT_MODES: [saas-multi-tenant, saas-dedicated, on-prem]

B. Enhanced docs/

docs/
├── ADRs/                            # (existing) Architecture decision records
├── dashboards/                      # (existing) Grafana/monitoring
├── runbooks/                        # (existing) Ops procedures
├── CORTX_PLATFORM_FDD.md           # NEW - Platform-wide functional design
├── ai_governance/                   # NEW - AI/RAG Governance
│   ├── AI_RULES.md                  # Claude/AI development guidelines
│   ├── FOCUS.md                     # Current priorities, constraints
│   ├── RAG_KNOWLEDGE_BASE.md        # Vector store management
│   └── MODEL_SELECTION.md           # AI model routing strategy
├── packs/                           # NEW - RulePack/WorkflowPack Documentation
│   ├── PACK_AUTHORING_GUIDE.md     # How to create Packs
│   ├── PACK_GOVERNANCE.md          # Approval & versioning process
│   ├── RULEPACK_SCHEMA.md          # JSON schema specifications
│   └── WORKFLOWPACK_SCHEMA.md      # YAML schema specifications
├── marketplace/                     # NEW - Pack Marketplace Docs
│   ├── MARKETPLACE_VISION.md       # "GitHub for compliance workflows"
│   ├── CERTIFICATION_PROCESS.md    # Pack certification tiers
│   └── REVENUE_MODEL.md            # 70/30 split, licensing
├── compliance/                      # NEW - Compliance Documentation
│   ├── FEDRAMP_STATUS.md           # FedRAMP readiness tracking
│   ├── HIPAA_CONTROLS.md           # HIPAA safeguards mapping
│   ├── NIST_800_53_MAPPING.md      # Control implementation
│   └── AUDIT_PROCEDURES.md         # Compliance audit processes
├── prompts/                         # NEW - AI/Dev Prompts
│   ├── CORTX_MODULE_FDD_TEMPLATE.md # Module FDD generator
│   ├── DAILY_CLOSEOUT_PROMPT_ORG.md
│   └── REPO_SCAFFOLDING_PROMPT.md   # This adapted template
└── tracking/                        # NEW - QA/PM Spine
    ├── ENTERPRISE_ROADMAP.md        # Org-wide roadmap
    ├── QA_ASSESSMENT.md             # Quality metrics across repos
    └── QA_RESPONSE.md               # QA process documentation

C. DAILY_LOGS/

DAILY_LOGS/
└── YYYY-MM-DD.md                    # Template for daily tracking

D. Root Makefile (org-wide operations)

# Targets: clone-all, update-all, status-all, test-all, deploy-all

E. Enhanced infra/

infra/
├── docs/                            # Infrastructure documentation
├── sql/                             # Shared SQL migrations/schemas
├── docker/                          # Shared Dockerfiles
├── helm/                            # Kubernetes charts
└── terraform/                       # ENHANCED
    ├── INDEX.md                     # Terraform structure guide
    ├── README.md                    # Setup instructions
    ├── QUICK_START.md               # Getting started
    ├── ARCHITECTURE.md              # Infrastructure architecture
    ├── DEPLOYMENT_SUMMARY.md        # Current deployments
    ├── backend.tf                   # GCS backend config
    ├── main.tf                      # Main resources
    ├── variables.tf                 # Variable definitions
    ├── outputs.tf                   # Output definitions
    ├── versions.tf                  # Provider versions
    ├── phase_1_3.tf                 # Current phase resources
    ├── monitoring.tf.disabled       # Future monitoring
    ├── alerting.tf.disabled         # Future alerting
    ├── environments/
    │   ├── dev.tfvars
    │   ├── staging.tfvars
    │   └── prod.tfvars
    └── scripts/
        ├── init.sh
        └── deploy.sh

F. Org-level files

├── .env.example                     # Org-wide secrets template
├── .gitignore                       # Enhanced for Node, Python, Terraform
└── ORGANIZATION_GUIDE.md            # New: How repos fit together

Level 2: Per-Repo Standardization

Apply consistently to all 9 repos with repo-specific customization.

A. Enhanced .claude/agents/

Keep existing agents.yaml, add individual agent files:

.claude/
├── agents.yaml                      # (existing - keep)
└── agents/                          # NEW
    ├── architect.md                 # Repo architect (contracts, standards)
    ├── coder.md                     # Implementation (features + tests)
    └── reviewer.md                  # Code review (lint, coverage, CODEOWNERS)

Each agent file includes:

  • Role definition
  • Repo-specific context (services, modules, dependencies)
  • Project variables (repo name, tech stack, cloud resources)

B. Standardized Makefile

Targets (adapt per repo):

.PHONY: help install build test lint format dev deploy clean

help:          # Show available targets
install:       # Install dependencies (pip/npm/pnpm)
build:         # Build artifacts
test:          # Run tests (pytest/jest)
lint:          # Lint code (ruff/eslint)
format:        # Format code (black/prettier)
dev:           # Start local dev server
deploy:        # Deploy to environment
clean:         # Clean build artifacts

Repo-specific variations:

  • cortx-platform: Python-focused, docker-compose targets
  • cortx-sdks: TypeScript + Python, pnpm, build outputs
  • cortx-packs: Schema validation, no server
  • cortx-e2e: Test orchestration, compose up/down
  • Suites: Module-based targets

C. CHANGELOG.md

Keep-a-changelog format:

# Changelog
All notable changes to {REPO_NAME} will be documented in this file.

## [Unreleased]
### Added
### Changed
### Deprecated
### Removed
### Fixed
### Security

## [0.1.0] - 2025-09-30
### Added
- Initial structure

D. Enhanced README.md

Standard sections:

# {REPO_NAME}

## Overview
{Purpose and value proposition}

## Quick Start
{How to get started}

## Repository Structure
{Directory layout}

## Development
{Local setup, testing, conventions}

## Deployment
{How to deploy}

## Dependencies
{What this repo depends on}

## Contributing
See [CONTRIBUTING.md](./CONTRIBUTING.md)

## License
{LICENSE}

E. .env.example

Repo-specific environment template with safe defaults

F. Enhanced docs/

docs/
├── {REPO_NAME}_FDD.md               # Functional Design Document
├── deployment/                      # Deployment guides
├── operations/                      # Runbooks
└── architecture/                    # Architecture diagrams

G. tests/ (standardized testing)

For Python repos (platform, e2e):

tests/
├── __init__.py
├── conftest.py                      # pytest fixtures
├── unit/                            # Unit tests
├── integration/                     # Integration tests
└── __utils__/                       # Test helpers

For TypeScript repos (sdks, designer):

tests/
├── jest.config.js
├── setup.ts
├── unit/
├── integration/
└── __utils__/

For Suites:

tests/
├── modules/                         # Module-specific tests
│   ├── fedreconcile/
│   ├── dataflow/                    # formerly fedtransform/
└── integration/                     # Cross-module tests

Level 3: Repo-Specific Enhancements

cortx-platform

Type: Services repository (Python FastAPI)

Additions:

services/
├── gateway/                         # (existing)
│   ├── src/
│   ├── tests/
│   ├── Dockerfile
│   ├── .env.example
│   └── README.md
└── template/                        # NEW - Service template
    ├── src/
    │   ├── app.py                   # FastAPI starter
    │   ├── config.py
    │   └── routes/
    ├── tests/
    ├── Dockerfile
    ├── .dockerignore
    ├── requirements.txt
    ├── .env.example
    └── README.md

Tech: Python 3.11, FastAPI, uvicorn, Docker, GCP Cloud Run Makefile targets: install, dev, test, lint, docker-build, docker-run, deploy

cortx-sdks

Type: Multi-language SDK repository

Additions:

sdk-ts/
├── src/
├── tests/
├── package.json                     # @sinergysolutionsllc/cortx-sdk
├── tsconfig.json
└── README.md

sdk-python/
├── cortx_sdk/
├── tests/
├── setup.py
├── pyproject.toml
└── README.md

packages/                            # NEW - Shared utilities
└── common-types/                    # TypeScript types

Tech: TypeScript (pnpm), Python 3.11, GitHub Packages Makefile targets: install, build, test, lint, publish

cortx-packs

Type: Schema/rule repository

Current structure is good, add:

workflowpacks/                       # NEW - Workflow definitions
└── template/
    └── v1/
        └── pack.json

docs/
└── PACK_AUTHORING_GUIDE.md         # How to create packs

Tech: JSON Schema, check-jsonschema Makefile targets: validate, lint, test

cortx-e2e

Type: Integration test repository

Enhancements:

tests/
├── scenario/                        # (existing) Test scenarios
│   └── smoke_test.py
├── integration/                     # NEW - Full integration tests
├── __utils__/                       # NEW - Test utilities
│   ├── docker_helpers.py
│   └── api_client.py
└── fixtures/                        # NEW - Test data

Current Makefile is good, enhance with:

  • make test-smoke, make test-integration, make test-all

fedsuite, corpsuite, medsuite, govsuite

Type: Module-based application suites

Standard structure (example: fedsuite):

modules/
├── fedreconcile/
│   ├── src/
│   ├── tests/
│   ├── README.md                    # (existing)
│   ├── package.json or requirements.txt
│   └── .env.example
├── dataflow/
│   └── (same structure, replacing legacy fedtransform)
└── template/                        # NEW - Module template
    ├── src/
    ├── tests/
    └── README.md

docs/
└── FEDSUITE_FDD.md                  # Functional design

apps/                                # NEW (if dashboard needed)
└── dashboard/                       # Next.js + Tailwind (optional)

Tech: Depends on module (Python/TypeScript) Makefile targets: install-all, test-all, lint-all, deploy-module

cortx-designer

Type: UI/Design tools

Enhancements:

apps/
└── designer/                        # Main app
    ├── src/
    ├── public/
    ├── package.json
    └── README.md

packages/                            # Shared UI components
└── ui-components/

Tech: TypeScript, React/Next.js, Tailwind Makefile targets: install, dev, build, test, lint

Implementation Variables

Org-Wide Variables

ORG_NAME: "Sinergy Solutions LLC"
DEFAULT_LICENSE: "MIT"
CLOUD: "GCP (Cloud Run + Pub/Sub + Cloud SQL + Cloud Logging)"
INFRA_IAC: "Terraform"
ENVIRONMENTS: ["dev", "staging", "prod"]
GIT_ORG: "sinergysolutionsllc"
REPOS:
  - cortx-platform
  - cortx-designer
  - cortx-sdks
  - cortx-packs
  - cortx-e2e
  - fedsuite
  - corpsuite
  - medsuite
  - govsuite

Per-Repo Variables

cortx-platform:

PROJECT_NAME: "cortx-platform"
PROJECT_SUMMARY: "CORTX Platform - AI orchestration and compliance automation platform with 7 core microservices"
LANG_STACK: ["Python 3.11", "FastAPI", "PostgreSQL", "Redis"]
RUNTIME_SERVICES: ["gateway", "identity", "ai-broker", "schemas", "validation", "compliance", "workflow"]
CLOUD_SERVICES: ["Cloud Run", "Cloud SQL", "Pub/Sub", "Cloud Logging", "Secret Manager"]
AI_CAPABILITIES: ["LangChain", "Gemini", "RAG", "Model Router"]
COMPLIANCE: ["FedRAMP Phase I", "NIST 800-53", "HIPAA", "SOC2"]
DEPLOYMENT: ["Multi-tenant SaaS", "Dedicated Clusters", "On-prem"]

cortx-sdks:

PROJECT_NAME: "cortx-sdks"
PROJECT_SUMMARY: "CORTX SDKs - TypeScript and Python client libraries for CORTX Platform API"
LANG_STACK: ["TypeScript", "Python", "pnpm"]
PACKAGES: ["sdk-ts", "sdk-python", "common-types"]
PUBLISH_TO: "GitHub Packages"

cortx-packs:

PROJECT_NAME: "cortx-packs"
PROJECT_SUMMARY: "CORTX Packs Registry - RulePacks & WorkflowPacks for compliance automation and process orchestration"
LANG_STACK: ["JSON Schema", "YAML"]
PACK_TYPES:
  - "rulepacks": "Validation rules, compliance policies (JSON)"
  - "workflowpacks": "Process orchestration definitions (YAML)"
VALIDATION: "check-jsonschema"
GOVERNANCE: "Version control, approval workflows, certification tiers"
EXAMPLES:
  - "federal/gtas-gate": "204 Treasury GTAS validation rules"
  - "healthcare/hipaa-audit": "HIPAA compliance checks"
  - "realestate/title-validation": "Property title verification rules"

cortx-e2e:

PROJECT_NAME: "cortx-e2e"
PROJECT_SUMMARY: "CORTX E2E Tests - End-to-end integration tests for the CORTX ecosystem"
LANG_STACK: ["Python", "pytest", "Docker Compose"]
TEST_TYPES: ["smoke", "integration", "scenario"]

fedsuite:

PROJECT_NAME: "fedsuite"
PROJECT_SUMMARY: "FedSuite - Federal financial compliance and reconciliation modules"
MODULES: ["fedreconcile", "dataflow"]
DOMAIN: "Federal Financial Management"
COMPLIANCE: ["GTAS", "FBDI"]

corpsuite:

PROJECT_NAME: "corpsuite"
PROJECT_SUMMARY: "CorpSuite - Corporate real estate and opportunity analysis modules"
MODULES: ["propverify", "greenlight", "investmait"]
DOMAIN: "Corporate Real Estate & Procurement"

medsuite:

PROJECT_NAME: "medsuite"
PROJECT_SUMMARY: "MedSuite - Healthcare compliance and claims verification modules"
MODULES: ["hipaaaudit", "claimsverify"]
DOMAIN: "Healthcare Compliance"
COMPLIANCE: ["HIPAA"]

govsuite:

PROJECT_NAME: "govsuite"
PROJECT_SUMMARY: "GovSuite - Government operations and compliance modules"
MODULES: []  # TBD
DOMAIN: "Government Operations"

cortx-designer:

PROJECT_NAME: "cortx-designer"
PROJECT_SUMMARY: "CORTX BPM Designer - Visual workflow builder with AI assistant for creating compliant RulePacks & WorkflowPacks"
LANG_STACK: ["TypeScript", "React", "Next.js 14", "Python", "FastAPI"]
UI_FRAMEWORK: "Next.js + Tailwind + React Flow (canvas)"
FEATURES:
  - "Visual Canvas": "28 node types (validation, decision, AI, approval, etc.)"
  - "AI Assistant": "Natural language → workflow conversion with RAG"
  - "Compiler": "Visual design → RulePack/WorkflowPack JSON/YAML"
  - "Testing": "Pack execution simulation with sample data"
  - "Deployment": "Push to cortx-platform registries"
AI_CAPABILITIES:
  - "RAG Vector Store": "Embedded Treasury/compliance knowledge"
  - "NLP Processing": "Intent analysis, parameter extraction"
  - "Smart Config": "Auto-generate node properties with compliance"
COMPLIANCE: ["204 GTAS rules", "Treasury templates", "HIPAA patterns"]

Conventions & Standards

Commit Messages

Format: Conventional Commits

<type>(<scope>): <description>

[optional body]

[optional footer]

Types: feat, fix, docs, chore, test, refactor, perf, ci, build Example: feat(gateway): add health check endpoint

Branching Strategy

  • Main branch: main (protected, requires PR + CI)
  • Feature branches: feature/<name> or <username>/<feature>
  • Short-lived: merge within 2-3 days
  • No long-running branches

Testing Standards

  • Unit test coverage: >80%
  • Integration tests: Required for services
  • E2E tests: cortx-e2e repo
  • Test naming: test_<function>_<scenario>_<expected>

Documentation Standards

  • README: Required in every repo/module/service
  • FDD: Required for each repo
  • API docs: OpenAPI/Swagger for services
  • Inline comments: For complex logic only

Environment Management

  • Never commit secrets
  • Always provide .env.example
  • Use GCP Secret Manager for prod
  • Local dev: .env (gitignored)

File Templates Summary

1. Org-Level Templates (7 files)

  • .claude/agents/tech-lead-architect.md
  • .claude/agents/tech-architect.md
  • .claude/agents/backend-services-dev.md
  • .claude/agents/ui-frontend-developer.md
  • .claude/agents/functional-lead.md
  • .claude/agents/gcp-deployment-ops.md
  • .claude/agents/quality-assurance-lead.md

2. Org Docs (6 files)

  • docs/ai_governance/AI_RULES.md
  • docs/ai_governance/FOCUS.md
  • docs/prompts/DAILY_CLOSEOUT_PROMPT_ORG.md
  • docs/tracking/ENTERPRISE_ROADMAP.md
  • docs/tracking/QA_ASSESSMENT.md
  • docs/tracking/QA_RESPONSE.md

3. Org Infrastructure (10+ files)

  • infra/terraform/INDEX.md
  • infra/terraform/QUICK_START.md
  • infra/terraform/ARCHITECTURE.md
  • infra/terraform/main.tf
  • infra/terraform/backend.tf
  • infra/terraform/variables.tf
  • infra/terraform/outputs.tf
  • infra/terraform/versions.tf
  • infra/terraform/environments/*.tfvars (3 files)
  • Makefile (org-level)

4. Per-Repo Templates (×9 repos = 81+ files)

  • .claude/agents/{architect,coder,reviewer}.md (3 × 9 = 27)
  • Makefile (9)
  • CHANGELOG.md (9)
  • docs/{REPO}_FDD.md (9)
  • .env.example (9)
  • Enhanced README.md (9)
  • tests/ structure (9)

5. Service/Module Templates (as needed)

  • services/template/ (cortx-platform)
  • modules/template/ (each suite × 4 = 4)
  • packages/common-types/ (cortx-sdks)

Implementation Phases

Phase 1: Org-Level Foundation (Immediate)

  1. Create .claude/agents/ with 7 agent files
  2. Enhance docs/ with ai_governance/, prompts/, tracking/
  3. Set up DAILY_LOGS/ with template
  4. Create org-level Makefile
  5. Build out infra/terraform/ structure
  6. Add .env.example at org level

Deliverables: Org-wide infrastructure and standards Duration: 1 day

Phase 2: Per-Repo Standardization (Rolling)

For each repo (prioritize by dependency order):

  1. cortx-platform (foundational)
  2. cortx-sdks (depends on platform)
  3. cortx-packs (standalone)
  4. cortx-e2e (depends on platform)
  5. fedsuite, corpsuite, medsuite, govsuite (parallel)
  6. cortx-designer (depends on sdks)

Per repo:

  1. Add .claude/agents/ (3 files)
  2. Create Makefile
  3. Add CHANGELOG.md
  4. Create {REPO}_FDD.md
  5. Add .env.example
  6. Enhance README.md
  7. Structure tests/

Duration: 2-3 days per repo (can parallelize)

Phase 3: Templates & Examples (Support)

  1. Create service template (cortx-platform)
  2. Create module templates (each suite)
  3. Create shared packages (cortx-sdks)
  4. Document patterns in each FDD

Duration: 2-3 days

Phase 4: Documentation & Training (Ongoing)

  1. Complete all FDD documents
  2. Fill in ENTERPRISE_ROADMAP
  3. Set up QA_ASSESSMENT process
  4. Create developer onboarding guide
  5. Record Loom videos for key workflows

Duration: Ongoing, 1 week initial push

Success Criteria

Org-Level

✅ All 7 Claude agents defined with project context ✅ Terraform infrastructure documented and deployable ✅ QA spine established (roadmap, assessment, response) ✅ Daily logging template in use ✅ Org-level Makefile operational

Per-Repo

✅ Consistent .claude/agents/ across all 9 repos ✅ Working Makefile with standard targets ✅ CHANGELOG maintained ✅ FDD document completed ✅ README follows standard structure ✅ Tests runnable via make test ✅ .env.example provided

Developer Experience

✅ New developer can clone any repo and run make install && make dev ✅ Testing is consistent: make test ✅ Deployment is documented: make deploy ✅ Claude agents provide context-aware assistance ✅ Conventions are clear and followed

Post-Implementation Checklist

Org-Level

# Verify org structure
ls -la .claude/agents/                    # Should have 7 .md files
ls -la docs/ai_governance/                # AI_RULES.md, FOCUS.md
ls -la docs/tracking/                     # ENTERPRISE_ROADMAP.md, QA_*.md
ls -la infra/terraform/                   # All .tf files + docs
make help                                 # Should show org targets

# Test org operations
make status-all                           # Check all repos
make test-all                             # Run tests across repos

Per-Repo (run in each repo)

# Verify structure
ls -la .claude/agents/                    # architect.md, coder.md, reviewer.md
test -f Makefile && echo "✅ Makefile"
test -f CHANGELOG.md && echo "✅ CHANGELOG"
test -f docs/${REPO}_FDD.md && echo "✅ FDD"
test -f .env.example && echo "✅ .env.example"

# Test operations
make help                                 # Show available targets
make install                              # Install dependencies
make test                                 # Run tests
make lint                                 # Lint code
make build                                # Build (if applicable)

Integration Tests

# From cortx-e2e
make compose-up                           # Start services
make test-smoke                           # Smoke tests pass
make test-integration                     # Integration tests pass
make compose-down                         # Cleanup

Documentation

# Verify all FDDs exist
for repo in cortx-platform cortx-designer cortx-sdks cortx-packs cortx-e2e fedsuite corpsuite medsuite govsuite; do
  test -f $repo/docs/${repo}_FDD.md && echo "✅ $repo FDD" || echo "❌ Missing $repo FDD"
done

# Verify Claude agents
find . -name "agents" -type d -exec ls -l {} \;

Next Steps

  1. Review this adaptation plan with stakeholders
  2. Approve variable values (especially cloud resources, licensing)
  3. Prioritize repos for Phase 2 implementation
  4. Assign owners for each repo's standardization
  5. Begin Phase 1 (org-level foundation)

Appendix: Key Differences from Monorepo Template

Monorepo Template Multi-Repo Adaptation
Single turbo.json Per-repo build configs
Root package.json workspace Each repo independent
apps/, packages/, services/ in one repo Split across cortx-platform, cortx-sdks, suites
Single .claude/agents/ Org-level + per-repo agents
Single Makefile Org-level + per-repo Makefiles
Unified testing Per-repo tests + cortx-e2e integration
One FDD Per-repo FDD + org roadmap
Monorepo CI Per-repo CI + org-level orchestration

END OF ADAPTATION PLAN