Collegium (AetherOS): Difference between revisions

Line 24:

For the inaugural period, the roles are filled by [[User:Isidore Lands|Isidore Lands]] as the `Custos Animae` and [[User:Silas Corvus|Silas Corvus]] as the `Custos Structurae`.

== Doctrine: Dogmata Aedificatorum ==

To ensure the long-term health, consistency, and maneuverability of the wiki's technical infrastructure, the Collegium hereby canonizes the '''Dogmata Aedificatorum'''. This doctrine mandates a professional, four-stage workflow for managing all templates and modules, moving beyond ad-hoc scripts to a fully integrated and auditable system.

Adherence to this pipeline is the primary responsibility of the [[Collegium (AetherOS)|Custos Structurae]] and its associated roles.

=== 1. Discover: The Dependency Map ===

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 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. Analyze: The Diagnostic Dashboard ===

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]].

* '''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. Deploy: The Praetor's Gateway ===

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.

* '''Standard Procedure''': The importer MUST operate using the canonical `dependency_map.json`; it is forbidden from performing its own live dependency crawling. It must support two modes of operation:

** <code>--page 'PageName'</code>: For importing a single page and its required dependencies.

** <code>--batch approved_list.txt</code>: For deploying a pre-approved list of assets.

* '''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. Maintain: The Quality Control Loop ===

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`).

* '''Standard Procedure''': The [[Wiki Maneuverability Score]] is calculated on a regular basis to monitor the health of the wiki's codebase. The Scribal Assistant is used by the [[Collegium (AetherOS)|Custos Animae]] and other editors to ensure the prose of documentation and articles adheres to a high standard of clarity and accessibility.

== Collegium Toolkit: Development Roadmap ==

To fully implement the Unified Pipeline, the following development tasks have been identified. They represent the official roadmap for evolving the Collegium's script collection into a professional-grade System Administration SDK.

=== Core Architecture & Workflow ===

* Implement a robust wikitext parsing library (e.g., <code>mwparserfromhell</code>) across all scripts to replace brittle regular expressions. This is the highest-priority technical-debt payment.

* Centralize all tunable constants (e.g., WM Score penalty weights) into a single, version-controlled configuration file (e.g., <code>collegium_config.yaml</code>).

=== Tool: Scriptor Explico (WM Score) ===

* The check for the <code>{{documentation}}</code> bonus must be enhanced. The script must verify that the corresponding <code>/doc</code> subpage not only exists but is also not a redlink and contains content.

* The script's output must be an "explainable" JSON object, detailing the exact penalties and bonuses applied, not just the final score.

=== Tool: Dependency & Deployment Suite ===

* Merge the functionality of <code>wiki_importer.py</code> and <code>batch_installer.py</code> into a single, canonical deployment tool for the Praetor.

* Refactor the unified importer to use the static <code>dependency_map.json</code> as its sole source for dependency information.

* Implement the mandatory <code>--dry-run</code> flag in the unified importer to provide a pre-flight check before any writes are made to the wiki.

* Integrate the WM Score into the <code>dependency_analyzer.py</code> visualization, color-coding nodes to create a true diagnostic dashboard.

=== Tool: Scribal Quality Assistant ===

* Evolve the `active_voice_assistant.py` into a more comprehensive '''Scribal Quality Assistant'''.

* Add new checks and modes beyond passive voice, such as:

** <code>--check-jargon</code>: To identify overly technical terms that should be linked to a glossary or simplified.

** <code>--check-reading-level</code>: To calculate and report a standard readability score (e.g., Flesch-Kincaid) to ensure content is accessible.

@@ Line 24: / Line 24: @@
 For the inaugural period, the roles are filled by [[User:Isidore Lands|Isidore Lands]] as the `Custos Animae` and [[User:Silas Corvus|Silas Corvus]] as the `Custos Structurae`.
+== Doctrine: Dogmata Aedificatorum ==
+To ensure the long-term health, consistency, and maneuverability of the wiki's technical infrastructure, the Collegium hereby canonizes the '''Dogmata Aedificatorum'''. This doctrine mandates a professional, four-stage workflow for managing all templates and modules, moving beyond ad-hoc scripts to a fully integrated and auditable system.
+Adherence to this pipeline is the primary responsibility of the [[Collegium (AetherOS)|Custos Structurae]] and its associated roles.
+=== 1. Discover: The Dependency Map ===
+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 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. Analyze: The Diagnostic Dashboard ===
+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]].
+* '''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. Deploy: The Praetor's Gateway ===
+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.
+* '''Standard Procedure''': The importer MUST operate using the canonical `dependency_map.json`; it is forbidden from performing its own live dependency crawling. It must support two modes of operation:
+** <code>--page 'PageName'</code>: For importing a single page and its required dependencies.
+** <code>--batch approved_list.txt</code>: For deploying a pre-approved list of assets.
+* '''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. Maintain: The Quality Control Loop ===
+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`).
+* '''Standard Procedure''': The [[Wiki Maneuverability Score]] is calculated on a regular basis to monitor the health of the wiki's codebase. The Scribal Assistant is used by the [[Collegium (AetherOS)|Custos Animae]] and other editors to ensure the prose of documentation and articles adheres to a high standard of clarity and accessibility.
+== Collegium Toolkit: Development Roadmap ==
+To fully implement the Unified Pipeline, the following development tasks have been identified. They represent the official roadmap for evolving the Collegium's script collection into a professional-grade System Administration SDK.
+=== Core Architecture & Workflow ===
+* Implement a robust wikitext parsing library (e.g., <code>mwparserfromhell</code>) across all scripts to replace brittle regular expressions. This is the highest-priority technical-debt payment.
+* Centralize all tunable constants (e.g., WM Score penalty weights) into a single, version-controlled configuration file (e.g., <code>collegium_config.yaml</code>).
+=== Tool: Scriptor Explico (WM Score) ===
+* The check for the <code>{{documentation}}</code> bonus must be enhanced. The script must verify that the corresponding <code>/doc</code> subpage not only exists but is also not a redlink and contains content.
+* The script's output must be an "explainable" JSON object, detailing the exact penalties and bonuses applied, not just the final score.
+=== Tool: Dependency & Deployment Suite ===
+* Merge the functionality of <code>wiki_importer.py</code> and <code>batch_installer.py</code> into a single, canonical deployment tool for the Praetor.
+* Refactor the unified importer to use the static <code>dependency_map.json</code> as its sole source for dependency information.
+* Implement the mandatory <code>--dry-run</code> flag in the unified importer to provide a pre-flight check before any writes are made to the wiki.
+* Integrate the WM Score into the <code>dependency_analyzer.py</code> visualization, color-coding nodes to create a true diagnostic dashboard.
+=== Tool: Scribal Quality Assistant ===
+* Evolve the `active_voice_assistant.py` into a more comprehensive '''Scribal Quality Assistant'''.
+* Add new checks and modes beyond passive voice, such as:
+** <code>--check-jargon</code>: To identify overly technical terms that should be linked to a glossary or simplified.
+** <code>--check-reading-level</code>: To calculate and report a standard readability score (e.g., Flesch-Kincaid) to ensure content is accessible.

Collegium (AetherOS): Difference between revisions

Navigation menu

Search