Alescent Change Register¶

02.900.020 v20261001.001

Record proposed, accepted, rejected, deferred, or superseded changes to the Alescent Body of Knowledge, Alescent Strategic Framework, and Alescent Canon.

Entries¶

Date: 2026-10-01 Change: Standardize Alescent typography on Inter across media. Rationale: Implement the owner-approved single-family decision and remove contradictory presentation and publishing defaults. Impacted artifacts:
- Visual Identity and its change log
- Presentation Standards
- Publishing Profiles and Diagram Style Guide
- Shared PDF and TikZ templates
- MkDocs font settings Decision owner: named participant Status: accepted for implementation; release through repository review
Date: 2026-07-28 Change: Establish the Alescent Body of Knowledge and canonical-authority architecture. Rationale: Adopt ABoK as the umbrella Alescent knowledge system; retain the Alescent Strategic Framework as its principal organizing Framework; retain Alescent Canon as the authoritative subset; retain the Alescent Legal Framework as a distinct operative framework; and distinguish Applied Value Library, Source Material, Perspectives, and derivative assets by explicit authority and lifecycle status. Impacted artifacts:
- README.md
- 02/001.md
- 02/010/000.md
- 02/900/010.md
- 02/900/030.md
- mkdocs.public-alescent-strategic-framework.yml
- downstream knowledge workspace ABoK and Framework Concepts Decision owner: named participant CRB: CRB-037 Status: accepted for implementation
Date: 2026-07-22 Change: Propagate the expanded Value Realization Domains doctrine through the Alescent Applied Value Library and semantic governance. Rationale: Preserve 01.014 as the portable authority while making Domain relationships operational in metadata, Products, Practice Areas, Perspectives, CIO guidance, model instructions, and public navigation. Impacted artifacts:
- 02/030/000.md
- 02/030/040/000.md
- Alescent Strategic Framework/Applied Value Library/Data Model/Library Item Metadata Model.yaml
- Alescent Strategic Framework/Applied Value Library/Perspectives/Model-Specific Perspectives/
- Alescent Strategic Framework/Alescent Canon/Semantic Model/
- 02/900/030.md Decision owner: named participant Status: proposed
Date: 2026-07-22 Change: Add the Azure AI Platform Value Economic Case Offering and its governed execution and communication cross-references. Rationale: Apply the neutral Platform-Enabled Value Conversion Pattern and Comparative Platform Value Efficiency method to a Microsoft-context customer decision while preventing Azure advocacy, unsupported Proof, or a positive multiplier presumption from entering portable doctrine. Impacted artifacts:
- 02/030/010/120/010.md
- 02/030/060/020/010.md
- 02/030/060/020/030.md
- 02/050/040.md
- 02/060/020.md Decision owner: named participant Status: proposed
Date: 2026-07-22 Change: Establish the neutral Platform-Enabled Value Conversion Pattern and Comparative Platform Value Efficiency assessment construct. Rationale: Preserve customer-specific, counterfactual, evidence-based Platform analysis while separating the financial Platform Value Multiplier from the qualitative Platform Value Enablement Score and preventing provider advocacy from becoming general doctrine. Impacted artifacts:
- 02/030/020/070.md
- 02/030/080/010.md
- 02/030/080/030.md
- Applied Value Library indexes and change logs Decision owner: named participant Status: proposed
Date: 2026-06-10 Change: Add Change Value Realization as an Alescent Practice and constrain 5D integration. Rationale: Replace the earlier Change Realization Management framing with Change Value Realization so the applied Practice focuses on realizing the value associated with change. Preserve conventional Change Management and ADKAR as external-compatible lenses. Limit 5D to Canonical Review Backlog treatment as a candidate method for Project-class Engagements only, not a default method for Programs or Portfolios. Impacted artifacts:
- 02/030/030/000.md
- 02/030/030/040.md
- 02/030/020/010.md
- 02/030/080/000.md
- 02/030/080/020.md Decision owner: TBD Status: proposed
Date: 2026-06-09 Change: Add Technical Writer Briefing Source. Rationale: Convert brand and website discovery material into a governed website handoff source for technical writers, website writers, content strategists, designers, developers, agencies, partners, and internal contributors while preserving source hierarchy, controlled terminology, claims boundaries, commercial-alignment guidance, and derivative-output status. Impacted artifacts:
- 02/060/020.md
- 02/060/040.md
- 02/060/050.md Decision owner: TBD Status: proposed
Date: 2026-06-09 Change: Add Website Handoff Governance. Rationale: Define how canonical, applied, brand, and derivative source materials should be packaged and handed off to website writers, designers, developers, agencies, partners, or internal contributors while preventing website copy, visual design, navigation labels, components, or implementation decisions from becoming source doctrine. Impacted artifacts:
- 02/060/010.md
- 02/060/020.md
- 02/060/030.md
- 02/060/040.md Decision owner: TBD Status: proposed
Date: 2026-06-09 Change: Add Engagement Model and Commercial Alignment guidance. Rationale: Define Alescent's engagement model and commercial-alignment posture as operating-model guidance while preserving legal and commercial instrument hierarchy, distinguishing alignment philosophy from commercial mechanics, and preventing overclaims about guaranteed outcomes, unlimited shared risk, universal contingency, or automatic value participation. Impacted artifacts:
- 02/020/010/000.md Decision owner: TBD Status: proposed
Date: 2026-06-09 Change: Add Audience and Market Focus guidance. Rationale: Define Alescent's priority audiences, initial market focus, adjacent contexts, sector priorities, cross-functional stakeholders, market selection criteria, and audience pathway guidance for website, Offering, Practice, Playbook, Proof, and derivative content. Impacted artifacts:
- 02/010/020.md
- 02/050/010.md
- 02/060/010.md Decision owner: TBD Status: proposed
Date: 2026-06-09 Change: Add Innovation Debt Optimization as an Alescent Practice. Rationale: Define Innovation Debt Optimization as a broader Practice for governing residual debt created by innovation, modernization, transformation, Product development, Platform change, operating-model change, sourcing decisions, capability expansion, and strategic experimentation, while preserving Technical Debt as a specific form of Innovation Debt. Impacted artifacts:
- 02/030/030/000.md
- 02/030/030/030.md
- 02/030/060/020/040.md
- 02/030/010/110/000.md Decision owner: TBD Status: proposed
Date: 2026-06-09 Change: Add Value Realization Efficiency as an Alescent performance measure and assessment construct. Rationale: Define Value Realization Efficiency for assessments, Offering Classes, portfolio reviews, and Investment evaluations while preserving Investment-first language, actual and forecasted efficiency views, as-of lifecycle analysis, event-dated Value Realization Schedules, recurrence-generated schedule instances, forecast vintages, and forecast calibration requirements. Impacted artifacts:
- 02/030/080/000.md
- 02/030/080/010.md
- 02/030/010/110/000.md Decision owner: TBD Status: proposed
Date: 2026-06-09 Change: Add Offering Class and Offering Architecture. Rationale: Establish Offering Classes as reusable structures for categories of Offerings, distinguish individual Offerings as context-specific instantiations of Offering Classes, and define versioning and Engagement lineage expectations so executed Engagements can preserve reference to their originating Offering Class, Offering, version, and amendments where practical. Impacted artifacts:
- 02/030/000.md
- Alescent Strategic Framework/Applied Value Library/Offerings/
- 02/060/010.md Decision owner: TBD Status: proposed
Date: 2026-06-09 Change: Expand Applied Value Library and Pattern Library guidance. Rationale: Strengthen the canonical explanation of the Applied Value Library as an Alescent intellectual asset base and the Pattern Library as a curated set of observed and prescribed logic used to identify, interpret, prescribe, govern, and execute Value Realization work. Impacted artifacts:
- 02/030/000.md
- 02/030/020/000.md
- 02/030/900/000.md Decision owner: TBD Status: proposed
Date: 2026-06-09 Change: Add the Straight As as a provisional Alescent narrative model for executive-facing Value Realization communication. Rationale: Provide a speakable narrative arc for helping executives understand how value moves from possible, asserted, or theoretical value toward realized, sustained, and administered value while preserving the formal Value Participation Model for canonical legal, commercial, and valuation use. Impacted artifacts:
- 02/050/010.md
- 02/050/040.md
- 02/050/050.md Decision owner: TBD Status: proposed
Date: 2026-06-09 Change: Strengthen brand and messaging guidance around real value, theoretical value, and qualified commercial alignment. Rationale: Preserve the market-facing distinction between theoretical, asserted, forecasted, or promised value and evidenced, verified, realized, and sustained value. Reserve the potential to develop REAL Value as a future Alescent narrative or brand concept while preventing premature trademark, acronym, or controlled-term treatment. Add commercial claim guidance so website and derivative copy does not imply guaranteed results, universal commercial mechanics, unlimited shared risk, or value participation where not supported by the applicable agreement. Impacted artifacts:
- 02/050/010.md
- 02/050/040.md
- 02/050/050.md Decision owner: TBD Status: proposed
Date: 2026-06-08 Change: Add Chief Information Officer Playbook, IT Investment Management Practice, and derivative-output governance. Rationale: Establish the CIO persona Playbook as an Alescent-specific applied Playbook, define IT Investment Management as a reusable Alescent Practice, and govern future PDF, deck, website, one-page, worksheet, assessment, and related output variants through derivative-asset governance rather than treating them as source doctrine. Impacted artifacts:
- Alescent Strategic Framework/Applied Value Library/Playbooks/Persona Playbooks/
- 02/030/030/010.md
- 02/050/040.md
- 02/060/020.md
- 02/060/030.md
- Alescent Strategic Framework/Website and Derivative Assets/_agent.guidance.yaml Decision owner: TBD Status: proposed
Date: 2026-06-03 Change: Establish Alescent Strategic Framework as the Alescent-specific Canon. Rationale: Separate portable Value Realization Framework doctrine from Alescent-specific strategy, operating models, legal and commercial framework, applied Library, brand, website, and derivative-asset governance. Impacted artifacts:
- README.md
- Alescent Strategic Framework/ Decision owner: TBD Status: accepted
Date: 2026-06-03 Change: Establish Applied Value Library. Rationale: Create a governed operating home for applied Patterns, Practices, Products, Platforms, Playbooks, Proof, and performance measures. Impacted artifacts:
- Alescent Strategic Framework/Applied Value Library/ Decision owner: TBD Status: accepted
Date: 2026-06-03 Change: Use repository-first, schema-governed, database-ready data strategy for the Applied Value Library. Rationale: Library items require structured metadata and active management, but repository-governed YAML should remain the initial source of truth until workflow and relational querying require a database such as Supabase. Impacted artifacts:
- Alescent Strategic Framework/Applied Value Library/Data Model/ Decision owner: TBD Status: accepted
Date: 2026-06-03 Change: Standardize governance directories as 900. Governance. Rationale: Preserve consistent repository architecture across Framework, Alescent, Library, legal and commercial, and operating-model areas. Impacted artifacts:
- README.md
- Alescent Strategic Framework/Governance/
- Alescent Strategic Framework/Applied Value Library/Governance/ Decision owner: TBD Status: accepted
Date: Change: Rationale: Impacted artifacts: Decision owner: Status: proposed | accepted | rejected | deferred | superseded