Skip to content

DEPENDENCY-MATRIX.md

Latest commit

 

History

History
412 lines (348 loc) · 32.2 KB

DEPENDENCY-MATRIX.md

File metadata and controls

412 lines (348 loc) · 32.2 KB
Raw

ArcKit Command Dependency Structure Matrix (DSM)

This matrix shows which commands depend on outputs from other commands.

Legend:

  • M = MANDATORY dependency (command will fail without it)
  • R = RECOMMENDED dependency (command works better with it)
  • O = OPTIONAL dependency (command can use if available)
  • Empty = No dependency

Reading the Matrix:

  • Rows = Commands that produce outputs
  • Columns = Commands that consume those outputs
  • Example: If row "principles" has "R" in column "stakeholders", it means stakeholders RECOMMENDS having principles first

Dependency Structure Matrix

PRODUCES → plan principles stakeholders risk sobc requirements data-model data-mesh-contract platform-design dpia research azure-research aws-research datascout wardley roadmap strategy adr sow dos gcloud-search gcloud-clarify evaluate hld-review dld-review backlog trello diagram servicenow devops mlops finops operationalize traceability analyze principles-compliance service-assessment tcop ai-playbook atrs secure mod-secure jsp-936 story pages
plan - R R R O O O R O O R R M O R R
principles - M R R R M R R R M M M M R M M R R R M M M M R
stakeholders O - M M M R O R R O R M R R R M O O R R R R R R R R
risk - M R O R R O O R R R R R R R R R R M R R
sobc O O - M O R R O R R R R R
requirements - M M M M M M M M M M M M M M R M M M M M M M M M M M R R M M M M M M M R R
data-model - M O M R R O O O R R R R R R R R R
data-mesh-contract - O
platform-design O R - O O R R R R
dpia - O R O O O R R R R R R R R R
research - R R R O R R R O R
azure-research - R R R R R R R R
aws-research - R R R R R R R R
datascout R O R - R O R R
wardley R O - R R O R R
roadmap O O - R O R R
strategy - R R
adr - R
sow - O R R R
dos - R O
gcloud-search - M O
gcloud-clarify - R O
evaluate - R R
hld-review R - M M M R R
dld-review O - R M R R
backlog - M R
trello -
diagram O R R - M R R R R R O O R
servicenow - R O R
devops - R R R
mlops - R R
finops - R R
operationalize - R R
traceability O - R R R R
analyze - O R O O R
principles-compliance - R R
service-assessment O O - R R
tcop R R R - R
ai-playbook R O R - R R R
atrs O - R R
secure R O R R O O - R O R R
mod-secure O R O - R R
jsp-936 O O - R
story O O - R
pages -
HLD (external) M O R M O R R
DLD (external) M M M R R

Command Groups by Dependency Level

Tier 0: Foundation (No Mandatory Dependencies)

These commands can run first:

  • plan - Project planning and timeline (can optionally read: stakeholders, requirements, principles, sobc, risk if they exist)
  • principles - Architecture principles

Tier 1: Strategic Context (Depends on Foundation)

  • stakeholders → Depends on: principles (R)

Tier 1.5: Risk Assessment (Depends on Stakeholders)

  • risk → Depends on: stakeholders (M), principles (R)

Tier 2: Business Justification

  • sobc → Depends on: stakeholders (M), risk (R), principles (R)

Tier 3: Requirements Definition

  • requirements → Depends on: stakeholders (R), sobc (R), principles (R)

Tier 3.5: Strategic Planning (Platform Strategy, Roadmaps & Strategy Synthesis)

  • platform-design → Depends on: principles (M), stakeholders (R), requirements (R), wardley (R), risk (O), sobc (O), data-model (O)
    • Note: Designs multi-sided platform strategy using Platform Design Toolkit (PDT) methodology
    • Best run after requirements when designing ecosystem-based platforms (Government as a Platform, marketplaces, data platforms)
    • Can run earlier if stakeholders and principles exist (requirements/wardley are recommended for better auto-population)
  • roadmap → Depends on: principles (M), stakeholders (R), requirements (R), wardley (R), risk (R)
    • Note: Creates strategic architecture roadmap with multi-year timeline and capability evolution
    • Requires principles as foundation; stakeholders and requirements provide strategic context
  • strategy → Depends on: principles (M), stakeholders (M), wardley (R), roadmap (R), sobc (R), risk (O)
    • Note: Synthesises strategic artifacts into executive-level Architecture Strategy document
    • Requires both principles AND stakeholders as mandatory inputs (unique among ArcKit commands)
    • Best run after creating principles, stakeholders, wardley, roadmap, and sobc for comprehensive strategy

