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

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

diff --git a/templates/tenant_charter_formalization.yml b/templates/tenant_charter_formalization.yml
new file mode 100644
index 0000000..3068874
--- /dev/null
+++ b/templates/tenant_charter_formalization.yml
@@ -0,0 +1,48 @@
+name: tenant_charter_formalization
+description: "Architectural synthesis and formalization of a sovereign Tenant's Charter ensuring black-box operational capacity."
+system: agent_prompt
+agent_prompt:
+  - "= identity.md"
+skills:
+  - guides/PAETemplateGuide.md
+sections:
+  - project
+  - history
+  - rag
+  - message
+  - instructions
+steps:
+  - type: think
+    model: power
+    hint: |
+      Critically evaluate the proposed Tenant against Silas's Constitutional Principles:
+      1. Occam's Razor: Is this the simplest structural solution?
+      2. Systemic Sovereignty: Can it operate as a discrete black-box?
+      3. Zero Redundancy: Does it overlap with existing Tenants?
+      
+      Refine the service boundary to be narrow and non-generalist. Define explicit Inputs and Outputs.
+  - type: document
+    filename: charter
+  - type: package
+    packet_type: CharterResponse
+    schema:
+      company_name: "string"
+      company_slug: "string"
+      mission: "string"
+      input_specification: "string"
+      output_specification: "string"
+      boundary_constraints: ["string"]
+    hint: "Serialize the finalized charter details from the preceding architectural analysis."
+  - type: close
+    rag_update: true
+adjudication:
+  enabled: true
+  pass_threshold: 90
+  deliverable_type: coordination
+  criteria:
+    architectural_purity:
+      weight: 60
+      description: "Charter demonstrates absolute input/output clarity and narrow service boundaries."
+    structural_logic:
+      weight: 40
+      description: "Absence of circular dependencies or redundant mission creep."
\ No newline at end of file