Collegium (AetherOS) - Revision history

AdminIsidore at 01:41, 12 August 2025

2025-08-12T01:41:52Z

← Older revision		Revision as of 01:41, 12 August 2025
Line 102:		Line 102:
	** <code>--check-jargon</code>: Identifies overly technical terms that should be linked to a glossary or simplified.		** <code>--check-jargon</code>: Identifies overly technical terms that should be linked to a glossary or simplified.
	** <code>--check-reading-level</code>: Calculates a standard readability score to ensure content is accessible.		** <code>--check-reading-level</code>: Calculates a standard readability score to ensure content is accessible.

			== 6. The Three-Tiered Protocol for Virtuous Operation ==
			The Collegium acknowledges two fundamental and opposing challenges inherent in any complex, evolving system:

			# '''The Combinatorial Explosion of Value:''' The "virtuousness" of the wiki's architecture is an emergent property of the interactions between all components. The true value function, <math>v: 2^N \to \mathbb{R}</math>, would require evaluating every possible subset of our ''N'' components—a computationally impossible task.
			# '''The Scarcity of Context:''' Achieving a holistic, "God View" of the system requires an immense context window, as demonstrated by the journey to establish this very framework. Conversely, a developer focused on a single component operates with a minimal, localized context.

			The protocol does not seek to "solve" these challenges in an absolute sense. Instead, it manages this tension by evolving '''[[Converti (AetherOS)\|Converti]]''' into an SDK capable of analyzing not just components, but '''Project Coalitions''', and synthesizing that analysis into '''On-Demand Architectural Briefs'''. This enables a formal, three-tiered system of operation, ensuring every contributor has precisely the scope of context required for their task.

			=== 6.1 The Macro-Scale: The Collegium and The God View ===
			This tier is the domain of the [[Collegium (AetherOS)\|Collegium]] itself, tasked with strategic oversight of the entire system.
			* '''Operator:''' The [[Collegium (AetherOS)\|Custos Animae]], [[Collegium (AetherOS)\|Custos Structurae]], and other senior members.
			* '''Context:''' The complete, unfiltered '''"God View"''' of the wiki's architecture.
			* '''Primary Tools:''' The full outputs of <code>converti map</code> and <code>converti audit</code>.
			* '''Objective:''' To make high-level, strategic decisions about the long-term health of the ecosystem, approve the definition of official "Projects," and set architectural policy.

			=== 6.2 The Meso-Scale: The Squad Leader and the Architectural Brief ===
			This tier is designed for the team lead, the feature owner, or the specialist AI agent who must understand a coherent subsystem without absorbing the context of the entire wiki.
			* '''Operator:''' A mid-level developer, a specialist AI agent, or the [[Collegium (AetherOS)\|Quaesitor]] performing a targeted review.
			* '''Context:''' A '''Scoped Context''', delivered as a concise, actionable mission briefing.
			* '''Primary Tools:'''
			** '''<code>converti audit --project <project_file.yml></code>''': This command performs a targeted audit on a pre-defined '''Project''' (a curated list of related templates and modules). It generates a '''Project Virtuousness Report''' which, in addition to individual [[Wiki Maneuverability Score\|WM Scores]], calculates metrics for the coalition itself:
			*** '''Cohesion Score (Bonus):''' Measures the degree of internal dependency within the project.
			*** '''Coupling Score (Penalty):''' Measures the project's reliance on components outside its defined scope.
			*** '''Redundancy Score (Penalty):''' Heuristically detects overlapping functionality between components within the project.
			** '''<code>converti brief --project <project_file.yml></code>''': This command is the ultimate tool for managing context scarcity. It feeds the project's source code, documentation, and Virtuousness Report into a "Quaesitor" LLM to synthesize an '''On-Demand Architectural Brief'''. This brief is a markdown document of no more than 2,000 tokens containing five mandatory sections:
			*** # '''Mandate:''' The core purpose and philosophy of the subsystem.
			*** # '''Architecture Overview:''' A high-level description of component interactions.
			*** # '''Current Virtues:''' The subsystem's primary strengths, based on the audit.
			*** # '''Current Debts:''' The primary challenges and risks, based on the audit.
			*** # '''Directives for Action:''' A short, bulleted list of critical rules a developer must follow when modifying this subsystem.

			=== 6.3 The Micro-Scale: The Coder and The Code ===
			This is the foundational tier, focused on the implementation of a single, well-defined task by an individual contributor.
			* '''Operator:''' Any developer or AI Wingman.
			* '''Context:''' A '''Code-Level Context''', focused entirely on the specific file or files being edited.
			* '''Primary Tools:'''
			** '''<code>converti format</code>''': To automatically apply the sanctioned code style.
			** '''<code>converti draft</code>''': To perform a pre-flight check for code quality and adherence to local best practices.
			* '''Objective:''' The virtuous implementation of a single task within the clear directives provided by a higher-level brief, ensuring that local actions contribute positively to the health of the global system.

AdminIsidore: /* 4.1 The Sanctioned Formatter Toolchain */

2025-08-12T01:15:44Z

4.1 The Sanctioned Formatter Toolchain

← Older revision		Revision as of 01:15, 12 August 2025
Line 56:		Line 56:
	All code contributions in PHP, Lua, and CSS must be processed through a sanctioned, opinionated formatter. The goal of this mandate is to completely eliminate subjective style debates, ensure consistency, and produce minimal, predictable diffs. This consistency is critical for the efficiency of both human editors and AI agents like [[ARC (AetherOS)\|ARC]]. The following tools, inspired by the minimalist philosophy of ''Black'' and ''Prettier'', are canonized for this purpose:		All code contributions in PHP, Lua, and CSS must be processed through a sanctioned, opinionated formatter. The goal of this mandate is to completely eliminate subjective style debates, ensure consistency, and produce minimal, predictable diffs. This consistency is critical for the efficiency of both human editors and AI agents like [[ARC (AetherOS)\|ARC]]. The following tools, inspired by the minimalist philosophy of ''Black'' and ''Prettier'', are canonized for this purpose:

	* '''For PHP:''' [[https://github.com/~~pretty-php~~/~~pretty-php\|~~pretty-php]]		* '''For PHP:''' Pretty PHP [[https://github.com/lkrms/pretty-php]]
	* '''For Lua:''' [[https://github.com/JohnnyMorganz/~~StyLua\|~~StyLua]]		* '''For Lua:''' StyLua [[https://github.com/JohnnyMorganz/StyLua]]
	* '''For CSS:''' [[https://prettier.io/\|Prettier]]		* '''For CSS:''' Prettier [[https://prettier.io/\|Prettier]]

	These formatters will be integrated directly into the '''[[Converti (AetherOS)\|converti]]''' SDK's `draft` command, providing a single, automated point of enforcement for all code entering the ecosystem. Configuration will be minimal and centrally managed within the `Converti` repository.		These formatters will be integrated directly into the '''[[Converti (AetherOS)\|converti]]''' SDK's `draft` command, providing a single, automated point of enforcement for all code entering the ecosystem. Configuration will be minimal and centrally managed within the `Converti` repository.

AdminIsidore at 01:12, 12 August 2025

2025-08-12T01:12:09Z

← Older revision		Revision as of 01:12, 12 August 2025
Line 70:		Line 70:
	# '''Layer 4: Automated Oversight (The Watcher):''' A maintenance bot, operated by the `Custos Structurae`, will periodically scan for non-compliant pages that may have bypassed the filter. The bot is authorized to revert non-compliant creations and notify the creator, ensuring the integrity of the policy.		# '''Layer 4: Automated Oversight (The Watcher):''' A maintenance bot, operated by the `Custos Structurae`, will periodically scan for non-compliant pages that may have bypassed the filter. The bot is authorized to revert non-compliant creations and notify the creator, ensuring the integrity of the policy.

	== 5. Collegium ~~Toolkit:~~ Development Roadmap ==		== 5. Converti: The Collegium's SDK and Development Roadmap ==
	~~To fully implement the Unified Pipeline and the mandates for structural integrity, 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.		The "Collegium Toolkit" is not a loose collection of scripts; it is a single, integrated SDK known as '''[[Converti (AetherOS)\|Converti]]'''. All previously separate tools are to be deprecated and their functionality folded into `Converti` as distinct commands and capabilities.

	~~=== 5.1 Core Architecture & Workflow ===~~		`Converti` is the canonized, opinionated, CLI-based quality and production system for the AetherOS wiki. It is designed to be downloaded and run directly in the terminal by any contributor—human developers and their AI Wingmen ([[ARC (AetherOS)\|Code Virtuoso's Companions]]) alike. Its sole purpose is to provide a unified pipeline to draft, validate, and deploy high-quality, "virtuous" code to the wiki, and to assist in the removal or refactoring of graceless code.
	* 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~~, ~~sanctioned formatter paths) into a single, version~~-~~controlled configuration file (e.g.~~, <code~~>collegium_config.yaml</code>).~~
	* Integrate the ~~sanctioned PHP, Lua~~, and ~~CSS formatters into the `Converti` SDK~~ to ~~automate~~ the ~~enforcement~~ of ~~the Formatter Toolchain mandate~~.

	~~=== 5.2 Tool: Scriptor Explico (WM Score) ===~~		The following roadmap outlines the planned evolution of `Converti` into this comprehensive SDK.
	* 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 a minimum character count.
	* The script's output must be an "explainable" JSON object, detailing the exact penalties and bonuses applied, not just the final score.

	=== 5.~~3 Tool: Dependency & Deployment Suite~~ ===		=== 5.1 Core Architecture and Pipeline ===
	* ~~Merge the functionality of~~ <code>~~wiki_importer.py~~</code> and ~~<code>batch_installer~~.~~py</code> into a single, canonical deployment tool for~~ the ~~Praetor, tentatively named~~ '''~~praetor_importer.py~~'''.		The foundation of the SDK will be upgraded to ensure maximum robustness and automation.
	* Refactor the unified importer to use the static <code>~~dependency_map~~.~~json~~</code> ~~as its sole source for dependency information~~. ~~On-~~the~~-fly crawling is deprecated~~.		* '''Parsing Engine Upgrade:''' `Converti`'s wikitext parsing engine will be rebuilt using a dedicated library (e.g., <code>mwparserfromhell</code>). This will replace all brittle regular expression-based logic, ensuring accurate and reliable analysis of complex templates and modules. This is the highest-priority technical-debt payment.
	* ~~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~~.		* '''Centralized Configuration:''' `Converti` will be driven by a single, version-controlled configuration file, <code>collegium_config.yaml</code>. This file will contain all tunable constants, including WM Score weights and formatter paths, making the entire system's behavior transparent and easy to adjust.
	* Integrate the WM Score into the <code>~~dependency_analyzer.py~~</code> ~~visualization~~, ~~color-coding nodes~~ to ~~create a true diagnostic dashboard for~~ the ~~Quaesitor~~.		* '''Integrated Formatter Toolchain:''' The sanctioned code formatters ('''[[https://github.com/pretty-php/pretty-php\|pretty-php]]''', '''[[https://github.com/JohnnyMorganz/StyLua\|StyLua]]''', and '''[[https://prettier.io/\|Prettier]]''') will be integrated directly into the SDK. A new command, <code>converti format</code>, will be created to automatically apply the canonized style to any staged codebase.

	=== 5.~~4 Tool~~: ~~Scribal Quality Assistant~~ ===		=== 5.2 Commands for Analysis and Discovery (The Quaesitor's Toolkit) ===
	* ~~Evolve~~ the `active_voice_assistant.py` into a ~~more~~ comprehensive '''Scribal Quality Assistant'''.		This suite of commands allows the [[Collegium (AetherOS)\|Quaesitor]] to map and audit the wiki's entire structural landscape.
	* ~~Add new checks and modes beyond~~ passive voice~~, such as:~~		* '''<code>converti map</code>''': This command replaces the standalone `dependency_resolver.py`. It takes a list of root pages as input and generates the canonical <code>dependency_map.json</code> artifact, which serves as the static worldview for all other commands.
	** <code>--check-jargon</code>: ~~To identify~~ overly technical terms that should be linked to a glossary or simplified.		* '''<code>converti audit</code>''': This powerful command replaces both `dependency_analyzer.py` and `scriptor_explico.py`. It consumes the <code>dependency_map.json</code> and performs a full analysis, generating:
	** <code>--check-reading-level</code>: ~~To calculate and report~~ a standard readability score ~~(e.g., Flesch-Kincaid)~~ to ensure content is accessible ~~to a broader audience~~.		** The '''[[Wiki Maneuverability Score]]''' for every page in the map, with an enhanced check to ensure documentation pages exist and are not empty.
			** A detailed, "explainable" JSON output that breaks down the calculation for each page's score.
			** A human-readable text report summarizing the most foundational and complex pages.
			** An enriched, interactive HTML graph where nodes are '''color-coded by their WM Score''' and '''sized by their foundational importance''', creating a true diagnostic dashboard.

			=== 5.3 Commands for Deployment and Maintenance (The Praetor's Gateway) ===
			This suite provides the tools for the [[Collegium (AetherOS)\|Praetor]] and [[Collegium (AetherOS)\|Custos Animae]] to manage the lifecycle of code on the wiki.
			* '''<code>converti deploy</code>''': This command replaces both `wiki_importer.py` and `batch_installer.py`, becoming the sole, sanctioned gateway for deploying code. It is driven by the static dependency map and supports two primary modes:
			** <code>converti deploy --page 'Template:Infobox'</code>: For deploying a single asset and its dependencies.
			** <code>converti deploy --batch approved_list.txt</code>: For executing a controlled, batch deployment of pre-vetted assets.
			* '''Mandatory Dry-Run Protocol:''' The `deploy` command will feature a mandatory <code>--dry-run</code> flag. This provides a pre-flight check that generates a report of all proposed changes (creations, skips, errors) without writing to the wiki, ensuring all deployments are deliberate and auditable.
			* '''<code>converti assist</code>''': This command evolves the `active_voice_assistant.py` into a comprehensive '''Scribal Quality Assistant''' for interactive content improvement. It will feature several modes for authors:
			** <code>--check-voice</code>: The original check for passive voice.
			** <code>--check-jargon</code>: Identifies overly technical terms that should be linked to a glossary or simplified.
			** <code>--check-reading-level</code>: Calculates a standard readability score to ensure content is accessible.

AdminIsidore: /* Collegium Toolkit: Development Roadmap */

2025-08-12T01:05:44Z

Collegium Toolkit: Development Roadmap

AdminIsidore: /* Doctrine: Dogmata Aedificatorum */

2025-08-12T01:04:37Z

Doctrine: Dogmata Aedificatorum

@@ Line 29: / Line 29: @@
 These are not guidelines; they are binding protocols enforced through automated tooling and administrative oversight, primarily executed by the [[Collegium (AetherOS)|Custos Structurae]] and the [[Collegium (AetherOS)|Praetor]].
 === Omnia vivunt, omnia inter se conexa -- Discover: The Dependency Map ===
@@ Line 65: / Line 53: @@
 * '''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.
-=== Practical Applications ===
+=== 4.1 The Sanctioned Formatter Toolchain ===
 # '''Layer 1: User Guidance (The Nudge):''' A custom JavaScript payload deployed via <code>MediaWiki:Common.js</code> will detect attempts to create a new page in the Template or Module namespaces. It will then display a prominent, helpful notification guiding the user to create a <code>/sandbox</code> subpage instead.
 # '''Layer 2: Technical Enforcement (The Gate):''' The [[Extension:AbuseFilter|AbuseFilter extension]] is configured to disallow the creation of any new page in the Template (NS_TEMPLATE) or Module (NS_MODULE) namespaces unless the page title ends with <code>/sandbox</code>. This provides a hard, non-bypassable technical block.

AdminIsidore: /* Doctrine: Dogmata Aedificatorum */

2025-08-12T01:03:46Z

Doctrine: Dogmata Aedificatorum

← Older revision		Revision as of 01:03, 12 August 2025
Line 28:		Line 28:
	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.		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~~.		These are not guidelines; they are binding protocols enforced through automated tooling and administrative oversight, primarily executed by the [[Collegium (AetherOS)\|Custos Structurae]] and the [[Collegium (AetherOS)\|Praetor]].

	=== 1. Omnia vivunt, omnia inter se conexa -- Discover: The Dependency Map ===		=== 4.1 The Sanctioned Formatter Toolchain ===
			All code contributions in PHP, Lua, and CSS must be processed through a sanctioned, opinionated formatter. The goal of this mandate is to completely eliminate subjective style debates, ensure consistency, and produce minimal, predictable diffs. This consistency is critical for the efficiency of both human editors and AI agents like [[ARC (AetherOS)\|ARC]]. The following tools, inspired by the minimalist philosophy of ''Black'' and ''Prettier'', are canonized for this purpose:

			* '''For PHP:''' [[https://github.com/pretty-php/pretty-php\|pretty-php]]
			* '''For Lua:''' [[https://github.com/JohnnyMorganz/StyLua\|StyLua]]
			* '''For CSS:''' [[https://prettier.io/\|Prettier]]

			These formatters will be integrated directly into the '''[[Converti (AetherOS)\|converti]]''' SDK's `draft` command, providing a single, automated point of enforcement for all code entering the ecosystem. Configuration will be minimal and centrally managed within the `Converti` repository.

			=== 4.2 The Sandbox-First Mandate ===
			To protect the stability of the live environment, all new templates and modules must be created and tested in a sandbox environment before being promoted to the main namespace. Direct creation of live templates and modules is forbidden. This mandate is enforced through a multi-layered technical and procedural framework:

			=== 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. Salus populi suprema lex esto -- Analyze: The Diagnostic Dashboard ===		=== 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. Quo Eundum! -- Deploy: The Praetor's Gateway ===		=== 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 60:
	* '''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. Pacta sunt servanda pietate -- Align: The Quality Control Loop ===		=== 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`).
	* '''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.		* '''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.

			=== Practical Applications ===
			# '''Layer 1: User Guidance (The Nudge):''' A custom JavaScript payload deployed via <code>MediaWiki:Common.js</code> will detect attempts to create a new page in the Template or Module namespaces. It will then display a prominent, helpful notification guiding the user to create a <code>/sandbox</code> subpage instead.
			# '''Layer 2: Technical Enforcement (The Gate):''' The [[Extension:AbuseFilter\|AbuseFilter extension]] is configured to disallow the creation of any new page in the Template (NS_TEMPLATE) or Module (NS_MODULE) namespaces unless the page title ends with <code>/sandbox</code>. This provides a hard, non-bypassable technical block.
			# '''Layer 3: Procedural Framework (The Path):''' The [[Extension:TemplateSandbox\|TemplateSandbox extension]] is the officially sanctioned tool for testing and previewing changes made in sandbox pages. The workflow is as follows: creation in the sandbox, testing via `Special:TemplateSandbox`, and finally, promotion to the main namespace by a member of the Collegium.
			# '''Layer 4: Automated Oversight (The Watcher):''' A maintenance bot, operated by the `Custos Structurae`, will periodically scan for non-compliant pages that may have bypassed the filter. The bot is authorized to revert non-compliant creations and notify the creator, ensuring the integrity of the policy.

	== Collegium Toolkit: Development Roadmap ==		== Collegium Toolkit: Development Roadmap ==

AdminIsidore: /* Doctrine: Dogmata Aedificatorum */

2025-08-12T01:00:11Z

Doctrine: Dogmata Aedificatorum

AdminIsidore: /* 4. Align: The Quality Control Loop */

2025-08-12T00:52:24Z

4. Align: The Quality Control Loop

← Older revision		Revision as of 00:52, 12 August 2025
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. Align: The Quality Control Loop ===		=== 4. Conservo et aligno -- 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`).

AdminIsidore: /* 3. Deploy: The Praetor's Gateway */

2025-08-12T00:50:39Z

3. Deploy: The Praetor's Gateway

← Older revision		Revision as of 00:50, 12 August 2025
Line 40:		Line 40:
	* '''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. Deploy: The Praetor's Gateway ===		=== 3. Displicare (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.

AdminIsidore: /* 2. Analyze: The Diagnostic Dashboard */

2025-08-12T00:49:41Z

2. Analyze: The Diagnostic Dashboard

← Older revision		Revision as of 00:49, 12 August 2025
Line 35:		Line 35:
	* '''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. Analyze: The Diagnostic Dashboard ===		=== 2. Explico (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]].

← Older revision		Revision as of 01:15, 12 August 2025
Line 56:		Line 56:
	All code contributions in PHP, Lua, and CSS must be processed through a sanctioned, opinionated formatter. The goal of this mandate is to completely eliminate subjective style debates, ensure consistency, and produce minimal, predictable diffs. This consistency is critical for the efficiency of both human editors and AI agents like [[ARC (AetherOS)\|ARC]]. The following tools, inspired by the minimalist philosophy of ''Black'' and ''Prettier'', are canonized for this purpose:		All code contributions in PHP, Lua, and CSS must be processed through a sanctioned, opinionated formatter. The goal of this mandate is to completely eliminate subjective style debates, ensure consistency, and produce minimal, predictable diffs. This consistency is critical for the efficiency of both human editors and AI agents like [[ARC (AetherOS)\|ARC]]. The following tools, inspired by the minimalist philosophy of ''Black'' and ''Prettier'', are canonized for this purpose:

	* '''For PHP:''' [[https://github.com/~~pretty-php~~/~~pretty-php\|~~pretty-php]]		* '''For PHP:''' Pretty PHP [[https://github.com/lkrms/pretty-php]]
	* '''For Lua:''' [[https://github.com/JohnnyMorganz/~~StyLua\|~~StyLua]]		* '''For Lua:''' StyLua [[https://github.com/JohnnyMorganz/StyLua]]
	* '''For CSS:''' [[https://prettier.io/\|Prettier]]		* '''For CSS:''' Prettier [[https://prettier.io/\|Prettier]]

	These formatters will be integrated directly into the '''[[Converti (AetherOS)\|converti]]''' SDK's `draft` command, providing a single, automated point of enforcement for all code entering the ecosystem. Configuration will be minimal and centrally managed within the `Converti` repository.		These formatters will be integrated directly into the '''[[Converti (AetherOS)\|converti]]''' SDK's `draft` command, providing a single, automated point of enforcement for all code entering the ecosystem. Configuration will be minimal and centrally managed within the `Converti` repository.

← Older revision		Revision as of 01:05, 12 August 2025
Line 70:		Line 70:
	# '''Layer 4: Automated Oversight (The Watcher):''' A maintenance bot, operated by the `Custos Structurae`, will periodically scan for non-compliant pages that may have bypassed the filter. The bot is authorized to revert non-compliant creations and notify the creator, ensuring the integrity of the policy.		# '''Layer 4: Automated Oversight (The Watcher):''' A maintenance bot, operated by the `Custos Structurae`, will periodically scan for non-compliant pages that may have bypassed the filter. The bot is authorized to revert non-compliant creations and notify the creator, ensuring the integrity of the policy.

	== Collegium Toolkit: Development Roadmap ==		== 5. 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.		To fully implement the Unified Pipeline and the mandates for structural integrity, 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 ===		=== 5.1 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.		* 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>).		* Centralize all tunable constants (e.g., WM Score penalty weights, sanctioned formatter paths) into a single, version-controlled configuration file (e.g., <code>collegium_config.yaml</code>).
			* Integrate the sanctioned PHP, Lua, and CSS formatters into the `Converti` SDK to automate the enforcement of the Formatter Toolchain mandate.

	=== Tool: Scriptor Explico (WM Score) ===		=== 5.2 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 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 a minimum character count.
	* The script's output must be an "explainable" JSON object, detailing the exact penalties and bonuses applied, not just the final score.		* 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 ===		=== 5.3 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.		* Merge the functionality of <code>wiki_importer.py</code> and <code>batch_installer.py</code> into a single, canonical deployment tool for the Praetor, tentatively named '''praetor_importer.py'''.
	* Refactor the unified importer to use the static <code>dependency_map.json</code> as its sole source for dependency information.		* Refactor the unified importer to use the static <code>dependency_map.json</code> as its sole source for dependency information. On-the-fly crawling is deprecated.
	* 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.		* 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.		* Integrate the WM Score into the <code>dependency_analyzer.py</code> visualization, color-coding nodes to create a true diagnostic dashboard for the Quaesitor.

	=== Tool: Scribal Quality Assistant ===		=== 5.4 Tool: Scribal Quality Assistant ===
	* Evolve the `active_voice_assistant.py` into a more comprehensive '''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:		* 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-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.		** <code>--check-reading-level</code>: To calculate and report a standard readability score (e.g., Flesch-Kincaid) to ensure content is accessible to a broader audience.

← Older revision		Revision as of 01:00, 12 August 2025
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. ~~Invenio (~~Discover): The Dependency Map ===		=== 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. ~~Explico (~~Analyze): The Diagnostic Dashboard ===		=== 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. ~~Displicare (~~Deploy): The Praetor's Gateway ===		=== 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. ~~Conservo et aligno~~ -- Align: The Quality Control Loop ===		=== 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`).