Capability Development Roadmap - Revision history

Sovereign: /* Phases */ Corrected formatting

2026-07-23T19:05:26Z

Phases: Corrected formatting

@@ Line 90: / Line 90: @@
 == Phases ==
-| Phase | Name | Capability gained | Exit criteria |
+{| class="wikitable"
-|-------|------|-------------------|---------------|
+! Phase
-| '''0''' | '''Foundations''' | Shared language, scope, boundaries | Working terminology available; physical–abstract boundary and “abstract standards are real; the system was missing” citable; discipline vs application explicit |
+! Name
-| '''1''' | '''Scaffold''' | Navigable, metadata-bearing corpus | Core pages carry agreed metadata patterns; static dates and category conventions reusable without reinventing each page |
+! Capability Gained
-| '''2''' | '''Core Architecture Stable''' | Citable core without weekly total rewrite | MoA hub, standing rules, and domain-appropriate boundary stable enough that procedures can point at them |
+! Exit Criteria
-| '''3''' | '''Procedure v0''' | Same structural steps every time | Pre-cal checklist in force; content-cal steps written; nonconformance logged before fix as operating rule |
+|-
-| '''4''' | '''Report v0''' | Outputs behave as instruments | Report and Cal Note templates exist; standing on the report; at least three sample reports, including at least one on a claim '''outside''' pure framework self-description |
+| '''0'''
-| '''5''' | '''Recommendation v0''' | Conditional guidance | Reports carry If-objective-X / evidence-suggests-Y form; unbound prescription is not the default |
+| '''Foundations'''
-| '''6''' | '''Pilot Loop''' | System corrected by external contact | At least three logged cals that changed a procedure, glossary, or standard via correction memory; '''at least one Tier-A or clear outcome-contact pilot''' — not only framework-on-framework checks |
+| Shared language, scope, and boundaries
-| '''7''' | '''Operational''' | Default path is procedure → report → recommendation | That loop is normal work, not a special event |
+| Working Terminology available; physical–abstract boundary and ''Abstract Standards Are Real; the System Was Missing'' citable; Discipline vs. Application explicitly defined.
-| '''8''' | '''Continuous Improvement''' | Permanent Beta as operations | Version bumps, new applications, and pilots are routine; no terminal “finished discipline” fantasy |
+|-
 === Spiral, not only ladder ===
-The '''discipline''' may sit at Operational / Continuous Improvement while a '''new application''' re-enters Foundations through Pilot Loop. Mature method, immature deployment — normal engineering pattern.
+The '''discipline''' may operate at '''Operational''' or '''Continuous Improvement''' while a '''new application''' begins again at '''Foundations''' and progresses through the Pilot Loop.
 == How to use this compass ==

Sovereign: Calibration Report | 2026-07-23 | v0.1 | Self-Assessment | Capability Development Roadmap Landmark freeze: compass+landmarks; infancy/apple-seed rules; phases 0–8; path so far; gaming boundary; Phase 0–2 heavy / 3 starting. Capability ≠ page count. Permanent Beta.

2026-07-23T19:02:38Z

Calibration Report | 2026-07-23 | v0.1 | Self-Assessment | Capability Development Roadmap Landmark freeze: compass+landmarks; infancy/apple-seed rules; phases 0–8; path so far; gaming boundary; Phase 0–2 heavy / 3 starting. Capability ≠ page count. Permanent Beta.

New page

= Capability Development Roadmap =

This page is a '''compass and set of landmarks''', not a railroad. Side paths may be discovered. Backtracking is allowed when evidence requires it. Surprise work is welcome. '''None of that redefines phase completion''' unless exit criteria are deliberately revised.

{{GameModule
| type =  Framework Model
| category = [[:Category:Meta & Framework|Meta & Framework]]
| Calibration Type =  Framework Layer
| Application Layer =  Framework Infrastructure
| Version = 0.1
| Maturity =  Experimental
| Last Updated = 2026-07-23
| description = Compass-and-landmarks capability path for Metrology of the Abstract and The Sovereign Games. Phases track operational capability with exit criteria, not page count. Subject to infancy and development rules; Permanent Beta. Surprise discoveries allowed; they do not redefine phase completion.
}}

== Charter ==

'''Purpose:''' Track the emergence of '''operational capability''' within the discipline.

Phases represent new abilities the system can '''demonstrate''', not the completion of documents. Exit criteria are based on '''observable capability''', not page count or activity volume.

'''Compass and landmarks:''' The path orients work. It does not forbid discovery. New trails may open; wrong turns may require backtrack. Landmarks (exit criteria) still define whether a phase is complete.

'''Project rules:'''
* Surprise discoveries remain allowed; they do not redefine phase completion.
* Phase completion is demonstrated by operational capability, not by page count.
* Instrument maturity (Experimental → Reference Standard Candidate) measures a '''page or tool'''. This roadmap measures '''project capability'''. Do not mix the scoreboards.

== Infancy and development rules ==

Have you ever seen an apple seed?

A seed is not a failed orchard. It is not graded by fruit count, canopy size, or whether it already feeds a village. It is graded by whether it is alive, oriented, and planted in conditions where growth is possible.

This roadmap and the project it describes remain in '''infancy'''. Process is still messy. Conventions are still forming. That is expected under development rules and [[Permanent Beta]].

{| class="wikitable"
! Infancy rule !! Meaning
|-
| Do not demand Operational behavior from Foundations work || Early phases produce language, scaffold, and citable architecture — not a full pilot factory
|-
| Mess is not the same as drift || Unfinished structure under active correction differs from silent contradiction left unlabeled
|-
| Labels stay honest || Experimental and Self-Assessed are strengths when true; inflating grade is a nonconformance
|-
| Development rules still bind || Pre-cal before content theater; log nonconformances before cosmetic fixes; standing remains tier-qualified
|-
| The seed is allowed to look like a seed || Outsiders and collaborators evaluate phase-appropriate capability, not a fantasy of finished NIST-for-abstract-systems
|}

These rules do not lower the bar for later phases. They prevent category error: judging Phase 0–2 by Phase 7 criteria.

== What success means (destination landmark) ==

Operational success for the calibration core means:

* Calibration '''procedures''' in routine use
* Calibration '''reports''' produced as normal work
* Calibration '''recommendations''' in conditional form (If objective is X, evidence suggests Y)
* Real-world (or clear outcome-contact) application cals feeding '''system''' improvement

That cluster is approximately '''Phase 5–7''', not “Phase 2 looking busy.”

== Path so far (landmarks already passed or in progress) ==

Work already done is mostly '''Foundations → Scaffold → Core Architecture Stable''', with '''Procedure v0''' beginning (structural pre-cal checklists in force).

{| class="wikitable"
! Landmark !! Status (Self-Assessed)
|-
| Shared discipline framing (MoA; See → Refuse → Build; Permanent Beta) || In place and in active use
|-
| Standing / confirmation / self-check distinctions || Formalized; still deepening under use
|-
| Domain-appropriate standards; abstract standards are real; system was missing || Formalized as principle pages / lexicon entries
|-
| Working terminology as discipline glossary || Seeded (Experimental)
|-
| Wiki scaffold (categories, GameModule, Admin Page Status conventions) || Largely in place; still messy at edges
|-
| Structural pre-cal checklist as procedure fragment || In use — early Phase 3 signal
|-
| Report / recommendation templates as default operations || Not yet Operational
|-
| Tier-A or clear outcome-contact pilots closing the loop || Not yet satisfied as phase exit
|}

Excellent conceptual pages can accumulate in Phases 0–2 without moving project capability into Pilots or Operational. That fact is intentional honesty, not disparagement of the pages.

== Phases ==

| Phase | Name | Capability gained | Exit criteria |
|-------|------|-------------------|---------------|
| '''0''' | '''Foundations''' | Shared language, scope, boundaries | Working terminology available; physical–abstract boundary and “abstract standards are real; the system was missing” citable; discipline vs application explicit |
| '''1''' | '''Scaffold''' | Navigable, metadata-bearing corpus | Core pages carry agreed metadata patterns; static dates and category conventions reusable without reinventing each page |
| '''2''' | '''Core Architecture Stable''' | Citable core without weekly total rewrite | MoA hub, standing rules, and domain-appropriate boundary stable enough that procedures can point at them |
| '''3''' | '''Procedure v0''' | Same structural steps every time | Pre-cal checklist in force; content-cal steps written; nonconformance logged before fix as operating rule |
| '''4''' | '''Report v0''' | Outputs behave as instruments | Report and Cal Note templates exist; standing on the report; at least three sample reports, including at least one on a claim '''outside''' pure framework self-description |
| '''5''' | '''Recommendation v0''' | Conditional guidance | Reports carry If-objective-X / evidence-suggests-Y form; unbound prescription is not the default |
| '''6''' | '''Pilot Loop''' | System corrected by external contact | At least three logged cals that changed a procedure, glossary, or standard via correction memory; '''at least one Tier-A or clear outcome-contact pilot''' — not only framework-on-framework checks |
| '''7''' | '''Operational''' | Default path is procedure → report → recommendation | That loop is normal work, not a special event |
| '''8''' | '''Continuous Improvement''' | Permanent Beta as operations | Version bumps, new applications, and pilots are routine; no terminal “finished discipline” fantasy |

=== Spiral, not only ladder ===

The '''discipline''' may sit at Operational / Continuous Improvement while a '''new application''' re-enters Foundations through Pilot Loop. Mature method, immature deployment — normal engineering pattern.

== How to use this compass ==

# Declare one '''active phase'''.
# Keep that phase’s exit criteria short enough to argue about.
# Map new work to: advances a criterion · Future Layer · Development Breadcrumb · backtrack note.
# Close a phase only when exit criteria pass — then move the pointer.
# Revise landmarks deliberately when evidence requires; do not let excitement silently rewrite completion.

== Boundary condition — roadmap gaming ==

This project and its collaborators are strong at Foundations and Scaffold artifacts. A failure mode is indefinite production of excellent Phase 0–2 pages while Pilot Loop and outcome contact never start.

If Phase 6 is “completed” only by more framework-on-framework calibration theater, record a '''Readiness Gap''': documentation excellence is not operational capability.

== Current pointer (Self-Assessed) ==

'''Active region: Phase 0–2 heavy; Phase 3 starting.'''

Next landmark emphasis: harden Procedure v0, then Report v0 with at least one outward-facing sample — without demanding orchard-scale fruit from an apple seed.

== Status ==

{| class="wikitable"
! Field !! Value
|-
| Version || 0.1
|-
| Maturity || Experimental
|-
| Calibration review || Self-Assessment
|-
| Validation || Low — architectural freeze of the path; not field-proven as a management instrument
|-
| Role || Compass and landmarks for capability development
|-
| Freeze note || v0.1 locks the phase shape and rules for citation; still Permanent Beta and infancy-bound
|}

This page is in [[Permanent Beta]]. The freeze is a '''landmark freeze''' (stable enough to steer by), not a claim that the project has left infancy.

'''See the Game. Refuse the Game. Build Better.'''

== Open Calibration Items ==
* Confirm on-wiki links to Working Terminology and Abstract Standards principle pages when titles stabilize.
* Define numeric N and ownership for Phase 6 logging in a short Pilot Log convention.
* Revisit active-phase pointer after first three outward sample reports exist.

{{RelatedPages}}
{{Standalone Transparency}}
{{Calibration Dependent}}
{{Calibration Dependencies Display}}
{{Calibration Maintenance}}
{{Framework Reference}}
{{Calibration Procedure Reference}}
{{Tracking Logs Reference}}

{{Resource
| Title = Capability Development Roadmap
| URL = https://www.thesovereigngames.com/wiki/Capability_Development_Roadmap
| Description = Compass-and-landmarks path for operational capability in Metrology of the Abstract. Phases with exit criteria; infancy rules; surprise discoveries allowed without redefining phase completion.
| Category = Meta & Framework
}}

{{Admin Page Status


| categorization = Done

| calibration_review = Self-Assessment

| instrument_grade = Experimental

| validation = Low

| review_date = 2026-07-23
| reviewed_by =

| priority = Core
| review_threshold = 90

| has_backlinks = Not checked

| outbound_links_valid = Not checked

| in_outline = Yes
| in_category_outline = Yes

| templates_complete = Needs review

| formatting_standard = Meets standard

| symmetry_check = Not applicable

| self_report_flagged = No

| terminology_consistent = Yes

| standing_check = Self-assessed only

| drift_report_status = Breadcrumb-Open
| depends_on = Metrology of the Abstract; Permanent Beta; Metrology of the Abstract — Working Terminology; Abstract Standards Are Real; the System Was Missing
}}

[[Category:Meta & Framework]]
[[Category:Strategic Actionable Plans]]