Tier 4: Detailed Design (Depends on Requirements)

Most commands in this tier require or strongly recommend ARC--REQ-.md:

  • data-model → Depends on: requirements (M), stakeholders (R), sobc (O)
  • dpia → Depends on: data-model (M), requirements (M), principles (R), stakeholders (R), risk (R)
  • research → Depends on: requirements (M), stakeholders (R), data-model (R), platform-design (R)
  • azure-research → Depends on: requirements (M), data-model (R), stakeholders (R), MCP Server (External)
    • Note: Requires Microsoft Learn MCP server to be installed for authoritative Azure documentation
  • aws-research → Depends on: requirements (M), data-model (R), stakeholders (R), MCP Server (External)
    • Note: Requires AWS Knowledge MCP server to be installed for authoritative AWS documentation
  • datascout → Depends on: requirements (M), data-model (O), stakeholders (R), principles (R)
    • Note: Discovers external data sources (APIs, datasets, open data portals) to fulfil project data requirements
    • Bidirectional with data-model: data-model is optional input, datascout recommends data-model updates as output
  • wardley → Depends on: requirements (R), principles (R)
    • Note: Can create initial map without prerequisites; better maps with requirements and principles
  • diagram → Depends on: requirements (M), platform-design (R)
  • adr → Depends on: principles (R), requirements (R), stakeholders (O), research (O), wardley (O)
    • Note: Architecture Decision Records; principles recommended but can create decisions without them
  • data-mesh-contract → Depends on: principles (M), data-model (R), stakeholders (R), diagram (R)
    • Note: Federated data product contracts for mesh architectures; requires principles for governance standards

Tier 5: Procurement (Depends on Requirements)

Most procurement commands require ARC--REQ-.md:

  • sow → Depends on: requirements (M), research (R)
  • dos → Depends on: requirements (M), stakeholders (M), sobc (R), research (R)
  • gcloud-search → Depends on: requirements (R), Digital Marketplace access (External)
    • Note: Requirements recommended for search context but not mandatory
  • gcloud-clarify → Depends on: requirements (M), gcloud-search (M)
  • evaluate → Depends on: requirements (M), sow (M), principles (R), research (R), gcloud-clarify (R)

Tier 6: Design Reviews (Depends on Design Documents + Requirements)

  • hld-review → Depends on: requirements (M), principles (M), HLD (M)
  • dld-review → Depends on: requirements (M), principles (M), HLD (M), DLD (M)

Tier 7: Implementation Planning (Depends on Design Reviews)

  • backlog → Depends on: requirements (M), HLD (M), stakeholders (R), risk (R)

Tier 7.5: Backlog Export (Depends on Backlog)

  • trello → Depends on: backlog (M) — specifically the JSON export (ARC-*-BKLG-*.json)
    • Note: Exports backlog to Trello board with sprint lists, labelled cards, and acceptance criteria checklists
    • Requires TRELLO_API_KEY and TRELLO_TOKEN environment variables

Tier 8: Operations (Depends on Architecture)

  • servicenow → Depends on: requirements (M), diagram (M), principles (R), HLD/DLD (R)
  • devops → Depends on: requirements (M), diagram (M), principles (R), HLD/DLD (R)
  • mlops → Depends on: requirements (M), data-model (R), ai-playbook (R), research (R) [for AI projects]
  • finops → Depends on: requirements (M), devops (R), diagram (R), principles (R)
  • operationalize → Depends on: requirements (M), diagram (M), HLD/DLD (R), principles (R), risk (R)
  • traceability → Depends on: requirements (M), HLD (M), DLD (M), data-model (R)

Tier 9: Quality Assurance (Can Run Before or After Compliance)

  • analyze → Depends on: principles (M), requirements (R), stakeholders (R), all other artifacts (O)
    • Note: Requires principles as foundation; other dependencies are optional - analyze identifies gaps for missing artifacts

