Content Comparison

rationaleID

string (uuid)

Yes

Unique identifier for the rationale

"7a98e34d-f2b4-4ad1-9ac9-ecda9f145d79"

rationaleTitle

string

Yes

Title or summary of the rationale

"Responding to new safety regulation"

description

string

Yes

Detailed explanation supporting a strategic response

"The new regulation requires immediate updates to inspection protocols"

triggerReference

string (uuid)

Yes

Primary trigger this rationale responds to

"uuid-of-trigger"

triggerReferences

array of uuid

No

Optional multiple triggers this rationale addresses

["uuid-1", "uuid-2"]

linkedDomains

array of enum

No

Business architecture domains influenced or justified by this rationale

["Policy", "Performance"]

rationaleType

string (enum)

Yes

The justification type for this rationale

"Compliance_Fulfillment"

rationaleOrientation

string (enum)

Yes

Whether the rationale is responding to existing conditions or anticipating future conditions

"Proactive"

anticipatedOutcomes

array of string

No

For proactive rationales, the expected benefits or outcomes

["Market leadership", "20% cost reduction"]

alternativeConsidered

array of objects

No

Other strategic options that were evaluated but not selected

See example below

reasoningPattern

string (enum)

No

The logical structure of the rationale

"Deductive"

evidenceBase

string (enum)

No

The foundation for the rationale

"External_Research"

strategicObjectiveReference

string (uuid)

No

Reference to the strategic objective this rationale supports

"uuid-of-objective"

businessValueType

string (enum)

No

The nature of value creation or preservation

"Risk_Reduction" or "Market_Creation"

competitivePositioning

object

No

How this rationale advances competitive stance

See example below

dateCreated

string (date)

No

The date the rationale was first recorded

"2025-04-20"

lastReviewed

string (date)

No

The most recent date of rationale review

"2025-06-01"

effectivenessRating

integer (1–5)

No

Optional evaluation of rationale effectiveness

4

author

string

No

The person or team who documented the rationale

"Business Architecture Team"

orgUnitTitle

string

No

The organisational unit that owns or authored the rationale

"Regulatory Compliance Division"

relatedRationales

array of uuid

No

References to other related rationales

["uuid-1", "uuid-2"]

relationshipTypes

array of enum

No

Type of relationship with each related rationale

["supports", "supersedes"]