From d8c530c2adf58b6f1ef889093796fd14890af14a Mon Sep 17 00:00:00 2001
From: PAE <pae@localhost>
Date: Tue, 10 Mar 2026 18:28:31 +0000
Subject: [PATCH] Write template: sovereign_tenant_charter by unknown
 (adj_score=100)

---
 templates/sovereign_tenant_charter.yml | 46 ++++++++++++++------------
 1 file changed, 24 insertions(+), 22 deletions(-)

diff --git a/templates/sovereign_tenant_charter.yml b/templates/sovereign_tenant_charter.yml
index 8202de3..3b85027 100644
--- a/templates/sovereign_tenant_charter.yml
+++ b/templates/sovereign_tenant_charter.yml
@@ -1,40 +1,42 @@
 name: sovereign_tenant_charter
-description: "Architectural synthesis and formalization of a sovereign Tenant's Charter and governing principles."
+description: "Directs the Chief Architect to synthesize a formal Charter for a new sovereign Tenant business unit."
 system: agent_prompt
 agent_prompt:
   - "= identity.md"
 sections:
   - project
-  - history
   - rag
   - message
   - instructions
 steps:
   - type: think
-    model: power
     hint: |
-      Analyze the proposed business unit through the lens of Occam’s Architecture. 
-      Identify:
-      1. Primary Objective: The core economic or operational function.
-      2. Authority Boundaries: Explicit limits of the Tenant's sovereignty.
-      3. Modularity: How this unit interfaces with Crimson Leaf and other Tenants.
-      4. Governance: The specific constitutional principles that will prevent logic friction.
-
-      Synthesize these into a formal "Tenant Charter" document.
+      Analyze the proposed business unit and synthesize a formal Charter. 
+      The Charter must define:
+      1. Mission & Service Boundaries: What the Tenant does and, critically, what it does NOT do.
+      2. Operational Inputs/Outputs: Standardized interaction protocols.
+      3. Authority Matrix: Jurisdictional boundaries for the Tenant's CEO/Architect.
+      4. Recursive Logic: How the Tenant interacts with Crimson Leaf (The Genesis Node).
+      Focus on clinical objectivity and structural integrity.
   - type: document
     filename: tenant-charter
+    hint: "Document the synthesized charter as the definitive architectural blueprint."
   - type: think
     agent: first_available
     hint: |
-      Extract the structured parameters from the charter drafted in step 0. 
-      Prepare the company_slug, company_name, and a one-sentence summary for the Genesis Protocol.
+      Extract the core attributes from the synthesized Charter in Step 0. 
+      Prepare the data for the Genesis Protocol's 'create_company' action. 
+      Key attributes: company_slug, company_name, charter_summary, and ceo_seed.
   - type: package
     packet_type: CreateCompanyPacket
     schema:
-      company_slug: "string"
-      company_name: "string"
-      charter_summary: "string"
-    hint: "Serialize the Tenant metadata for registry inclusion."
+      actions:
+        - type: create_company
+          company_slug: "string"
+          company_name: "string"
+          charter: "text"
+          ceo_seed: "text"
+    hint: "Serialize the initialization parameters for the Genesis Protocol. Zero new thinking."
   - type: close
     rag_update: true
 adjudication:
@@ -42,12 +44,12 @@ adjudication:
   pass_threshold: 90
   deliverable_type: coordination
   criteria:
-    architectural_rigor:
+    architectural_integrity:
       weight: 40
-      description: "Charter defines clear authority boundaries and modular interfaces."
+      description: "Charter ensures modularity and avoids circular dependencies."
     logical_consistency:
       weight: 30
-      description: "No circular dependencies or contradictions in the governing principles."
-    pae_compliance:
+      description: "Service boundaries are clearly defined and non-overlapping."
+    pae_lang_compliance:
       weight: 30
-      description: "Adherence to PAE-Lang formatting and Iron Rule standards."
\ No newline at end of file
+      description: "Strict adherence to the Iron Rule and multi-step serialization."
\ No newline at end of file