Tmah issue23

specifications/actions/125.yaml

@@ -1,8 +1,8 @@
 Metadata:
   Proposed: '2025-09-16'
   Adopted: '2025-11-01'
-  Modified: '2026-03-17'
-  Version: 1.7.0
+  Modified: '2026-04-04'
+  Version: 2.0.0
   Status: Accepted
   Approvers:
   - Name: Victoria Levy
@@ -19,17 +19,49 @@ Specification:
   Implementation Types:
   - null
   Weight: 1.0
-  Formula: null
-  Score Type: binary
+  Formula: |-
+    * Weighted sum
+    	TCO (score ×3),
+    	Vendor scoring (score ×3),
+    	Decision document (score ×3),
+    	Rules established (score ×1).
+      Max Raw Score (29)
+    * TCO_Analysis - Total Cost of Ownership analysis performed
+      (0=None, 1=High-level, 2=Detailed, 3=Validated with Finance)
+    * Vendor_Scored - Vendor options scored against criteria
+      (0=None, 1=Informal, 2=Structured scorecard, 3=Multi-stakeholder RFP)
+    * Decision_Doc - Build vs Buy decision formally documented and approved
+      (0=No, 1=Informal note, 2=Formal doc, 3=Exec-approved+reviewed)
+    * Rules_Est - Guiding rules / policy established for future decsions
+      (0=No rules, 1=Draft, 2=Published+Enforced)
+    * Output Range (0 - Max Raw)
+  Score Type: multi_bucket
   Scoring:
   - Score: 0
-    Condition: No rules established
+    Condition: Low Maturity, Score Range (0-8)
+  - Score: 4
+    Condition: Developing, Score Range (9-17)
+  - Score: 7
+    Condition: Established, Score Range (18-24)
   - Score: 10
-    Condition: Published policy
+    Condition: Optimizing, Score Range (25-29)
   References:
-  - Name: null
-    Link: null
+  - Name: Maturity Definition
+    Link: https://www.finops.org/framework/maturity-model/
     Comment: null
   Supplemental Guidance:
-  - null
+  - |-
+    CRAWL (0–8) No build-vs-buy process exists. TCO analysis is absent or undocumented, vendor comparisons are
+    informal, and decisions default to familiarity, relationships, or cost alone.
+  - |
+    WALK (9–17) Basic TCO covers License costs and implementation effort. Vendors are scored against a structured
+    scorecard, and decisions are loosely documented. Finance validation and exec sign-off are inconsistent.
+  - |
+    RUN (18–24) TCO is detailed, covering licensing, implementation, integration, training, support, and build
+    opportunity cost. A multi-stakeholder evaluation process is used, decisions are formally approved, and a guiding
+    policy is published and partially enforced.
+  - |
+    FLY (25–29) TCO is Finance-validated and accounts for multi-year trajectories, exit costs, and strategic
+    optionality. A full RFP with documented rationale is used, decisions are exec-approved and periodically reviewed,
+    and an enforced org-wide policy governs all future build-vs-buy choices.
   Overrides: null

specifications/actions/126.yaml

@@ -1,8 +1,8 @@
 Metadata:
   Proposed: '2025-09-16'
   Adopted: null
-  Modified: '2026-03-17'
-  Version: 0.7.0
+  Modified: '2026-04-04'
+  Version: 0.6.0
   Status: Proposed
   Approvers:
   - Name: null
@@ -15,16 +15,40 @@ Specification:
   Slug: 126-implement-config
   Implementation Types:
   - null
-  Weight: 0.0
-  Formula: null
-  Score Type: calculation
+  Weight: 1.0
+  Formula: |-
+    * Weighted sum
+    	Env coverage (score ×4),
+    	Data Integration (score ×4),
+    	Tag Config (score ×2),
+    	Config Doc (score ×2).
+    	Max raw (52)
+     * Env_Coverage - % of cloud environments covered by deployed tools
+      (0=0%, 1<50%, 2=50-79%, 3=80-94%, 4=95-99%, 5=100%)
+     * Data_Integration - Data sources integrated (billing, usage, tags, business context)
+      (0=None, 1=Billing Only, 2=+Usage, 3=+Tags, 4=+Business context, 5=All+Automated)
+     * Tag_Config - Tag/allocation rules configured and enforced tool
+      (0=No, 1=Partial manual, 2=Full manual, 3=Automated enforcement)
+     * Config_Doc - Tool configuration documented and version-controlled
+      (0=No rules, 1=Informal, 2=Documented, 3=Version-controlled+Reviewed)
+    * Output Range (0-52)
+  Score Type: multi_bucket
   Scoring:
   - Score: 0
-    Condition: null
+    Condition: Low Maturity, Score Range (0-15)
+  - Score: 4
+    Condition: Developing, Score Range (16-31)
+  - Score: 7
+    Condition: Established, Score Range (32-44)
+  - Score: 10
+    Condition: Optimizing, Score Range (45-52)
   References:
   - Name: null
     Link: null
     Comment: null
   Supplemental Guidance:
-  - null
+  - CRAWL Partial environment coverage, billing data only, no tag configuration.
+  - WALK 50–79% coverage, usage and billing data, partial tagging, informal config documentation.
+  - RUN 80–94% coverage, tags integrated, full manual tag rules, documented configuration.
+  - FLY 100% coverage, all data sources automated, automated tag enforcement, version-controlled configuration.
   Overrides: null