Collegium (AetherOS): Difference between revisions

(One intermediate revision by the same user not shown)

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:

* '''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.

Line 102:

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

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

@@ 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:
-* '''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.
@@ Line 102: / Line 102: @@
 ** <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.
+== 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 &lt;project_file.yml&gt;</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 &lt;project_file.yml&gt;</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.

Collegium (AetherOS): Difference between revisions

Navigation menu

Search