Collegium (AetherOS): Difference between revisions
Jump to navigation
Jump to search
AdminIsidore (talk | contribs) |
AdminIsidore (talk | contribs) |
||
Line 30: | Line 30: | ||
Adherence to this pipeline is the primary responsibility of the [[Collegium (AetherOS)|Custos Structurae]] and its associated roles. | Adherence to this pipeline is the primary responsibility of the [[Collegium (AetherOS)|Custos Structurae]] and its associated roles. | ||
=== 1. | === 1. Omnia vivunt, omnia inter se conexa -- Discover: The Dependency Map === | ||
The foundation of all structural review is a comprehensive understanding of the wiki's dependency graph. | The foundation of all structural review is a comprehensive understanding of the wiki's dependency graph. | ||
* '''Canonical Tool''': [[scripts/dependency_resolver.py|dependency_resolver.py]] is the sole, authorized tool for analyzing the complete dependency tree of a given set of root pages. | * '''Canonical Tool''': [[scripts/dependency_resolver.py|dependency_resolver.py]] is the sole, authorized tool for analyzing the complete dependency tree of a given set of root pages. | ||
* '''Canonical Artifact''': The output of this tool, <code>dependency_map.json</code>, is considered the single source of truth for dependency relationships. On-the-fly dependency discovery by other scripts is forbidden to ensure all decisions are made from a common, static worldview. | * '''Canonical Artifact''': The output of this tool, <code>dependency_map.json</code>, is considered the single source of truth for dependency relationships. On-the-fly dependency discovery by other scripts is forbidden to ensure all decisions are made from a common, static worldview. | ||
=== 2. | === 2. Salus populi suprema lex esto -- Analyze: The Diagnostic Dashboard === | ||
With a definitive map, the [[Collegium (AetherOS)|Quaesitor]] can generate the necessary reports and visualizations to inform the Collegium. | With a definitive map, the [[Collegium (AetherOS)|Quaesitor]] can generate the necessary reports and visualizations to inform the Collegium. | ||
* '''Primary Tools''': [[scripts/scriptor_explico.py|scriptor_explico.py]] and [[scripts/dependency_analyzer.py|dependency_analyzer.py]]. | * '''Primary Tools''': [[scripts/scriptor_explico.py|scriptor_explico.py]] and [[scripts/dependency_analyzer.py|dependency_analyzer.py]]. | ||
* '''Standard Procedure''': The `dependency_analyzer` consumes the `dependency_map.json` to generate its report. Crucially, it must also integrate the [[Wiki Maneuverability Score]] calculated by `scriptor_explico` to enrich its visualization. The resulting interactive graph serves as the Collegium's primary diagnostic dashboard, color-coding nodes by their WM Score and sizing them by their foundational importance (in-degree). | * '''Standard Procedure''': The `dependency_analyzer` consumes the `dependency_map.json` to generate its report. Crucially, it must also integrate the [[Wiki Maneuverability Score]] calculated by `scriptor_explico` to enrich its visualization. The resulting interactive graph serves as the Collegium's primary diagnostic dashboard, color-coding nodes by their WM Score and sizing them by their foundational importance (in-degree). | ||
=== 3. | === 3. Quo Eundum! -- Deploy: The Praetor's Gateway === | ||
All new code enters the wiki through a single, controlled gateway managed by the [[Collegium (AetherOS)|Praetor]]. | All new code enters the wiki through a single, controlled gateway managed by the [[Collegium (AetherOS)|Praetor]]. | ||
* '''Canonical Tool''': A unified [[scripts/wiki_importer.py|wiki_importer.py]] (to be refactored and renamed '''praetor_importer.py''') is the only sanctioned method for importing templates and modules. | * '''Canonical Tool''': A unified [[scripts/wiki_importer.py|wiki_importer.py]] (to be refactored and renamed '''praetor_importer.py''') is the only sanctioned method for importing templates and modules. | ||
Line 48: | Line 48: | ||
* '''Critical Safety Protocol''': All deployment actions must first be run with the <code>--dry-run</code> flag to produce a report of intended changes. This report must be reviewed by the Praetor before a final, live deployment is executed. | * '''Critical Safety Protocol''': All deployment actions must first be run with the <code>--dry-run</code> flag to produce a report of intended changes. This report must be reviewed by the Praetor before a final, live deployment is executed. | ||
=== 4. | === 4. Pacta sunt servanda pietate -- Align: The Quality Control Loop === | ||
Ongoing quality is ensured through a suite of maintenance and quality assistance tools. | Ongoing quality is ensured through a suite of maintenance and quality assistance tools. | ||
* '''Primary Tools''': The refactored `scriptor_explico.py` and the '''Scribal Quality Assistant''' (evolved from `active_voice_assistant.py`). | * '''Primary Tools''': The refactored `scriptor_explico.py` and the '''Scribal Quality Assistant''' (evolved from `active_voice_assistant.py`). |