Skip to content

Alescent Progression Pattern Registry

02.030.020.080 v20260803.001

Change Log

Purpose and Boundary

This registry governs Alescent-specific Progression Patterns used to assess, design, execute, evidence, and sustain Capability and Competency maturity advancement.

The registry applies, specializes, and operationalizes the portable VRBoK Maturity Progression architecture. It does not redefine the Maturity Model, controlled anchor states, adjacent Progressions, Reference Progressions, evidence principles, or fit-for-value rules.

Relationship to the VRBoK

Portable doctrine is maintained in:

Alescent Progression Patterns may cite or specialize portable Patterns. Where a Pattern becomes sufficiently generalized and portable, it may be proposed for VRBoK adoption through canonical governance.

Registry Rules

  • Relationships are many-to-many.
  • A Pattern may apply to several Capabilities, Competencies, Domains, Effects, and Maturity Progressions.
  • A Pattern may have different roles in different contexts.
  • A Progression Application must identify the source Maturity Position, adjacent target Maturity Level, scope, evidence basis, and fit-for-value rationale.
  • Pattern use does not prove maturity advancement or realized value.
  • Alescent Products, Platforms, Offerings, assessment instruments, and Playbooks may support a Pattern but are not portable requirements.

Initial Candidate Registry

These entries are proposed seeds for development. They are not yet complete Pattern documents.

Candidate Pattern Typical Progression relationships Illustrative Domains Illustrative Effects
Minimum Viable Operating Context Improvising, primary Players, Practices, Projects, Platforms Capability Optimization, Competency Optimization, Confidence Optimization, Control Optimization
Operating Evidence Capture Improvising and Normalizing, evidence-producing Players, Practices, Products, Projects Confidence Optimization, Control Optimization, Capability Optimization
Standard Practice Establishment Normalizing, primary Practices, Players, Platforms Capability Optimization, Continuity Optimization, Control Optimization, Compliance Optimization
Required Proficiency Definition Normalizing, primary; Improvising, conditional Players, Practices Competency Optimization, Capability Optimization, Capacity Optimization
Exception Governance Normalizing and Rationalizing, primary or contributing Practices, Players, Projects Control Optimization, Compliance Optimization, Continuity Optimization, Complexity Optimization
Authoritative Source Establishment Rationalizing, primary; Normalizing and Optimizing, contributing Platforms, Practices, Products, Players Control Optimization, Confidence Optimization, Complexity Optimization, Cost Optimization
Variant Inventory and Disposition Rationalizing, primary Practices, Platforms, Products, Partners Complexity Optimization, Cost Optimization, Continuity Optimization, Capability Optimization
Stable-Work Automation Optimizing, primary Practices, Platforms, Players, Products Cost Optimization, Capacity Optimization, Consumption Optimization, Capability Optimization
Governed Feedback Loop Optimizing, primary Practices, Platforms, Products, Players Capability Optimization, Confidence Optimization, Contribution Optimization, Control Optimization
Cross-Boundary Dependency Mapping Harmonizing, primary; Rationalizing, contributing All six Domains Continuity Optimization, Complexity Optimization, Capability Optimization, Control Optimization
Semantic Reconciliation Rationalizing and Harmonizing, primary or contributing Platforms, Practices, Partners, Products Confidence Optimization, Control Optimization, Complexity Optimization, Compliance Optimization
End-to-End Effect Measurement Harmonizing, primary; Optimizing, contributing All six Domains Contribution Optimization, Capability Optimization, Confidence Optimization, Cost Optimization
State-of-the-Art Recalibration Optimizing and Harmonizing, conditional All six Domains Capability Optimization, Competition Optimization, Confidence Optimization, Continuity Optimization

Pattern Record

progression_pattern:
  id: ""
  name: ""
  version: ""
  lifecycle_status: "proposed"
  authority_status: "reference"
  pattern_class:
    - "Progression Pattern"
  definition: ""

  portable_sources: []

  applicable_progressions:
    - progression: "Improvising | Normalizing | Rationalizing | Optimizing | Harmonizing"
      role: "primary | contributing | conditional | evidence-producing | excluded"
      rationale: ""

  applicable_subjects:
    capabilities: []
    competencies: []
    practices: []
    platforms: []
    products: []
    qualified_other: []

  domain_relationships:
    primary: []
    contributing: []
    affected: []
    evidence_producing: []
    excluded: []

  effects:
    priorities: []
    contributors: []
    protected: []
    adverse_or_tradeoff: []

  plays: []
  playbooks: []
  other_efforts: []
  required_practices: []
  required_proficiencies: []
  enabling_platforms: []
  enabling_products: []
  partner_conditions: []
  project_or_initiative_relationships: []
  evidence_indicators: []
  exit_criteria_supported: []
  alescent_products: []
  alescent_platforms: []
  offerings: []
  proof_artifacts: []
  performance_measures: []
  limitations: []
  sources_and_validation: []

Application Record

A customer-, engagement-, account-, Product-, Platform-, or Practice-specific use should be recorded as a Progression Application, not as a new Pattern unless it contains reusable logic.

A Progression Application should identify:

  • Maturity Subject and scope;
  • source Maturity Level and Position;
  • adjacent target Maturity Level;
  • selected Progression Patterns;
  • Plays, Playbooks, Projects, and other Efforts;
  • Priority Effects and trade-offs;
  • Domain relationships;
  • Investments, accountabilities, evidence, and exit criteria;
  • confidence, limitations, and regression triggers.

Governance

New Alescent Progression Patterns should be reviewed for reuse, evidence, supportability, ownership, Practice Area relationships, commercialization readiness, and portability potential.

The registry should be maintained as repository-governed structured data when the number of Pattern records makes Markdown insufficient. GitHub remains the source of truth for governed ABoK records unless another system is explicitly designated.