55 lines
2.0 KiB
YAML
55 lines
2.0 KiB
YAML
name: sovereign_tenant_charter
|
|
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
|
|
- rag
|
|
- message
|
|
- instructions
|
|
steps:
|
|
- type: think
|
|
hint: |
|
|
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 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:
|
|
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:
|
|
enabled: true
|
|
pass_threshold: 90
|
|
deliverable_type: coordination
|
|
criteria:
|
|
architectural_integrity:
|
|
weight: 40
|
|
description: "Charter ensures modularity and avoids circular dependencies."
|
|
logical_consistency:
|
|
weight: 30
|
|
description: "Service boundaries are clearly defined and non-overlapping."
|
|
pae_lang_compliance:
|
|
weight: 30
|
|
description: "Strict adherence to the Iron Rule and multi-step serialization." |