48 lines
1.5 KiB
YAML
48 lines
1.5 KiB
YAML
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." |