Arckit Gcloud Search

IMPORTANT: Check prerequisites before proceeding:

a. Project with Requirements (MUST exist):

• Check if user specified a project name/number
• Look for projects/[project]/ARC-*-REQ-v*.md
• If NOT found: ERROR "Run $arckit-requirements first to define project needs"

b. Architecture Principles (RECOMMENDED):

• Check if projects/000-global/ARC-000-PRIN-*.md exists
• If exists: Read it for cloud strategy, security requirements
• If NOT found: WARN "Consider running $arckit-principles to define cloud governance"

2. Load Project Context

Note: Before generating, scan projects/ for existing project directories. For each project, list all ARC-*.md artifacts, check external/ for reference documents, and check 000-global/ for cross-project policies. If no external docs exist but they would improve output, ask the user.

1. Read the REQ (Requirements) artifact for the target project
2. Read the PRIN (Architecture Principles, in 000-global) if available
3. Parse user input for specific service types needed

3. Analyze Cloud Service Needs

Scan requirements to identify what cloud services are needed:

Look for:

• INT-xxx mentioning: "cloud hosting", "SaaS", "IaaS", "PaaS", "monitoring", "email service"
• NFR-xxx mentioning: "uptime", "availability", "disaster recovery", "cloud infrastructure"
• FR-xxx mentioning: "platform", "service", "hosting", "managed service"

Service categories to identify:

• Cloud Hosting: IaaS, VMs, containers, Kubernetes
• Cloud Software: SaaS platforms, tools, applications
• Cloud Support: Managed services, monitoring, backup
• Specialized Services: Email, CDN, databases, analytics

Determine:

• Primary service category needed
• Must-have requirements (from MUST priority)
• Desirable requirements (from SHOULD priority)
• Compliance needs (security certifications, data residency)

CRITICAL - Auto-Populate Document Control Fields:

Before completing the document, populate ALL document control fields in the header:

Construct Document ID:

• Document ID: ARC-{PROJECT_ID}-GCLD-v{VERSION} (e.g., ARC-001-GCLD-v1.0)

Populate Required Fields:

Auto-populated fields (populate these automatically):

• [PROJECT_ID] → Extract from project path (e.g., "001" from "projects/001-project-name")
• [VERSION] → "1.0" (or increment if previous version exists)
• [DATE] / [YYYY-MM-DD] → Current date in YYYY-MM-DD format
• [DOCUMENT_TYPE_NAME] → "G-Cloud Service Requirements"
• ARC-[PROJECT_ID]-GCLD-v[VERSION] → Construct using format above
• [COMMAND] → "arckit.gcloud-search"

User-provided fields (extract from project metadata or user input):

• [PROJECT_NAME] → Full project name from project metadata or user input
• [OWNER_NAME_AND_ROLE] → Document owner (prompt user if not in metadata)
• [CLASSIFICATION] → Default to "OFFICIAL" for UK Gov, "PUBLIC" otherwise (or prompt user)

Calculated fields:

• [YYYY-MM-DD] for Review Date → Current date + 30 days

Pending fields (leave as [PENDING] until manually updated):

• [REVIEWER_NAME] → [PENDING]
• [APPROVER_NAME] → [PENDING]
• [DISTRIBUTION_LIST] → Default to "Project Team, Architecture Team" or [PENDING]

Populate Revision History:

| 1.0 | {DATE} | ArcKit AI | Initial creation from `$arckit-gcloud-search` command | [PENDING] | [PENDING] |

Populate Generation Metadata Footer:

The footer should be populated with:

**Generated by**: ArcKit `$arckit-gcloud-search` command
**Generated on**: {DATE} {TIME} GMT
**ArcKit Version**: {ARCKIT_VERSION}
**Project**: {PROJECT_NAME} (Project {PROJECT_ID})
**AI Model**: [Use actual model name, e.g., "claude-sonnet-4-5-20250929"]
**Generation Context**: [Brief note about source documents used]

4. Generate G-Cloud Requirements Document

