SRM JSON Schema

This page documents the composite JSON Schema for the Strategic Response Model (SRM). The composite groups the model's four component records — triggers, rationales, strategic intents and strategic responses — so that a complete set can be exchanged and validated as one document. Each component is defined in its own schema.

Schema: strategic-response-model.schema.json
Specification: JSON Schema Draft-07

Component	Schema	Documentation
Trigger	trigger.schema.json	Trigger Schema
Rationale	rationale.schema.json	Rationale Schema
Strategic Intent	strategic-intent.schema.json	Strategic Intent below
Strategic Response	strategic-response.schema.json	Strategic Response below

Performance indicators are not part of the composite: they are separate records (performance-indicator.schema.json, see Performance Indicators) that intents and responses reference by ID.

Schema Overview

The four components link to each other by identifier rather than by nesting:

Composite Attributes

Attribute	Type	Required	Description
triggers	Array[Object]		Triggers that prompt a response; each item is a Trigger record
rationales	Array[Object]		Rationales justifying responses; each item is a Rationale record
strategicIntents	Array[Object]		Proactive strategic intents; each item is a Strategic Intent record
strategicResponses	Array[Object]		Strategic responses; each item is a Strategic Response record

None of the lists is required, and the composite rejects any other property.

Complete Schema

This is the composite schema as published in the repository:

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "$id": "https://triodian.com/schemas/strategic-response-model.schema.json",
  "title": "Strategic Response Model Schema",
  "description": "Composite of the Strategic Response Model: triggers (what prompts change), rationales (why respond), strategic intents (proactive aspirations) and strategic responses (what is done). Each is defined in its own schema; this composite groups them for exchange.",
  "type": "object",
  "properties": {
    "triggers": {
      "type": "array",
      "description": "Triggers that prompt a response",
      "items": {
        "$ref": "trigger.schema.json"
      }
    },
    "rationales": {
      "type": "array",
      "description": "Rationales justifying responses",
      "items": {
        "$ref": "rationale.schema.json"
      }
    },
    "strategicIntents": {
      "type": "array",
      "description": "Proactive strategic intents",
      "items": {
        "$ref": "strategic-intent.schema.json"
      }
    },
    "strategicResponses": {
      "type": "array",
      "description": "Strategic responses",
      "items": {
        "$ref": "strategic-response.schema.json"
      }
    }
  },
  "additionalProperties": false
}

Strategic Intent

A strategic intent is a proactive strategic aspiration or opportunity the organization intends to pursue, realised through strategic responses.

Attribute	Type	Required	Description
intentID	String	✓	Unique identifier for the strategic intent
title	String	✓	Concise name describing the strategic intent
description	String	✓	Detailed explanation of the intent's purpose and scope
strategicObjectiveReference	String	✓	Direct link to the relevant strategic objective
opportunityType	Enum	✓	Classification of opportunity type
targetTimeframe	String		Expected time horizon for realization
maturityLevel	Enum		Assessment of organizational readiness
potentialValue	Enum		Estimated business value or impact
uncertaintyLevel	Enum		Assessment of associated risks and unknowns
responseReferences	Array[String]		Strategic responses initiated by this intent
responsibleStakeholders	Array[String]		Key organizational units or roles championing the intent
businessCapabilitiesImpacted	Array[String]		Capabilities expected to be affected
rationaleReferences	Array[String]		List of rationale IDs providing justification for this intent
performanceIndicatorReferences	Array[String]		Metrics or KPIs that will be used to measure the success of the strategic intent
status	Enum		The current status of the strategic intent: proposed, planned, approved, inProgress, onHold, deferred, completed, cancelled, or transformed (reshaped into a different intent) and superseded (replaced by another intent)
lastUpdated	Date		The date when the strategic intent record was last updated

Opportunity Type (opportunityType)

Value	Description
innovation	New products, services or ways of working
growth	Revenue, market or customer growth
efficiency	Lower cost or higher productivity
resilience	Ability to withstand and recover from disruption
compliance	Getting ahead of regulatory or policy obligations
differentiation	Distinctive competitive position
sustainability	Environmental, social or governance outcomes
transformation	Fundamental change to the operating or business model

Maturity Level (maturityLevel)

Value	Description
conceptual	Idea stage; not yet explored
emerging	Early exploration and experiments under way
established	Intent agreed and supported by working practices
scaling	Being extended across the organization
optimizing	Mature and being continuously refined

Potential Value (potentialValue)

Value	Description
low	Limited value
medium	Moderate value
high	Significant value
critical	Value essential to the organization's future
transformative	Value that would change the organization's business model

Uncertainty Level (uncertaintyLevel)

