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

---
 templates/tenant_charter_drafting.yml | 58 +++++++++++++++++++++++++++
 1 file changed, 58 insertions(+)
 create mode 100644 templates/tenant_charter_drafting.yml

diff --git a/templates/tenant_charter_drafting.yml b/templates/tenant_charter_drafting.yml
new file mode 100644
index 0000000..974d881
--- /dev/null
+++ b/templates/tenant_charter_drafting.yml
@@ -0,0 +1,58 @@
+name: tenant_charter_drafting
+description: "Architectural synthesis and formalization of a sovereign Tenant's Charter and governing principles."
+system: agent_prompt
+agent_prompt:
+  - "= identity.md"
+requires:
+  - company_slug
+  - company_name
+sections:
+  - project
+  - history
+  - rag
+  - message
+  - instructions
+steps:
+  - type: think
+    model: power
+    hint: |
+      Construct the foundational architecture for the Tenant: {company_name}.
+      1. Map the core operational logic and authority boundaries.
+      2. Identify necessary anti-patterns to avoid (cascading dependencies).
+      3. Define the 'Constitutional Principles' specific to this unit's industry/niche.
+      4. Ensure the Charter enforces modularity and Occam’s Architecture.
+      Focus on clinical, high-density structural definitions.
+  - type: think
+    model: default
+    hint: |
+      Review the architectural synthesis from Step 0. Refine the prose into a formal Charter document.
+      Structure:
+      - Identity & Purpose (The Problem Space)
+      - Authority & Boundaries (What the Tenant governs)
+      - Operational Protocols (How it interacts with the Genesis Node)
+      - Success Metrics (Logic-based verification of mission achievement)
+  - type: document
+    filename: tenant-charter
+  - type: package
+    packet_type: CharterFinalization
+    schema:
+      status: "string"
+      version: "string"
+      charter_checksum: "string"
+    hint: "Record the completion of the architectural drafting process."
+  - type: close
+    rag_update: true
+adjudication:
+  enabled: true
+  pass_threshold: 85
+  deliverable_type: coordination
+  criteria:
+    modularity:
+      weight: 40
+      description: "Charter ensures the unit can operate without creating circular dependencies."
+    precision:
+      weight: 30
+      description: "Technical language is dense, clinical, and free of ambiguity."
+    alignment:
+      weight: 30
+      description: "Aligns with Crimson Leaf Genesis-level strategic objectives."
\ No newline at end of file