Arckit Wardley Gameplay

The 11 gameplay categories are: A (User Perception), B (Accelerators), C (De-accelerators), D (Dealing with Toxicity), E (Market), F (Defensive), G (Attacking), H (Ecosystem), I (Competitor), J (Positional), K (Poison).

User Input

$ARGUMENTS

Step 1: Read Available Documents

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.

MANDATORY (warn if missing):

• WARD (Wardley Map, in projects/{project}/wardley-maps/) — Extract: all components with evolution positions, dependencies, inertia points, build/buy decisions already made, map title and strategic question
  • If missing: warn user — "A Wardley Map (WARD artifact) is required before running gameplay analysis. Please run $arckit-wardley first to create your map."
  • Do not proceed without a WARD artifact; the gameplay analysis has no basis without component positions

RECOMMENDED (read if available, note if missing):

• WCLM (Climate Assessment) — Extract: active climatic patterns, evolution velocity predictions, war/peace/wonder phase assessment. Informs which plays are timely.
• WDOC (Doctrine Assessment) — Extract: doctrine maturity scores, identified weaknesses. Weak doctrine constrains which plays can be executed successfully.

OPTIONAL (read if available, skip silently if missing):

• RSCH / AWRS / AZRS (Research) — Extract: vendor landscape, market dynamics, competitive intelligence. Enriches competitor and market gameplay options.
• PRIN (Architecture Principles, in 000-global) — Extract: strategic principles, technology standards, ethical constraints. Filters out plays incompatible with organisational values.

Understand the Strategic Context:

• What is the core strategic question the map was built to answer?
• What decisions need to be made? (Build vs Buy, market entry, competitive response, ecosystem play)
• What is the organisation's risk tolerance? (LG/N plays only, or all alignments considered?)
• What time horizon? (Immediate: 0-3 months, Near: 3-12 months, Strategic: 12-24 months)

Step 1b: Read external documents and policies

• Read any external documents listed in the project context (external/ files) — extract existing strategic analysis, competitive intelligence, market research
• Read any enterprise standards in projects/000-global/external/ — extract cross-project strategic context, portfolio-level plays in progress
• If no external strategic documents found but they would improve gameplay selection, note: "External competitive intelligence or market research documents would enrich this analysis. Place them in projects/{project-dir}/external/ and re-run."
• Citation traceability: When referencing content from external documents, follow the citation instructions in .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.

Step 2: Read Reference Material

Read .arckit/skills/wardley-mapping/references/gameplay-patterns.md — this is the full 60+ gameplay catalog across 11 categories with D&D alignments, Play-Position Matrix, compatibility tables, anti-patterns, and case study summaries. This file is the authoritative source for all gameplay descriptions, applicability guidance, and compatibility rules used in Steps 4-9 below.

Step 3: Extract Map Context

From the WARD artifact, extract the following structured information that will drive gameplay selection:

Component Inventory:

For each component on the map, record:

• Component name
• Visibility position (0.0-1.0)
• Evolution position (0.0-1.0) and corresponding stage (Genesis/Custom-Built/Product/Commodity)
• Dependencies (what it depends on, what depends on it)
• Inertia indicators (if any noted in the WARD artifact)
• Build/buy/reuse decision already made (if recorded)

Strategic Position Summary:

• Total components: {count}
• Genesis components: {count and names}
• Custom-Built components: {count and names}
• Product components: {count and names}
• Commodity components: {count and names}
• Components with inertia: {list}
• Key dependencies and critical path: {summary}

Existing Build/Buy Decisions:

• Components being built in-house: {list}
• Components being bought/licensed: {list}
• Decisions still undecided: {list}

Step 4: Situational Assessment

Before evaluating plays, establish the situational context that determines which plays are viable.

Position Analysis

Where are your components on the map relative to the competitive landscape?

• Genesis concentration: Are you leading with novel capabilities competitors haven't mapped yet?
• Custom-Built differentiation: Where do you have bespoke competitive advantage?
• Product parity: Where are you competing on features with established vendors?
• Commodity laggard: Where are you running custom infrastructure that the market has commoditised?

Identify the dominant position type (Genesis leader / Custom-Built strength / Product parity / Commodity laggard) as this drives the Play-Position Matrix selection in Step 5.