Value	Description
low	Well understood, few unknowns
medium	Some unknowns
high	Many unknowns
critical	Unknowns that threaten the intent's viability
experimental	Outcome unknown until tested

Strategic Response

A strategic response records what the organization does: the aligned change across business architecture domains, initiated by triggers or intents and justified by rationales.

Core Attributes

Attribute	Type	Required	Description
responseID	String	✓	A unique identifier for the strategic response
responseTitle	String	✓	A short title summarising the response
responseType	Enum	✓	The classification of the response, e.g. policyChange, capabilityDevelopment, initiativeLaunch, complianceProgram, digitalTransformation (75 values; see the schema)
responseDescription	String	✓	Detailed description of the strategic response, its objectives, and scope
affectedDomains	Array[Enum]	✓	Business architecture domains impacted by this response (shared domain list)
status	Enum	✓	The current status of the strategic response (shared work status: proposed, planned, approved, inProgress, onHold, deferred, completed, cancelled)
triggerReferences	Array[String]		List of triggerIDs that initiated this strategic response
intentReferences	Array[String]		List of strategic intentIDs that initiated this response
rationaleReferences	Array[String]		List of rationaleIDs providing justification for this response
performanceIndicatorReferences	Array[String]		Metrics or KPIs that will be used to measure the success of the strategic response
impactedUnits	Array[Object]		Organization units impacted by this response and their roles
implementationPlan	String		Reference or description of the plan outlining how the response will be executed
expectedOutcomes	String		Anticipated results or benefits from implementing the response
responsibleOrgUnits	Array[String]		Organization units accountable for executing the strategic response
startDate	Date		The planned start date for implementing the strategic response
endDate	Date		The planned completion date for the strategic response
lastUpdated	Date		The date when the strategic response record was last updated

Strategic Alignment Attributes

Attribute	Type	Required	Description
strategicThemes	Array[String]		Organizational strategic priorities this response supports
alignmentStrength	Integer		How closely the response aligns with organizational strategy (1-5)
adjacentInitiatives	Array[String]		Related initiatives that complement or support this response
strategicLevers	Array[Enum]		Business mechanisms being utilized to effect change
strategicHorizon	Enum		Categorization of the strategic timeframe (H1: 0-18 months, H2: 18-36 months, H3: 36+ months)

Domain-Specific Attributes

Each domain adds IDs of the records the response addresses and objects describing the change. The structure of each object is defined in strategic-response.schema.json.

Customer

Attribute	Type	Required	Description
customerSegmentIDs	Array[String]		Customer segments this response targets
customerOutcomes	Array[Object]		Specific customer outcomes resulting from this response
customerExperienceChanges	Array[Object]		Specific changes to customer experience
customerFeedbackMechanism	String		How customer feedback will be collected

Market

Attribute	Type	Required	Description
marketIDs	Array[String]		Markets this response addresses
competitorIDs	Array[String]		Competitors this response addresses
competitiveAdvantage	Object		Competitive advantage created or enhanced
marketPositionChanges	Array[Object]		Specific changes to market position
competitiveMonitoring	Object		How competitive reactions will be monitored

Finance

Attribute	Type	Required	Description
financeIDs	Array[String]		Financial elements this response addresses
financialOutcomes	Array[Object]		Specific financial outcomes resulting from this response
financialResources	Object		Resources required for this response
financialRiskAssessment	Array[Object]		Assessment of financial risks
financialReviewMechanism	String		How financial performance will be reviewed

Risk Management

Attribute	Type	Required	Description
riskIDs	Array[String]		Risk elements this response addresses
implementedControls	Array[Object]		Risk controls implemented by this response
riskMonitoring	Array[Object]		Ongoing risk monitoring approaches
residualRiskAssessment	String		Assessment of risk remaining after response

Supply Chain

Attribute	Type	Required	Description
supplyChainIDs	Array[String]		Supply chain elements this response addresses
supplyChainOutcomes	Array[Object]		Specific supply chain outcomes resulting from this response
supplyChainChanges	Array[Object]		Specific changes to supply chain configuration
supplyChainRisks	Array[Object]		Risks related to the supply chain response
stakeholderEngagement	Object		Approach to engaging key stakeholders

Innovation

Attribute	Type	Required	Description
innovationIDs	Array[String]		Innovation elements this response addresses
innovationOutcomes	Array[Object]		Specific innovation outcomes resulting from this response
innovationCapabilityChanges	Array[Object]		Changes to innovation capabilities
experimentationApproach	Object		How concepts will be tested
portfolioImpact	Object		How innovation portfolio is affected

Sustainability