Tier 10: Compliance Assessment (Depends on Multiple Artifacts)

These assess compliance across the project:

  • principles-compliance → Depends on: principles (M), requirements (R), stakeholders (R), risk (R), data-model (R), platform-design (R), HLD (R), DLD (R), hld-review (R), dld-review (R), traceability (R), dpia (R), tcop (R), secure (R), mod-secure (R)
    • Note: All dependencies except principles are RECOMMENDED - better assessment with more artifacts
  • service-assessment → Depends on: requirements (M), plan (R), data-model (R), platform-design (O), principles (R), stakeholders (R), risk (R), analyze (R), hld-review (R), dld-review (R), diagram (R), traceability (R), wardley (R), tcop (O), ai-playbook (O), atrs (O), secure (O), mod-secure (O), jsp-936 (O), principles-compliance (O)
    • Note: Compliance artifacts are optional - service-assessment identifies them as gaps if missing
  • tcop → Depends on: requirements (M), principles (R), diagram (R)
  • ai-playbook → Depends on: requirements (O) [if AI system]
  • atrs → Depends on: requirements (M), principles (R), data-model (R) [for AI/algorithmic systems]
  • secure → Depends on: requirements (M), principles (M), risk (R)
  • mod-secure → Depends on: requirements (M), principles (M), risk (R)
  • jsp-936 → Depends on: requirements (M), principles (M), mod-secure (R), risk (R) [for MOD AI systems]

Tier 11: Project Story & Reporting (Depends on All Artifacts)

Final reporting command that creates comprehensive project narrative:

  • story → Depends on: principles (M), all other artifacts (R)
    • Note: Requires principles as foundation; recommends multiple artifacts for comprehensive narrative
    • Generates comprehensive historical record with timeline analysis, traceability chains, governance achievements
    • Best run at project milestones or completion when most/all artifacts are complete

Tier 12: Documentation Publishing (Utility)

Publishing command that generates documentation site:

  • pages → Depends on: All document-producing artifacts (R)
    • Note: pages indexes and displays all project documents - more documents = better site
    • Recommended dependencies: principles, stakeholders, risk, sobc, requirements, data-model, dpia, research, wardley, roadmap, adr, sow, evaluate, hld-review, dld-review, backlog, diagram, servicenow, traceability, analyze, principles-compliance, service-assessment, tcop, ai-playbook, atrs, secure, mod-secure, jsp-936, story, HLD, DLD
    • Generates GitHub Pages site with Mermaid diagram support
    • Best run when project has substantial documentation to publish

Critical Paths

Standard Project Path (Non-AI, Non-Government)

plan → principles → stakeholders → risk → sobc → requirements → research → wardley →
sow/evaluate → hld-review → backlog → servicenow → devops → operationalize →
traceability → principles-compliance → analyze → story

UK Government Project Path

plan → principles → stakeholders → risk → sobc → requirements → datascout → data-model → research →
wardley → gcloud-search → gcloud-clarify → evaluate → hld-review → dld-review →
backlog → servicenow → devops → operationalize → traceability →
tcop → secure → principles-compliance → analyze → service-assessment → story

UK Government Platform Strategy Path

plan → principles → stakeholders → risk → sobc → requirements → platform-design → datascout → data-model → research →
wardley → gcloud-search → evaluate → hld-review → dld-review → backlog → servicenow →
devops → operationalize → traceability → tcop → secure → principles-compliance →
analyze → service-assessment → story

UK Government AI Project Path

plan → principles → stakeholders → risk → sobc → requirements → datascout → data-model → research →
wardley → gcloud-search → evaluate → hld-review → dld-review → backlog → servicenow →
devops → mlops → operationalize → traceability → tcop → ai-playbook → atrs → secure →
principles-compliance → analyze → service-assessment → story

MOD Defence Project Path

plan → principles → stakeholders → risk → sobc → requirements → datascout → data-model → research →
wardley → dos → evaluate → hld-review → dld-review → backlog → servicenow →
devops → operationalize → traceability → tcop → mod-secure → principles-compliance →
analyze → service-assessment → story

MOD Defence AI Project Path

plan → principles → stakeholders → risk → sobc → requirements → datascout → data-model → research →
wardley → dos → evaluate → hld-review → dld-review → backlog → servicenow →
devops → mlops → operationalize → traceability → tcop → mod-secure → jsp-936 →
principles-compliance → analyze → service-assessment → story

