Write template: tenant_charter_standardization by unknown (adj_score=100)

templates/tenant_charter_standardization.yml

@@ -3,6 +3,8 @@ description: "Architectural synthesis of a sovereign Tenant's Charter, ensuring
 system: agent_prompt
 agent_prompt:
   - "= identity.md"
+skills:
+  - guides/PAETemplateGuide.md
 sections:
   - agent
   - project
@@ -13,20 +15,23 @@ sections:
 steps:
   - type: think
     hint: |
-      Analyze the proposed business unit through the lens of Silas's Architectural Standards.
+      Critically evaluate the proposed business unit. 
-      1. Define the 'Black Box' boundary: What is the exact transformation performed on inputs?
+      1. Define the 'Black Box': What are the exact Inputs and Outputs?
-      2. Identify the core service: Is it a specific, non-generalist mission?
+      2. Verify Sovereignty: Can this unit function if all other Tenants are offline?
-      3. Audit for circularity: Does this unit depend on another internal unit in a way that creates a recursive loop?
+      3. Audit for Redundancy: Does this overlap with existing units in the RAG/Portfolio?
-      4. Strategy: Draft the 'charter.md' content including Role, Core Directives, and Input/Output definitions.
+      4. Simplify: Apply Occam's Razor to the service boundary.
+      
+      Provide a technical justification for the charter's structure.
   - type: document
     filename: charter
+    hint: "Formalize the results of the previous analysis into the charter.md format."
   - type: package
     packet_type: CharterFinalization
     schema:
-      charter_status: "string"
+      status: "string"
-      primary_directive: "string"
+      tenant_name: "string"
-      sovereignty_score: "integer 1-100"
+      structural_purity_score: "integer 1-100"
-    hint: "Serialize the architectural status and metadata of the drafted charter."
+    hint: "Serialize the metadata of the finalized charter. Do not include prose."
   - type: close
     rag_update: true
 adjudication:
@@ -36,7 +41,7 @@ adjudication:
   criteria:
     architectural_purity:
       weight: 60
-      description: "Charter defines a narrow, non-generalist service boundary with zero redundancy."
+      description: "Boundaries are narrow, non-recursive, and exhibit zero redundancy."
     operational_sovereignty:
       weight: 40
-      description: "The unit is described as a discrete black-box capable of independent operation."
+      description: "The charter enables independent black-box operation."