Attribute	Type	Required	Description
sustainabilityIDs	Array[String]		Sustainability elements this response addresses
environmentalOutcomes	Array[Object]		Specific environmental outcomes from this response
socialOutcomes	Array[Object]		Specific social outcomes from this response
stakeholderExpectations	Array[Object]		Stakeholder expectations being addressed
complianceRequirements	Array[Object]		Sustainability compliance requirements addressed
climateScenarioConsiderations	Object		Climate scenarios factored into response

People

Attribute	Type	Required	Description
peopleIDs	Array[String]		People elements this response addresses
workforceChanges	Array[Object]		Specific workforce changes implemented
culturalDevelopment	Object		Cultural development initiatives
talentDevelopmentApproach	Object		Approach to talent development
knowledgeManagementStrategy	Object		Strategy for managing knowledge
competencyFrameworkUpdates	Array[Object]		Updates to competency frameworks

Technology

Attribute	Type	Required	Description
technologyIDs	Array[String]		Technology elements this response addresses
architectureChanges	Array[Object]		Specific architecture changes implemented
technicalDebtImpact	Object		Impact on technical debt
securityEnhancements	Array[Object]		Security improvements implemented
integrationApproaches	Object		Integration approaches implemented
technologyStandardsChanges	Array[Object]		Changes to technology standards

Channel

Attribute	Type	Required	Description
channelIDs	Array[String]		Channels this response addresses
channelOutcomes	Array[Object]		Specific channel outcomes
channelChanges	Array[Object]		Specific changes to channel configuration
partnerEngagement	Object		Approach to engaging channel partners
omniChannelIntegration	Object		Omnichannel integration approach
distributionNetworkOptimization	Object		Distribution network optimization

Impacted Unit (impactedUnits)

Attribute	Type	Required	Description
orgUnitTitle	String	✓	Name of the organization unit
orgUnitID	String		ID of the organization unit named in orgUnitTitle
relationshipRole	Enum	✓	Role the unit plays in relation to this response
relationshipStrength	Integer		Strength of the relationship on a scale from 1 (very weak) to 5 (very strong)

Relationship Role (relationshipRole)

Value	Description
owningUnit	Owns the response and is accountable for its outcome
providingUnit	Provides resources, services or delivery for the response
consumingUnit	Consumes the outputs of the response
utilisingUnit	Uses the capabilities or assets the response changes
custodianUnit	Holds custody of assets or information the response affects
dependentUnit	Depends on the response for its own operations
supportedUnit	Receives support as a result of the response
governingUnit	Oversees or governs the response

Strategic Lever (strategicLevers)

Value	Description
scale	Growing size or volume
scope	Broadening range of products, markets or activities
differentiation	Standing apart from competitors
innovation	Introducing something new
efficiency	Doing more with less
resilience	Withstanding and recovering from disruption
other	Another lever, described in responseDescription

Strategic Horizon (strategicHorizon)

Value	Description
horizon1	0-18 months: defending and extending the core business
horizon2	18-36 months: building emerging businesses
horizon3	36+ months: creating options for future businesses

Complete Example

A composite document holding one record of each component, linked by ID:

{
  "triggers": [
    {
      "triggerID": "TRG-003",
      "label": "Privacy Act Amendment 2024",
      "description": "New privacy legislation requiring enhanced consent management",
      "primaryCategory": "regulatoryCompliance",
      "origin": "External",
      "timeHorizon": "shortTerm",
      "impactLevel": "critical",
      "status": "responded",
      "detectionMethod": "Regulatory publication",
      "detectionDate": "2024-06-15",
      "sourceReference": "https://legislation.gov.au/privacy-act-2024",
      "strategicResponseReferences": [
        "ID-001"
      ],
      "affectedEntities": [
        {
          "domainType": "policy",
          "entityID": "POL-007",
          "title": "Data Retention Policy"
        },
        {
          "domainType": "capability",
          "entityID": "CAP-014",
          "title": "Consent Management"
        }
      ]
    }
  ],
  "rationales": [
    {
      "rationaleID": "RAT-001",
      "rationaleTitle": "Mandatory Compliance with Privacy Legislation",
      "description": "The organization must implement enhanced consent management and data subject rights processing to comply with the Privacy Act Amendment 2024. Non-compliance would result in penalties up to $50M and significant reputational damage.",
      "triggerReference": "TRG-003",
      "linkedDomains": [
        "policy",
        "capability",
        "information",
        "technology",
        "initiative"
      ],
      "rationaleType": "complianceFulfillment",
      "rationaleOrientation": "reactive",
      "alternativesConsidered": [
        {
          "alternativeDescription": "Minimal compliance approach",
          "reasonForRejection": "High risk of regulatory interpretation challenges"
        }
      ],
      "reasoningPattern": "causal",
      "evidenceBase": "externalResearch",
      "businessValueType": "riskReduction",
      "dateCreated": "2024-07-01",
      "author": "Legal Compliance Team",
      "orgUnitTitle": "Legal and Compliance"
    }
  ],
  "strategicIntents": [
    {
      "intentID": "OBJ-001",
      "title": "Trusted Data Steward",
      "description": "Be recognised by customers as the most trustworthy custodian of personal data in the market",
      "strategicObjectiveReference": "OBJ-004",
      "opportunityType": "differentiation",
      "targetTimeframe": "2026",
      "maturityLevel": "emerging",
      "potentialValue": "high",
      "uncertaintyLevel": "medium",
      "responseReferences": [
        "ID-001"
      ],
      "responsibleStakeholders": [
        "Chief Privacy Officer"
      ],
      "businessCapabilitiesImpacted": [
        "Consent Management",
        "Data Governance"
      ],
      "rationaleReferences": [
        "RAT-001"
      ],
      "performanceIndicatorReferences": [
        "PI-001"
      ],
      "status": "approved",
      "lastUpdated": "2024-07-01"
    }
  ],
  "strategicResponses": [
    {
      "responseID": "ID-001",
      "responseTitle": "Privacy Act Compliance Program",
      "responseType": "complianceProgram",
      "responseDescription": "Launch a compliance program that updates data retention and consent policies, enhances the consent management capability and implements a consent management platform",
      "triggerReferences": [
        "TRG-003"
      ],
      "intentReferences": [
        "OBJ-001"
      ],
      "rationaleReferences": [
        "RAT-001"
      ],
      "performanceIndicatorReferences": [
        "PI-001",
        "PI-005"
      ],
      "affectedDomains": [
        "initiative",
        "policy",
        "capability",
        "technology"
      ],
      "impactedUnits": [
        {
          "orgUnitTitle": "Office of the Chief Privacy Officer",
          "orgUnitID": "OU-CPO",
          "relationshipRole": "owningUnit",
          "relationshipStrength": 5
        },
        {
          "orgUnitTitle": "Enterprise Technology",
          "orgUnitID": "OU-TECH",
          "relationshipRole": "providingUnit",
          "relationshipStrength": 4
        },
        {
          "orgUnitTitle": "Legal and Compliance",
          "orgUnitID": "OU-LEGAL",
          "relationshipRole": "governingUnit",
          "relationshipStrength": 3
        }
      ],
      "implementationPlan": "Privacy Compliance Program plan v1.2",
      "expectedOutcomes": "Full compliance with the amended Privacy Act by June 2025",
      "responsibleOrgUnits": [
        "Office of the Chief Privacy Officer"
      ],
      "startDate": "2024-07-01",
      "endDate": "2025-06-30",
      "status": "inProgress",
      "lastUpdated": "2024-12-01",
      "strategicThemes": [
        "Customer trust"
      ],
      "alignmentStrength": 4,
      "strategicLevers": [
        "resilience"
      ],
      "strategicHorizon": "horizon1",
      "riskIDs": [
        "RISK-031"
      ],
      "implementedControls": [
        {
          "controlName": "Consent capture control",
          "controlDescription": "Consent is recorded and checked before personal data is processed",
          "controlType": "preventive"
        }
      ],
      "technologyIDs": [
        "TECH-CMP-001"
      ]
    }
  ]
}

Schema Validation

To validate SRM documents against the composite schema, load the component schemas and common.schema.json alongside it so that its references resolve:

# Using ajv-cli
npm install -g ajv-cli
ajv validate -s strategic-response-model.schema.json \
  -r trigger.schema.json -r rationale.schema.json \
  -r strategic-intent.schema.json -r strategic-response.schema.json \
  -r common.schema.json -d my-srm.json

# Using the repository's validator
python scripts/validate.py

Integration Patterns

REST API Pattern

POST /api/v1/strategic-responses
Content-Type: application/json

{
  "responseID": "...",
  "responseTitle": "New Compliance Response",
  "responseType": "complianceProgram",
  "responseDescription": "...",
  "affectedDomains": [ ... ],
  "status": "proposed"
}

Event-Driven Pattern

{
  "eventType": "strategic-response.created",
  "eventTime": "2024-12-18T10:30:00Z",
  "data": {
    "responseID": "ID-001",
    "responseTitle": "Privacy Act Compliance Program",
    "status": "approved"
  }
}

For Data Engineers

The SRM schemas can be registered in your data catalog to enable lineage tracking from business decisions to data changes. Consider creating automated workflows that generate SRM entries when data quality alerts trigger remediation activities.

Related Documentation

• Strategic Response Model Overview — Conceptual documentation
• Trigger Schema — Trigger component details
• Rationale Schema — Rationale component details
• Performance Indicators — KPI details
• Trigger and rationale walkthrough — Worked examples in the composite form