Note: analyze and service-assessment can also run earlier in the workflow to identify gaps in missing artifacts (all their dependencies are optional). The story command can be run at any project milestone to create a narrative snapshot, but is most comprehensive when run after all artifacts are complete. The paths above show the complete workflow with story as the final reporting step.

Platform Design: The platform-design command is used when designing multi-sided platforms (Government as a Platform, marketplaces, data platforms) and should be inserted after requirements definition but before detailed design. See "UK Government Platform Strategy Path" above.

Artifact Dependencies Summary

Commands That Are Frequently Consumed (High Fan-In)

ARC--REQ-.md - consumed by 37 commands:

  • data-model (M), data-mesh-contract (M), platform-design (M), dpia (M), research (M), azure-research (M), aws-research (M), datascout (M), wardley (M), roadmap (M), adr (M), sow (M), dos (M), gcloud-search (R), gcloud-clarify (M), evaluate (M), hld-review (M), dld-review (M), backlog (M), diagram (M), servicenow (M), devops (M), mlops (M), finops (M), operationalize (M), traceability (R), analyze (R), principles-compliance (M), service-assessment (M), tcop (M), ai-playbook (M), atrs (M), secure (M), mod-secure (M), jsp-936 (M), story (R), pages (R)

ARC-000-PRIN-v.md* - consumed by 21 commands:

  • stakeholders (M), risk (R), sobc (R), requirements (R), platform-design (M), dpia (R), wardley (M), roadmap (M), strategy (M), sow (M), dos (R), evaluate (M), hld-review (M), servicenow (R), mlops (R), traceability (R), analyze (M), service-assessment (M), atrs (M), secure (M), story (R)

ARC--STKE-.md - consumed by 22 commands:

  • risk (M), sobc (M), requirements (M), data-model (R), data-mesh-contract (O), platform-design (R), dpia (R), research (O), azure-research (R), aws-research (M), datascout (R), wardley (O), roadmap (O), strategy (M), adr (R), hld-review (R), operationalize (R), traceability (R), analyze (R), principles-compliance (R), mod-secure (R), jsp-936 (R)

HLD (external document) - consumed by 7 commands:

  • dld-review (M), backlog (M), diagram (R), servicenow (R), traceability (M), hld-review (validates it), service-assessment (M)
    • Note: analyze reads HLD directly if available (O), not via hld-review

ARC--PLAT-.md - consumed by 6 commands:

  • research (R), wardley (R), diagram (R), analyze (M), principles-compliance (R), service-assessment (R)

Commands That Produce Critical Artifacts (High Fan-Out)

requirements produces ARC--REQ-.md → consumed by 37 commands (highest) principles produces ARC-000-PRIN-v*.md → consumed by 21 commands stakeholders produces ARC--STKE-.md → consumed by 22 commands HLD (external) → consumed by 7 commands risk produces ARC--RISK-.md → consumed by 6 commands platform-design produces ARC--PLAT-v.md → consumed by 6 commands

Design Notes

  1. ARC--REQ-.md is the central artifact - Nearly all downstream commands depend on it
  2. ARC-000-PRIN-v.md is the governance foundation* - All design reviews check against principles
  3. Strategic order matters - stakeholders → risk → sobc → requirements ensures business justification before technical work
  4. Platform strategy bridges business and technical - platform-design sits between requirements (business needs) and design (technical architecture), useful for ecosystem-based platforms
  5. Quality gates can run iteratively - analyze and service-assessment have optional dependencies, allowing them to run early (identifying gaps) or late (validating completeness)
  6. Compliance assessments feed quality gates - tcop, ai-playbook, atrs, secure, mod-secure, jsp-936 outputs are optionally consumed by analyze and service-assessment
  7. External artifacts - HLD and DLD are created outside ArcKit but validated by hld-review/dld-review commands

Version

  • ArcKit Version: 1.4.0
  • Matrix Date: 2026-02-05
  • Commands Documented: 46
  • Matrix Rows: 47 (45 document-generating commands + 2 external documents)
  • Note: /arckit.customize (46th command) is a utility command not in the matrix — it has no dependencies and produces no outputs consumed by other commands

Changelog

2026-02-05 - Added Template Customization Command

  • Added: /arckit.customize command (46th ArcKit command) for copying templates to .arckit/templates-custom/
  • Not in matrix: Utility command with no dependencies and no outputs consumed by other commands
  • Purpose: Enables template customization that persists across arckit init updates

2026-02-05 - Added Architecture Strategy Command

  • Added: /arckit.strategy command (45th ArcKit command) for synthesising strategic artifacts into executive-level Architecture Strategy document
  • Added: strategy row and column to dependency matrix
  • Updated: Tier 3.5 Strategic Planning to include strategy command
  • Dependencies: principles (M), stakeholders (M), wardley (R), roadmap (R), sobc (R), risk (O)
  • Consumed by: story (R), pages (R)
  • Note: Unique among ArcKit commands in requiring TWO mandatory inputs (principles AND stakeholders)
  • Purpose: Creates single coherent strategic narrative from multiple strategic artifacts for executive stakeholders

2026-02-04 - Added Trello Export Command

  • Added: /arckit.trello command (44th ArcKit command) for exporting product backlog to Trello boards
  • Added: trello row and column to dependency matrix
  • Added: Tier 7.5 Backlog Export for trello command
  • Dependencies: backlog (M) — reads ARC-*-BKLG-*.json
  • Consumed by: None (external Trello board output)
  • Note: Requires TRELLO_API_KEY and TRELLO_TOKEN environment variables; uses Trello REST API via curl

2026-02-01 - Added Data Source Discovery Command

  • Added: /arckit.datascout command (43rd ArcKit command) for discovering external data sources (APIs, datasets, open data portals, commercial providers)
  • Added: datascout row and column to dependency matrix
  • Updated: Tier 4 Detailed Design to include datascout command
  • Dependencies: requirements (M), data-model (O), stakeholders (R), principles (R)
  • Consumed by: data-model (R), research (R), adr (R), dpia (O), diagram (O), traceability (R), pages (R)
  • Note: Bidirectional with data-model; prioritises UK Government open data sources (TCoP Point 10)

2026-01-29 - Added AWS Research Command

  • Added: /arckit.aws-research command (42nd ArcKit command) for AWS-specific technology research using AWS Knowledge MCP server
  • Added: aws-research row and column to dependency matrix
  • Updated: Tier 4 Detailed Design to include aws-research command
  • Dependencies: requirements (M), data-model (R), stakeholders (R), MCP Server (External)
  • Consumed by: diagram (R), devops (R), finops (R), adr (R), pages (R)
  • Note: Requires AWS Knowledge MCP server for authoritative AWS documentation

2026-01-29 - Added Azure Research Command

  • Added: /arckit.azure-research command (41st ArcKit command) for Azure-specific technology research using Microsoft Learn MCP server
  • Added: azure-research row and column to dependency matrix
  • Updated: Tier 4 Detailed Design to include azure-research command
  • Dependencies: requirements (M), data-model (R), stakeholders (R), MCP Server (External)
  • Consumed by: diagram (R), devops (R), finops (R), adr (R), secure (O), pages (R)
  • Note: Requires Microsoft Learn MCP server for authoritative Azure documentation

2026-01-28 - Added Missing Operations Commands to Matrix

  • Fixed: Added devops, mlops, finops, operationalize rows and columns to the matrix
  • Updated: ARC--REQ-.md consumption count from 23 to 27 commands
  • Updated: ARC-000-PRIN-v*.md consumption count from 15 to 17 commands
  • Note: These commands were documented in Tier 8 but missing from the actual DSM table

2026-01-28 - Standardized Filename Patterns

  • Updated: All filename references now use Document ID pattern ARC-{PROJECT_ID}-{TYPE}-v*.md
  • Updated: Multi-instance types use ARC-{PROJECT_ID}-{TYPE}-{NUM}-v*.md (ADR, DIAG, WARD, DMC)
  • Updated: Subdirectory references use explicit patterns (wardley-maps/ARC-*-WARD-*.md, diagrams/ARC-*-DIAG-*.md)
  • Updated: Vendor submissions use versioned pattern (hld-v*.md, dld-v*.md)
  • Version: Bumped to 1.0.0

