Skip to content

Alescent Effect References

02.030.130.000 v20260803.001

Change Log

Purpose and Boundary

This document family provides Alescent-specific reference guidance for applying canonical VRBoK Effects.

It may define:

  • Alescent Reference Tiers;
  • Primary and Secondary Effect Classes;
  • typical Personas and accountabilities;
  • typical Value Realization Domain relationships;
  • Reference Effort Sets and illustrative Efforts;
  • Alescent Plays, Playbooks, Practices, Offerings, Products, Platforms, Proof, and Performance Measures;
  • downstream knowledge workspace mirror and synchronization guidance;
  • scenario and engagement guidance.

It must not redefine portable Effect identity, canonical definition, Optimized Condition, designation roles, evidence principles, or valuation boundaries.

Governing VRBoK Sources

The applied references depend on:

  • 01.020.010.010, Effects;
  • 01.020.010.020, Value Realization Effects;
  • 01.020.010.020.010, Effect Reference Model;
  • 01.020.010.020.020, Effect Registry and Lifecycle;
  • the applicable individual Effect definition, beginning with 01.020.010.020.100, Cost Optimization.

Where an ABoK reference conflicts with the VRBoK, the ABoK reference must be corrected unless a canonical VRBoK change is adopted through governance.

Reference Architecture

Layer Content
Canonical Effect Portable identity, definition, Optimized Condition, semantic boundary, evidence, and valuation doctrine.
Alescent Effect Reference Non-binding Alescent tier, classes, Domains, Effort Sets, Plays, Playbooks, Personas, and applied guidance.
Effect Application Customer-, Engagement-, Offering-, Initiative-, Product-, Platform-, Project-, or scenario-specific designation and value case.

Current Contents

Reference Posture

Alescent references are governed defaults and working preferences. They are not universal requirements.

An Alescent Reference Tier, class assignment, Effort Set, Playbook, Persona relationship, or scenario recommendation may be overridden or adapted where:

  • the customer provides explicit direction;
  • the governing Engagement or Initiative establishes a different Priority;
  • evidence indicates a different materiality, timing, risk, or value pathway;
  • legal, regulatory, commercial, Partner, or operating constraints require another treatment;
  • the reference is not fit-for-value for the declared context.

The deviation should be recorded where material. It does not alter the canonical Effect or the general Alescent reference.

Applied Effect Reference Structure

Each material Alescent Effect Reference should identify:

  1. canonical Effect ID and VRBoK source;
  2. Alescent Reference Tier;
  3. Primary Effect Class;
  4. Secondary Effect Classes;
  5. typical Domain relationships;
  6. common Personas and accountabilities;
  7. Reference Effort Sets;
  8. illustrative Efforts;
  9. relevant Plays and Playbooks;
  10. relevant Practices and Progression Patterns;
  11. applicable Offerings, Products, Platforms, Proof, and Performance Measures;
  12. common scenarios and exclusions;
  13. downstream knowledge workspace object ID and synchronization status;
  14. evidence, valuation, trade-off, and anti-pattern reminders;
  15. reference limitations and override guidance.

Candidate and Canonical Boundary

The downstream knowledge workspace Effect object type is a discovery and working environment containing both governed mirrors and exploratory candidate Effects.

An Alescent Effect Reference should not be created merely because an object exists in downstream knowledge workspace. The underlying Effect must be canonical in the VRBoK or explicitly identified as a candidate under review.

Governance

GitHub remains the source of truth for governed ABoK Effect References.

downstream knowledge workspace may mirror canonical and applied fields, retain working notes, and support relationships. Material changes proposed in downstream knowledge workspace should be reviewed through a CRB, issue, or pull request before they alter governed repository doctrine.