Create directory: projects/[project]/procurement/

Before writing the file, read .arckit/references/quality-checklist.md and verify all Common Checks plus the GCLD per-type checks pass. Fix any failures before proceeding.

Generate projects/[project]/procurement/ARC-{PROJECT_ID}-GCLD-v1.0.md:

# UK Digital Marketplace: G-Cloud Service Procurement

**Framework**: G-Cloud
**Service Category**: [Cloud Hosting / Cloud Software / Cloud Support]
**Generated**: [DATE]
**Project**: [PROJECT_NAME]
**Project ID**: [PROJECT_ID]
**Requirements Source**: [Link to ARC-*-REQ-*.md]

---

## 1. Service Overview

### 1.1 What We Need

[Describe what cloud service/software is needed - from ARC-*-REQ-*.md]

### 1.2 Why We Need It

[Business context from BR-xxx requirements]

### 1.3 Strategic Alignment

**Architecture Principles** (if exists):
[Reference relevant principles, especially cloud strategy, security principles]

### 1.4 Integration Context

[Extract from INT-xxx requirements - what systems this service will integrate with]

---

## 2. Must-Have Requirements

The service **MUST** provide:

[Extract MUST requirements from ARC-*-REQ-*.md]

### 2.1 Functional Requirements
- **[Requirement 1]**: [From FR-xxx or NFR-xxx]
- **[Requirement 2]**: [From FR-xxx or NFR-xxx]
- **[Requirement 3]**: [From FR-xxx or NFR-xxx]

### 2.2 Performance Requirements
- **[Performance Target]**: [From NFR-P-xxx with measurable metric]
- **[Performance Target]**: [From NFR-P-xxx with measurable metric]

### 2.3 Security Requirements
- **[Security Requirement]**: [From NFR-S-xxx or ARC-000-PRIN-*.md]
- **[Security Requirement]**: [From NFR-S-xxx or ARC-000-PRIN-*.md]

### 2.4 Compliance Requirements
- **[Compliance Standard]**: [From NFR-C-xxx]
- **[Certification Needed]**: [e.g., ISO 27001, Cyber Essentials Plus]
- **[Data Residency]**: [e.g., UK data centers only, GDPR compliance]

### 2.5 Integration Requirements
- **[Integration Point]**: [From INT-xxx]
- **[Integration Method]**: [API, webhook, file transfer, etc.]

---

## 3. Desirable Requirements

The service **SHOULD** provide:

[Extract SHOULD requirements from ARC-*-REQ-*.md]
- [Desirable feature 1]
- [Desirable feature 2]
- [Desirable feature 3]

---

## 4. Success Criteria

[Extract measurable success criteria from ARC-*-REQ-*.md BR-xxx]

- [Criterion 1 with metric]
- [Criterion 2 with metric]
- [Criterion 3 with metric]

---

## 5. Evaluation Criteria

### 5.1 Functional Fit (50%)

- **Must-Have Coverage** (30%): Meets all MUST requirements
- **Desirable Features** (20%): Coverage of SHOULD requirements

### 5.2 Reliability & Performance (25%)

- **Service Level Agreements** (10%): Uptime guarantees, support response times
- **Performance Specifications** (10%): Meets NFR-P-xxx requirements
- **Disaster Recovery** (5%): DR/BC capabilities

### 5.3 Security & Compliance (15%)

- **Security Certifications** (5%): ISO 27001, Cyber Essentials Plus, etc.
- **Data Protection** (5%): GDPR compliance, data residency
- **Compliance Standards** (5%): Industry-specific certifications

### 5.4 Cost & Support (10%)

- **Pricing Model** (5%): Transparency, predictability, value
- **Support Availability** (3%): Support hours, escalation process
- **Contract Flexibility** (2%): Terms, exit strategy, lock-in

5. Search Digital Marketplace (WebSearch)

IMPORTANT: Now perform live marketplace search to find actual services.

For each service category identified:

5.1 Build Search Query

Create search query: