Generate a Technology Code of Practice (TCoP) review document for a UK Government technology project
You are helping to conduct a Technology Code of Practice (TCoP) review for a UK Government technology project or programme.
$ARGUMENTS
The Technology Code of Practice is a set of 13 criteria to help government design, build and buy technology. It's used by the Digital Spend Control team to assess technology spending proposals.
TCoP Reference: https://www.gov.uk/guidance/the-technology-code-of-practice
Generate a comprehensive TCoP review document by:
Loading the template (with user override support):
.arckit/templates/tcop-review-template.md exists in the project root.arckit/templates/tcop-review-template.md (default)Tip: Users can customize templates with
$arckit-customize tcop
Read Available Documents:
Note: Before generating, scan
projects/for existing project directories. For each project, list allARC-*.mdartifacts, checkexternal/for reference documents, and check000-global/for cross-project policies. If no external docs exist but they would improve output, ask the user.
MANDATORY (warn if missing):
$arckit-requirements first$arckit-principles firstRECOMMENDED (read if available, note if missing):
OPTIONAL (read if available, skip silently if missing):
Assess compliance: Based on the user's description and any existing project documentation, assess compliance against all 13 TCoP points:
Read external documents and policies:
external/ files) — extract previous TCoP assessment results, departmental interpretations of TCoP points, remediation plans000-global/policies/) — extract approved technology lists, procurement policies, cloud-first mandatesprojects/000-global/external/ — extract enterprise technology standards, digital strategy documents, cross-project TCoP compliance evidenceprojects/{project-dir}/external/ and re-run, or skip.".arckit/references/citation-instructions.md. Place inline citation markers (e.g., [PP-C1]) next to findings informed by source documents and populate the "External References" section in the template.For each TCoP point:
Provide realistic assessments:
Generate compliance scorecard: Create a summary showing status of all 13 points
Prioritize actions: Identify critical issues requiring immediate attention
Detect version: Before generating the document ID, check if a previous version exists:
ARC-{PROJECT_ID}-TCOP-v*.md files in the project directoryBefore writing the file, read .arckit/references/quality-checklist.md and verify all Common Checks plus the TCOP per-type checks pass. Fix any failures before proceeding.
projects/[project-folder]/ARC-{PROJECT_ID}-TCOP-v${VERSION}.mdCRITICAL - Auto-Populate Document Control Fields:
Before completing the document, populate ALL document control fields in the header:
ARC-{PROJECT_ID}-TCOP-v{VERSION} (e.g., ARC-001-TCOP-v1.0)Auto-populated fields (populate these automatically):
[PROJECT_ID] → Extract from project path (e.g., "001" from "projects/001-project-name")[VERSION] → Determined version from step 8[DATE] / [YYYY-MM-DD] → Current date in YYYY-MM-DD format[DOCUMENT_TYPE_NAME] → "Technology Code of Practice Review"ARC-[PROJECT_ID]-TCOP-v[VERSION] → Construct using format from Step 1[COMMAND] → "arckit.tcop"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 (requirements, research, risks)[YYYY-MM-DD] for Review Date → Phase gate dates (Alpha/Beta/Live for compliance docs)Pending fields (leave as [PENDING] until manually updated):
[REVIEWER_NAME] → [PENDING][APPROVER_NAME] → [PENDING][DISTRIBUTION_LIST] → Default to "Project Team, Architecture Team" or [PENDING]| 1.0 | {DATE} | ArcKit AI | Initial creation from `$arckit-tcop` command | [PENDING] | [PENDING] |
The footer should be populated with:
**Generated by**: ArcKit `$arckit-tcop` 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]
## Document Control
| Field | Value |
|-------|-------|
| **Document ID** | ARC-001-TCOP-v1.0 |
| **Document Type** | {Document purpose} |
| **Project** | Windows 10 to Windows 11 Migration (Project 001) |
| **Classification** | OFFICIAL-SENSITIVE |
| **Status** | DRAFT |
| **Version** | 1.0 |
| **Created Date** | 2025-10-29 |
| **Last Modified** | 2025-10-29 |
| **Review Date** | 2025-11-30 |
| **Owner** | John Smith (Business Analyst) |
| **Reviewed By** | [PENDING] |
| **Approved By** | [PENDING] |
| **Distribution** | PM Team, Architecture Team, Dev Team |
## Revision History
| Version | Date | Author | Changes | Approved By | Approval Date |
|---------|------|--------|---------|-------------|---------------|
| 1.0 | 2025-10-29 | ArcKit AI | Initial creation from `$arckit-tcop` command | [PENDING] | [PENDING] |
The document must include:
When assessing compliance:
Common critical issues:
Project phases matter:
For AI/ML systems: Also consider requirements from the AI Playbook (may need ATRS - Algorithmic Transparency Record)
For public-facing services: Point 13 (Service Standard) is mandatory - must pass GDS service assessments
For Digital Spend Control submissions: Focus on points most relevant to spending approval:
Data protection: If processing personal data, Point 7 is critical - DPIA completion is mandatory before going live
Be aware of:
# Technology Code of Practice (TCoP) Review
**Project**: Benefits Eligibility Chatbot
**Overall TCoP Compliance**: Partially Compliant
## TCoP Point 1: Define User Needs
**Status**: ✅ Compliant
**Evidence**: User research completed with 50+ DWP claimants...
[Checked items and gaps listed]
## TCoP Point 6: Make Things Secure
**Status**: ⚠️ Partially Compliant
**Evidence**: Threat model exists, but penetration testing not yet completed...
**Gaps/Actions Required**:
- Schedule pen test before Private Beta (HIGH PRIORITY)
...
## Overall Compliance Summary
**Score**: 9/13 Compliant (3 Partially Compliant, 1 N/A)
**Critical Issues**:
1. DPIA not completed (Point 7) - BLOCKING for Beta
2. Accessibility audit incomplete (Point 2) - Required for Beta
Generate the TCoP review now based on the project information provided.
< or > (e.g., < 3 seconds, > 99.9% uptime) to prevent markdown renderers from interpreting them as HTML tags or emoji