| Table of Contents | ||
|---|---|---|
|
...
See https://orthogramic.atlassian.net/wiki/spaces/OM/pages/291242002 for reference cases.
Trigger Taxonomy
Triggers in the Orthogramic Metamodel follow a standardized classification system that enables consistent categorization, improved searchability, and enhanced analytics. Each trigger is classified according to:
Primary Category: The main classification of the trigger (e.g., Regulatory, Technological, Strategic)
Subcategory: A more specific classification within the primary category
Origin: Whether the trigger is internal or external to the organization
Time Horizon: The temporal nature of the trigger (immediate, short-term, long-term)
Impact Level: The potential significance of the trigger (low, medium, high, critical)
This taxonomy provides a framework for organizing triggers consistently, allowing organizations to:
Track patterns in strategic responses across similar trigger types
Analyze the distribution of triggers by source, timeframe, and impact
Identify which categories of triggers most frequently drive strategic changes
Maintain a trigger registry that can be referenced across multiple strategic response models
The standardized taxonomy also supports governance and auditability by ensuring that triggers are documented according to consistent criteria, making it easier to trace decision-making patterns over time.
Trigger JSON Schema
See: https://github.com/Orthogramic/Orthogramic_Metamodel
Schema properties
Field | Type | Required | Description | Example |
|---|
triggerID
rationaleID | string (uuid) | Yes | Unique identifier for the |
rationale |
"RAT- |
triggerTitle
A short title describing the nature of the trigger.
New Regulatory Mandate
triggerType
The classification of the trigger (e.g., External, Internal, Performance-Based).
External
triggerDescription
A detailed explanation of the trigger's context and implications.
Mandate issued by the national regulator requiring compliance.
triggerDate
The date when the trigger was identified or became effective.
2025-04-19
associatedRationaleIDs
STR-005" | ||||
rationaleTitle | string | Yes | Title or summary of the rationale | "Ensure Regulatory Compliance" |
description | string | Yes | A detailed explanation of the rationale supporting a strategic response | "To meet new safety regulations and avoid penalties" |
triggerReference | string (uuid) | Yes | Reference to the trigger that prompted this rationale | "TRG-EXT-2025-01" |
linkedDomains | array of string (enum) | No | List of business architecture domains influenced or justified by this rationale | ["Policy", "Capabilities"] |
primaryDriver | string (enum) | Yes | Primary category for the rationale | "Compliance_Requirement" |
reasoningPattern | string (enum) | No | The logical structure of the rationale | "Normative" |
evidenceBase | string (enum) | No | The foundation for the rationale | "Regulatory_Requirement" |
strategicAlignment | string (enum) | No | How the rationale connects to organizational strategy | "Risk_Mitigation" |
businessValueType | string (enum) | No | The nature of value creation or preservation | "Regulatory_Compliance" |
dateCreated | string (date) | No | The date the rationale was first recorded | "2025-04-20" |
author | string | No | The person or team who documented the rationale | "Regulatory Affairs Team" |
orgUnitTitle | string | No | The organizational unit that owns or authored the rationale | "Regulatory Affairs Unit" |
relatedRationales | array of string (uuid) | No | References to other related rationales | ["RAT-STR- |
006"] |
sourceReference
Reference to the source document or authority of the trigger.
https://regulator.gov/mandate2025
These updated schema properties tables provide a clear overview of the enhanced Trigger and Rationale schemas, including field types, requirement status, descriptions, and example values. The tables reflect the expanded taxonomy features that enable better categorization, analytics, and auditability within the Orthogramic Metamodel.This schema allows organizations to systematically capture and manage triggers that necessitate strategic responses, ensuring traceability and alignment across the enterprise architecture.
...