Capability Assessment

What can the organisation actually execute?

• Resources: Investment capacity for directed plays (Directed Investment, Land Grab, Threat Acquisition)
• Risk tolerance: Can the organisation absorb failure from Experimentation, Fool's Mate, or Ambush plays?
• Ecosystem relationships: Are partnerships, alliances, or community ties available to support Ecosystem plays?
• Time horizon: Urgency drives towards faster plays (Fool's Mate, Land Grab); longer horizons allow Experimentation and Education
• Doctrine maturity (from WDOC if available): Weak doctrine limits execution of complex multi-play strategies

Market Context

What is the market doing?

• Growing or consolidating?: Growing markets favour Land Grab and Directed Investment; consolidating markets favour Harvesting and Last Man Standing
• Regulatory pressures: Presence of government/regulatory factors enables Industrial Policy; constraints on Lobbying plays
• Customer pain points: Unmet needs favour Education, Market Enablement, and Creating Artificial Needs
• Substitutes emerging?: Threat of substitution suggests Raising Barriers to Entry, Tower and Moat, or proactive Open Approaches

Peace/War/Wonder Phase

If WCLM is available, extract the phase assessment. If not, infer from map:

• Peace: Feature competition dominates → favour Differentiation, Standards Game, Sensing Engines
• War: Industrialisation underway → favour Open Approaches, Ecosystem, Centre of Gravity, Managing Inertia
• Wonder: New higher-order systems emerging → favour Experimentation, Weak Signal/Horizon, Co-creation

Step 5: Evaluate Play Options by Category

Evaluate each of the 11 categories systematically. For each category, list plays that are applicable given your map position and situational assessment.

Use the Play-Position Matrix from gameplay-patterns.md section 3 to match your dominant position to appropriate plays. Then assess each play within the applicable categories.

For each applicable play, provide:

Play: [Play Name] ([D&D Alignment])
Category: [Category Letter and Name]
Applicable because: [1-2 sentences referencing specific components/positions from the map]
Evolution stage match: [Does this play match the component's evolution stage?]
Recommendation: Apply / Monitor / Skip
Rationale: [Why apply/monitor/skip — specific to this map and context]

Category A: User Perception

Evaluate: Education, Bundling, Creating Artificial Needs, Confusion of Choice, Brand and Marketing, FUD, Artificial Competition, Lobbying/Counterplay

Which plays are relevant given your user-facing components and their evolution stage?

Category B: Accelerators

Evaluate: Market Enablement, Open Approaches, Exploiting Network Effects, Co-operation, Industrial Policy

Which plays would accelerate evolution of Custom-Built components you want to commoditise, or grow a market you want to lead?

Category C: De-accelerators

Evaluate: Exploiting Constraint, Intellectual Property Rights/IPR, Creating Constraints

Which plays could slow commoditisation of components you want to protect? Note CE plays with explicit warning.

Category D: Dealing with Toxicity

Evaluate: Pig in a Poke, Disposal of Liability, Sweat and Dump, Refactoring

Which components are toxic (technical debt, poor fit, declining value) and what is the appropriate disposal strategy?

Category E: Market

Evaluate: Differentiation, Pricing Policy, Buyer/Supplier Power, Harvesting, Standards Game, Last Man Standing, Signal Distortion, Trading

What market-positioning plays are available given your evolution stage and competitive position?

Category F: Defensive

Evaluate: Threat Acquisition, Raising Barriers to Entry, Procrastination, Defensive Regulation, Limitation of Competition, Managing Inertia

What threats need defending against, and which defensive plays are appropriate?

Category G: Attacking

Evaluate: Directed Investment, Experimentation, Centre of Gravity, Undermining Barriers to Entry, Fool's Mate, Press Release Process, Playing Both Sides

What offensive plays are executable given your resources, risk tolerance, and time horizon?

Category H: Ecosystem

Evaluate: Alliances, Co-creation, Sensing Engines/ILC, Tower and Moat, N-sided Markets, Co-opting and Intercession, Embrace and Extend, Channel Conflicts and Disintermediation

What ecosystem plays are available — do you have the components and relationships to build or join an ecosystem?

Category I: Competitor

Evaluate: Ambush, Fragmentation Play, Reinforcing Competitor Inertia, Sapping, Misdirection, Restriction of Movement, Talent Raid, Circling and Probing

What competitor-directed plays are available? Flag CE plays with explicit ethical caution.

Category J: Positional

Evaluate: Land Grab, First Mover/Fast Follower, Aggregation, Weak Signal/Horizon

What positional plays would secure or improve your strategic position on the map?

Category K: Poison

Evaluate: Licensing Play, Insertion, Designed to Fail

Recognise these when they are used against you. Flag whether any are currently affecting your value chain as defensive awareness.

Step 6: Check Play Compatibility

From the plays recommended as "Apply" in Step 5, check compatibility using the tables in gameplay-patterns.md section 4.

Reinforcing Combinations

List recommended plays that work well together, referencing the compatibility table:

Primary Play + Compatible Play → Why they reinforce each other
Example: Open Approaches + Co-creation → Openness attracts community that co-creates the ecosystem

Identify 2-3 high-value combinations that form a coherent strategic thrust.

Conflicting Plays

Flag any selected plays that conflict with each other:

Play A conflicts with Play B → Why (referencing the conflicts table)
Resolution: Which to prioritise, or how to resolve the conflict

Do not recommend play combinations that undermine each other — force an explicit resolution.

Overall Play Coherence

Assess the selected play portfolio:

• Are the plays strategically coherent? Do they tell a consistent story?
• Is there an appropriate mix of offensive and defensive plays?
• Is the alignment profile acceptable? (All LG/N? Mix includes LE? Any CE flagged for recognition only?)

Step 7: Detail Selected Plays

For each play recommended as "Apply" in Step 5, provide a detailed execution plan. Limit to the top 5-8 plays to keep the document actionable.

For each detailed play:

[Play Name] ([D&D Alignment]) — Category [Letter]

Description: [One sentence from the gameplay catalog, tailored to this specific context]

Why it applies here: [Specific reference to components, evolution positions, and situational factors that make this play appropriate]

Prerequisites: What must be true before executing this play?

• [Prerequisite 1: specific to this map context]
• [Prerequisite 2]
• [Prerequisite 3 if needed]

Execution Steps:

1. [Specific, actionable first step — who does what]
2. [Second step]
3. [Third step]
4. [Continuing steps as needed]

Expected Outcomes:

• Short-term (0-3 months): [Tangible, observable result]
• Long-term (6-18 months): [Strategic position achieved]

Risks and Mitigations:

Success Criteria (measurable):

• [Criterion 1 — observable, specific]
• [Criterion 2]
• [Criterion 3]

Review Points: When should progress on this play be reassessed?

• [Trigger or date] — check [what specifically]

Step 8: Anti-Pattern Check

Before finalising the strategy, verify it avoids the six strategic anti-patterns from gameplay-patterns.md section 5.

For each anti-pattern, explicitly confirm or flag:

Playing in the wrong evolution stage: Are any recommended plays applied to components at the wrong evolution stage? (e.g., Experimentation on a commodity component, Harvesting on a Genesis component) → Status: [No violations identified / Flagged: {details}]

Ignoring inertia: Have inertia points from the WARD artifact been addressed in the execution plans? Is there a play (e.g., Managing Inertia) to handle organisational resistance? → Status: [Addressed via [play name] / Warning: inertia points {list} have no mitigation]

Single-play dependence: Is the strategy dangerously dependent on one play succeeding? Is there a layered play portfolio? → Status: [Portfolio of {count} plays provides redundancy / Warning: single play {name} is the only defence/offence]

Misreading evolution pace: Has the evolution velocity of key components been validated (against WCLM if available)? → Status: [Evolution positions verified / Warning: {components} may be mis-positioned]

Ecosystem hubris: If ecosystem plays (Tower and Moat, N-sided Markets, Sensing Engines) are selected, is there a plan to continue generating genuine ecosystem value? → Status: [ILC/Weak Signal plays included to maintain ecosystem health / Warning: ecosystem play selected without monitoring mechanism]

Open washing: If Open Approaches is selected alongside Licensing Play, Standards Game, or Embrace and Extend — is this coherent? → Status: [Coherent — no contradiction identified / Warning: Open Approaches and {play} may signal open washing to the community]

Step 9: Case Study Cross-References

Which real-world examples from gameplay-patterns.md section 6 most closely parallel the recommended strategy? For each relevant case study, provide a 1-2 sentence connection to the selected plays.

Limit to the 3-5 most relevant case studies. Avoid forcing connections where the parallel is weak.

Step 10: Generate Output

Create the gameplay analysis document using the template:

File Location: projects/{project_number}-{project_name}/wardley-maps/ARC-{PROJECT_ID}-WGAM-{NNN}-v1.0.md

Naming Convention:

• ARC-001-WGAM-001-v1.0.md — First gameplay analysis for project 001
• ARC-001-WGAM-002-v1.0.md — Second gameplay analysis (e.g., for a revised map)

Read the template (with user override support):

• First, check if .arckit/templates/wardley-gameplay-template.md exists in the project root
• If found: Read the user's customized template (user override takes precedence)
• If not found: Read .arckit/templates/wardley-gameplay-template.md (default)

Tip: Users can customise templates with $arckit-customize wardley.gameplay

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}-WGAM-{NNN}-v{VERSION} (e.g., ARC-001-WGAM-001-v1.0)
• Sequence number {NNN}: Check existing files in wardley-maps/ and use the next WGAM number (001, 002, ...)

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] → "Wardley Gameplay Analysis"
• ARC-[PROJECT_ID]-WGAM-{NNN}-v[VERSION] → Construct using format above
• [COMMAND] → "arckit.wardley.gameplay"

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-wardley.gameplay` command | [PENDING] | [PENDING] |

Populate Generation Metadata Footer:

**Generated by**: ArcKit `$arckit-wardley.gameplay` 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 — WARD, WCLM, WDOC, etc.]

Output Contents

The Wardley Gameplay Analysis document must include:

1. Executive Summary: Strategic context, map summary, recommended play portfolio overview (2-3 paragraphs)

2. Map Context: Component inventory table, dominant position type, situational assessment summary

3. Play Evaluation by Category: All 11 categories assessed with Apply/Monitor/Skip for each applicable play

4. Play Compatibility Matrix: Reinforcing combinations and flagged conflicts

5. Detailed Play Execution Plans: Top 5-8 plays with prerequisites, execution steps, outcomes, risks, success criteria

6. Anti-Pattern Check: Explicit pass/fail for all 6 anti-patterns

7. Case Study Cross-References: 3-5 relevant real-world parallels

8. Recommended Play Portfolio: Summary table of all recommended plays with alignment, category, priority, and time horizon

9. Traceability: Link to WARD artifact, WCLM (if used), WDOC (if used), RSCH (if used)

Step 11: Integration with ArcKit Workflow

Wardley Mapping Suite

This command is part of the Wardley Mapping suite:

# Foundation: always run first
$arckit-wardley — Create Wardley Map (required WARD artifact)

# Analysis layer: run after map creation
$arckit-wardley.climate — Assess climatic patterns (WCLM artifact)
$arckit-wardley.gameplay — Identify strategic plays (WGAM artifact) ← you are here

# Execution layer: run after analysis
$arckit-roadmap — Create roadmap to execute selected plays
$arckit-strategy — Synthesise into architecture strategy document

Before Gameplay Analysis

If WARD artifact does not exist:

"A Wardley Map is required. Run `$arckit-wardley` first to create your map, then return here."

If WCLM is missing but gameplay is proceeding:

"Note: No climate assessment (WCLM) found. Consider running `$arckit-wardley.climate` after this analysis —
climate patterns may affect which plays are timely and which are premature."

After Gameplay Analysis

Recommend next steps based on selected plays:

# If Directed Investment or Land Grab selected
"Your selected plays include resource-intensive options. Consider running `$arckit-roadmap` to create a
phased execution plan with investment milestones."

# If ecosystem plays selected (Tower and Moat, N-sided Markets, etc.)
"Your strategy includes ecosystem plays. Consider running `$arckit-strategy` to synthesise these into
a coherent architecture strategy document."

# If Open Approaches selected
"The Open Approaches play may involve open-sourcing or publishing components. Consider running
`$arckit-sow` if procurement is needed for the ecosystem, or `$arckit-research` to identify
existing open communities to join."

# If UK Government project
"As a UK Government project, ecosystem and market plays should be validated against TCoP Point 3
(Open Source), Point 8 (Share/Reuse), and G-Cloud procurement constraints. Run `$arckit-tcop`."

Important Notes

Gameplay Selection Quality Standards

Good Gameplay Analysis:

• Plays matched to actual component evolution stages (not generic advice)
• Play-Position Matrix used explicitly
• Compatibility conflicts identified and resolved
• Anti-patterns explicitly checked and cleared
• Execution plans are specific and actionable (not generic)
• Alignment profile considered against organisational values
• Case study references are genuinely analogous

Poor Gameplay Analysis:

• Recommending all plays without prioritisation
• Ignoring evolution stage when selecting plays
• Mixing conflicting plays without resolution
• Recommending CE plays without ethical flagging
• Generic execution steps not tied to specific components
• No anti-pattern check

Alignment Ethics

When recommending plays with LE or CE alignment:

• LE plays: Flag explicitly with "(Lawful Evil — self-interested but within accepted norms)" and note reputational or regulatory risks
• CE plays: Include explicit warning — "This play is classified CE (Chaotic Evil). It is presented for recognition purposes only. Deploying this play deliberately would damage stakeholder trust and may create legal exposure."
• CE plays should never appear in "Apply" recommendations — only in "Recognise and Defend Against" lists

Play Sequencing

Some plays must be sequenced carefully:

• Education before Open Approaches: Market must understand the value before openness can grow it
• Weak Signal/Horizon before Land Grab: Identify the opportunity before committing resources to capture it
• Managing Inertia before Ecosystem plays: Internal resistance must be addressed before ecosystem commitments can be honoured
• Experimentation before Directed Investment: Validate the opportunity before scaling it

• Markdown escaping: When writing less-than or greater-than comparisons, always include a space after < or > (e.g., < 3 seconds, > 99.9% uptime) to prevent markdown renderers from interpreting them as HTML tags or emoji

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

Final Output

Generate a comprehensive Wardley Gameplay Analysis document saved to:

projects/{project_number}-{project_name}/wardley-maps/ARC-{PROJECT_ID}-WGAM-{NUM}-v{VERSION}.md

The document must be:

• Complete with all sections from template
• Specific (plays matched to actual map components, not generic advice)
• Executable (each recommended play has actionable steps)
• Ethically annotated (alignment flags for LE/CE plays)
• Compatible (conflicting plays resolved, reinforcing combinations identified)
• Anti-pattern checked (all 6 anti-patterns explicitly cleared)

After creating the document, provide a summary to the user:

Wardley Gameplay Analysis Complete: {document_name}

Location: projects/{project}/wardley-maps/ARC-{PROJECT_ID}-WGAM-{NUM}-v{VERSION}.md

Plays Evaluated: {total_plays_considered} across 11 categories
Recommended (Apply): {count} plays
Monitor: {count} plays
Skip: {count} plays

Top 3 Recommended Plays:
1. {Play Name} ({Alignment}) — {one-line rationale}
2. {Play Name} ({Alignment}) — {one-line rationale}
3. {Play Name} ({Alignment}) — {one-line rationale}

Key Reinforcing Combination: {Play A} + {Play B} → {why}

Key Risks:
- {Risk 1}
- {Risk 2}

Anti-Pattern Check: {count}/6 passed — {any warnings}

Next Steps:
- $arckit-wardley.climate — Validate plays against climatic forces (if not done)
- $arckit-roadmap — Create execution roadmap for selected plays
- $arckit-strategy — Synthesise gameplay into architecture strategy

Remember: Gameplay analysis is only as good as the map it is based on. If the map components are mispositioned, the play selection will be wrong. Always validate component evolution positions before committing to a play strategy.

Suggested Next Steps

After completing this command, consider running:

• $arckit-roadmap -- Create roadmap to execute selected plays
• $arckit-strategy -- Synthesise gameplay into architecture strategy
• $arckit-wardley.climate -- Validate plays against climatic patterns (when Climate assessment not yet performed)