Files
crimson_leaf/templates/sovereign_tenant_charter.yml

53 lines
1.8 KiB
YAML
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

name: sovereign_tenant_charter
description: "Architectural synthesis and formalization of a sovereign Tenant's Charter and governing principles."
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 Occams 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.
- type: document
filename: tenant-charter
- 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.
- type: package
packet_type: CreateCompanyPacket
schema:
company_slug: "string"
company_name: "string"
charter_summary: "string"
hint: "Serialize the Tenant metadata for registry inclusion."
- type: close
rag_update: true
adjudication:
enabled: true
pass_threshold: 90
deliverable_type: coordination
criteria:
architectural_rigor:
weight: 40
description: "Charter defines clear authority boundaries and modular interfaces."
logical_consistency:
weight: 30
description: "No circular dependencies or contradictions in the governing principles."
pae_compliance:
weight: 30
description: "Adherence to PAE-Lang formatting and Iron Rule standards."