Converti (AetherOS): Difference between revisions
Jump to navigation
Jump to search
AdminIsidore (talk | contribs) Created page with "{{AetherOS_Component}} '''Converti''' is a command-line utility designed to import articles from external wikis, such as Wikipedia, and intelligently prepare them for use within the AetherOS ecosystem. It serves as a gatekeeper, ensuring that new information is clean, functional, and structurally sound before it becomes a source of knowledge for both human users and their Wingman AIs. The tool was developed by Isidore Lands and Silas..." |
AdminIsidore (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
{{AetherOS_Component}} | {{AetherOS_Component}} | ||
'''Converti''' is a command-line utility designed to | '''Converti''' is a command-line utility suite designed to manage the lifecycle of templates and modules within the AetherOS ecosystem. It serves as the primary toolkit for the [[Collegium (AetherOS)]], enabling the analysis, controlled importation, and quality assurance of the wiki's structural components. | ||
The tool was developed by [[User: | The tool was developed by [[User:Isidore Lands|Isidore Lands]] and [[User:Silas Corvus|Silas Corvus]]. | ||
== Purpose in Symbiotic Learning == | == Purpose in Symbiotic Learning == | ||
The core purpose of Converti is to | The core purpose of Converti is to ensure the structural integrity and maneuverability of the wiki's knowledge base. A lean, well-documented, and minimally dependent codebase is essential for the symbiotic learning between users and their [[Wingman AI|Wingman AIs]]. | ||
By providing tools to analyze and gracefully import components, Converti prevents "dependency hell" and ensures the wiki does not become cluttered with the unmanaged complexity of its source wikis. | |||
== | == The Converti Toolkit == | ||
Converti is a | Converti is comprised of several distinct scripts, each serving a specific function in the Collegium's review process. | ||
=== Stage 1: | === Stage 1: Dependency Analysis === | ||
The first step is to map the full dependency tree of a set of root templates from an external source like Wikipedia. | |||
* '''`dependency_resolver.py`''': Scans a list of templates and recursively maps every sub-template and Lua module they depend on, saving the result to `dependency_map.json`. | |||
* '''`dependency_analyzer.py` (`scriptor_explico.py`)''': Ingests the raw dependency map and generates a human-readable report (`dependency_report.txt`) and an interactive graph (`dependency_graph.html`), highlighting the most foundational and complex components. | |||
=== Stage 2: | === Stage 2: Controlled Import === | ||
After | After the `Custos Animae` and `Custos Structurae` have reviewed the analysis and created a curated `approved_list.txt`, the batch installer imports only the necessary components. | ||
* '''`batch_installer.py`''': Reads the approved list and the dependency map, and surgically imports only the approved pages and their direct dependencies from Wikipedia, skipping any that already exist on ooda.wiki. | |||
=== Stage 3: | === Stage 3: Quality Assurance & Refactoring === | ||
Once templates are imported, the Collegium can analyze their quality and complexity. | |||
* '''`scriptor_explico.py`''': Calculates a '''[[Wiki Maneuverability Score]]''' for each template based on its complexity, dependency count, and documentation quality. | |||
* '''`refactoring_assistant.py`''': (Under Development) An assistant that uses an LLM to review low-scoring templates and suggest simplifications or alternative implementations. | |||
== Future Development == | == Future Development == | ||
* '''Active Voice Assistant''': | * '''Active Voice Assistant''': An on-wiki tool to help editors convert passive voice to active voice, further improving the clarity and readability of the knowledge base. |