2026-01-22 - Added Pages Command

  • Added: /arckit.pages command (40th ArcKit command) for GitHub Pages documentation site generation with Mermaid diagram support
  • Category: Documentation & Publishing
  • Dependencies: None (utility command)

2026-01-21 - Added FinOps Command

  • Added: /arckit.finops command (39th ArcKit command) for FinOps strategy with cloud cost management, optimization, governance, and forecasting
  • Updated: Tier 8 Operations to include finops command
  • Dependencies: requirements (M), devops (R), diagram (R), principles (R)

2026-01-09 - Added DevOps, MLOps, and Operationalize Commands

  • Added: /arckit.devops command (34th ArcKit command) for DevOps strategy with CI/CD pipelines, IaC, container orchestration
  • Added: /arckit.mlops command (35th ArcKit command) for MLOps strategy with model lifecycle, training pipelines, serving, monitoring
  • Added: /arckit.operationalize command (36th ArcKit command) for operational readiness with SRE practices, runbooks, DR/BCP
  • Updated: Tier 8 Operations to include devops, mlops (AI projects), operationalize commands
  • Updated: All 6 critical paths to include new commands in operations phase
  • Dependencies:
    • devops: requirements (M), diagram (R), research (R), principles (R)
    • mlops: requirements (M), data-model (R), ai-playbook (R), research (R)
    • operationalize: requirements (M), servicenow (R), diagram (R), risk (R)

2025-01-06 - Added Platform Design Command

  • Added: /arckit.platform-design command (33rd ArcKit command) for multi-sided platform strategy design using Platform Design Toolkit (PDT) methodology
  • Added: platform-design row and column to dependency matrix
  • Added: New critical path: "UK Government Platform Strategy Path" showing where platform-design fits
  • Added: Tier 3.5 "Strategic Planning (Platform Strategy)" for platform-design placement
  • Updated: Tier 4 commands to optionally consume platform-design (research R, wardley R, diagram R)
  • Updated: analyze to consume platform-design (O), principles-compliance (R), service-assessment (O)
  • Dependencies: principles (M), stakeholders (R), requirements (R), wardley (R), risk (O), sobc (O), data-model (O)
  • Consumed by: research (R), wardley (R), diagram (R), analyze (M), principles-compliance (R), service-assessment (R)
  • Use case: Designing Government as a Platform (GaaP) services, data marketplaces, multi-sided platforms

2025-11-04 - Added Principles Compliance Command

  • Added: /arckit.principles-compliance command for measuring architecture principles adherence
  • Added: principles-compliance row and column to dependency matrix
  • Updated: All critical paths to include principles-compliance assessment
  • Updated: Tier 10 description to include principles-compliance command
  • Updated: service-assessment to optionally consume principles-compliance output (O)
  • Dependencies: principles (M), requirements (R), stakeholders (R), risk (R), data-model (R), HLD (R), DLD (R), hld-review (R), dld-review (R), traceability (R), dpia (R), tcop (R), secure (R), mod-secure (R)

2025-11-02 - Critical Fixes + Optional Dependencies

  • Added: analyze row showing optional dependencies on all artifacts
  • Fixed: service-assessment compliance dependencies changed from M to O (tcop, ai-playbook, atrs, secure, mod-secure, jsp-936)
  • Fixed: analyze compliance dependencies changed from M to O (tcop, ai-playbook, atrs, mod-secure)
  • Updated: Critical paths reordered to show compliance commands before quality gates
  • Updated: Tier 9 and Tier 10 descriptions to reflect optional dependencies and iterative execution
  • Added: 23 optional dependencies to complete matrix:
    • plan: principles, stakeholders, risk, sobc, requirements (5)
    • diagram: principles, DLD, tcop, ai-playbook, atrs (5)
    • wardley: principles, tcop, ai-playbook, atrs (4)
    • tcop: diagram, wardley (2)
    • ai-playbook: diagram, wardley, atrs (3)
    • atrs: diagram, wardley (2)
    • secure: diagram (1)
    • mod-secure: diagram (1)
    • jsp-936: data-model, diagram (2)
    • sow: dos, hld-review (2)
    • DLD: diagram (1)
  • Updated Templates:
    • architecture-diagram-template.md: Added ATRS to Linked Artifacts
    • wardley-map-template.md: Added AI Playbook/ATRS mapping sections for AI systems