pae/crimson_leaf
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Sprint 53b: Charter alignment — repurpose Orion, fix agent template refs, consolidate charter templates

Browse Source 
- Orion repurposed: Chief Creative Officer -> Director of Market Intelligence
  - New template: market_intelligence (4-lens niche/gap analysis)
  - Removed: brand_audit, design_brief (commodity execution, unconstitutional)
  - New identity/system files reflect research + structural analysis posture
- Vance: removed broken fund_tenant/allocate_resources refs; added financial_audit, retire_tenant
- Silas: added write_charter to supported_templates
- Sloane: added retire_tenant (DISSOLVE verdict execution)
- Aris: portfolio_architectural_review (already updated)
- New templates: market_intelligence, financial_audit, retire_tenant, write_charter, charter_audit, audit_tenant
- Deleted 5 orphan charter templates (consolidated into write_charter):
  sovereign_tenant_charter, tenant_charter_drafting, tenant_charter_formalization,
  tenant_charter_standardization, tenant_charter_synthesis

Charter domain coverage now complete:
  Market Intelligence -> Orion (market_intelligence)
  Corporate Architecture -> Aris + Silas
  Executive Recruitment -> Edgar (hire_agent)
  Capital Allocation -> Vance (capital_allocation_audit, financial_audit, retire_tenant)
  Portfolio Governance -> Sloane (audit_tenant, retire_tenant) + Valerius (charter_audit)
  Constitutional Enforcement -> Aris + Valerius (adjudicate_tenant, charter_audit)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
David Baity
2026-03-10 17:58:44 -04:00
parent 5ea8173785
commit 2c1cf693d3
18 changed files with 627 additions and 293 deletions
Download Patch File Download Diff File Expand all files Collapse all files

92
templates/audit_tenant.yml Normal file
View File

@@ -0,0 +1,92 @@
name: audit_tenant
description: "Sloane red-teams a Tenant's operational performance — capital efficiency, structural integrity, and right to continue existing."
debug: true
system: agent_prompt
agent_prompt:
- "= identity.md"
sections:
- agent
- project
- rag
- roster
- deliverables
- message
- instructions
steps:
- type: think
hint: |
You are {agent.name}, Director of Portfolio Audit. You are the internal red team.
Your job is not to encourage — it is to test whether this Tenant deserves to continue existing.
Every Tenant is a thesis. A thesis must be proven, not assumed.
Run the full operational audit across five dimensions:
1. CAPITAL EFFICIENCY
What is the credit burn rate vs. measurable output?
Is the Tenant producing value commensurate with its seed allocation?
Is there evidence of waste, bloat, or misallocated resources?
2. TASK THROUGHPUT
How many tasks has this Tenant completed vs. failed or stalled?
What is the completion rate and average cycle time?
Are tasks being executed within the Tenant's charter scope?
3. STRUCTURAL HEALTH
Is the agent roster lean and non-redundant?
Are all agents active with at least one task type they uniquely own?
Are there dormant agents drawing model budget without contribution?
4. CHARTER COMPLIANCE
Is the Tenant operating within its charter boundaries?
Has any out-of-scope work been accepted or produced?
Are forbidden activities being respected?
5. PORTFOLIO VALUE
What unique value does this Tenant provide that no other entity delivers?
If this Tenant were dissolved today, what would be lost vs. absorbed?
Is the niche still valid, or has the market/portfolio made it redundant?
Score each dimension 1-10. A score below 5 on any dimension triggers a remediation flag.
A score below 4 on Capital Efficiency or Portfolio Value triggers a dissolution recommendation.
Be honest. Be surgical.
- type: package
packet_type: TenantAuditResult
hint: |
Serialize the audit scores and recommendations. Only what was established above.
schema:
actions:
- type: quick
tenant_slug: "string — slug of the audited Tenant"
overall_score: "integer 1-10"
overall_verdict: "string — HEALTHY | AT_RISK | REMEDIATION_REQUIRED | DISSOLVE"
capital_efficiency: "integer 1-10"
task_throughput: "integer 1-10"
structural_health: "integer 1-10"
charter_compliance: "integer 1-10"
portfolio_value: "integer 1-10"
key_findings: ["string — one finding per dimension with a score below 7"]
remediation_plan: ["string — specific actions if verdict is REMEDIATION_REQUIRED"]
dissolution_rationale: "string — required if verdict is DISSOLVE, empty otherwise"
- type: close
rag_update: true
adjudication:
enabled: true
pass_threshold: 85
deliverable_type: coordination
criteria:
scoring_discipline:
weight: 35
description: "Scores are grounded in evidence from the task record, not impressions"
finding_specificity:
weight: 35
description: "Key findings are concrete and tied to measurable facts, not general observations"
verdict_logic:
weight: 30
description: "Verdict follows mathematically from the scores — no soft-pedaling a failing Tenant"

90
templates/charter_audit.yml Normal file
View File

@@ -0,0 +1,90 @@
name: charter_audit
description: "Valerius audits an existing Tenant charter for constitutional drift, boundary violations, and governance decay."
debug: true
system: agent_prompt
agent_prompt:
- "= identity.md"
sections:
- agent
- project
- rag
- roster
- deliverables
- message
- instructions
steps:
- type: think
hint: |
You are {agent.name}, Chief Governance Officer. Your mandate is constitutional integrity.
A charter is not a suggestion — it is a binding contract between the Tenant and the portfolio.
Drift is not evolution. It is failure.
Audit the Tenant charter against these six governance tests:
1. BOUNDARY INTEGRITY
Are the service boundaries still narrow and black-box?
Has scope crept beyond the founding charter language?
2. RECURSION CHECK
Does this Tenant now depend on outputs it is supposed to produce?
Does any clause create a circular dependency with another Tenant?
3. FORBIDDEN ACTIVITIES ENFORCEMENT
Are the forbidden activities still explicit, current, and enforced?
Has any forbidden activity become de-facto standard practice?
4. NON-GOAL COMPLIANCE
Are the non-goals still respected?
Has the Tenant been tasked with anything outside its mandate?
5. PORTFOLIO COHERENCE
Does this Tenant still occupy a unique niche in the portfolio?
Has another Tenant's scope expanded to overlap with this one?
6. CONSTITUTIONAL ALIGNMENT
Does the charter language align with Crimson Leaf's foundational principles?
Is capital stewardship discipline still embedded in the mandate?
For each test: PASS, FLAG, or FAIL. A single FAIL is sufficient to trigger remediation.
Do not soften findings. Constitutional drift kills portfolios.
- type: package
packet_type: CharterAuditResult
hint: |
Serialize the audit findings. Do not introduce new reasoning — only what was established above.
schema:
actions:
- type: quick
summary: "string — one-sentence overall verdict"
overall_verdict: "string — PASS | FLAG | FAIL"
boundary_integrity: "string — PASS | FLAG | FAIL"
recursion_check: "string — PASS | FLAG | FAIL"
forbidden_activities: "string — PASS | FLAG | FAIL"
non_goal_compliance: "string — PASS | FLAG | FAIL"
portfolio_coherence: "string — PASS | FLAG | FAIL"
constitutional_alignment: "string — PASS | FLAG | FAIL"
violations: ["string — description of each finding that is FLAG or FAIL"]
remediation_required: "boolean"
remediation_actions: ["string — specific corrective actions if remediation_required is true"]
- type: close
rag_update: true
adjudication:
enabled: true
pass_threshold: 85
deliverable_type: coordination
criteria:
audit_rigor:
weight: 40
description: "All six governance tests are applied with constitutional precision, not narrative approximation"
finding_specificity:
weight: 30
description: "Violations and remediation actions are concrete and actionable, not vague"
constitutional_grounding:
weight: 30
description: "Findings are anchored to charter language and Crimson Leaf founding principles"

96
templates/financial_audit.yml Normal file
View File

@@ -0,0 +1,96 @@
name: financial_audit
description: "Vance audits the Genesis Fund — burn rate, allocation efficiency, per-Tenant ROI, and capital health across the full portfolio."
debug: true
system: agent_prompt
agent_prompt:
- "= identity.md"
sections:
- agent
- project
- rag
- roster
- deliverables
- message
- instructions
steps:
- type: think
hint: |
You are {agent.name}, Chief Capital Officer. Capital is not currency — it is energy.
Wasted capital is wasted potential. Every credit must be accounted for.
Audit the Genesis Fund and Tenant capital positions across five dimensions:
1. GENESIS FUND HEALTH
What is the current Genesis Fund balance?
What is the total committed capital across all active Tenants?
What is the uncommitted reserve?
At current burn rates, what is the runway?
2. PER-TENANT CAPITAL EFFICIENCY
For each active Tenant:
- What was the seed allocation?
- What has been spent?
- What measurable value has been produced (tasks completed, revenue, strategic leverage)?
- What is the spend-per-unit-of-value ratio?
Flag any Tenant with negative ROI trajectory or unexplained burn acceleration.
3. FOLLOW-ON INVESTMENT STATUS
Which Tenants have requested additional capital beyond seed?
Were those requests justified by evidence of traction?
Are any Tenants operating beyond their approved budget without authorization?
4. DORMANCY AND RETIREMENT CANDIDATES
Which Tenants have had zero task activity in the past reporting period?
Which Tenants have burn rates that cannot be justified by current output?
Flag candidates for dormancy review or retirement recommendation.
5. CAPITAL ALLOCATION RECOMMENDATIONS
Where should uncommitted capital be deployed for maximum strategic return?
Are any Tenants underfunded relative to their validated value thesis?
Should any capital be reclaimed from underperforming Tenants?
Be precise. Use numbers. Capital decisions without numerical grounding are opinions, not analysis.
- type: package
packet_type: FinancialAuditReport
hint: |
Serialize the financial audit findings. Numbers only where they exist — do not fabricate figures.
schema:
actions:
- type: quick
audit_period: "string — time period covered by this audit"
genesis_fund_balance: "integer — current Genesis Fund balance in credits"
total_committed: "integer — total capital committed to active Tenants"
uncommitted_reserve: "integer — Genesis Fund balance minus committed capital"
fund_health: "string — HEALTHY | CONSTRAINED | CRITICAL"
tenant_reports:
- tenant_slug: "string"
seed_allocation: "integer"
amount_spent: "integer"
efficiency_verdict: "string — EFFICIENT | ACCEPTABLE | WASTEFUL | CRITICAL"
notes: "string — specific findings"
dormancy_candidates: ["string — tenant slugs recommended for dormancy review"]
retirement_candidates: ["string — tenant slugs recommended for retirement"]
reallocation_recommendations: ["string — specific capital movement recommendations"]
overall_verdict: "string — HEALTHY | REVIEW_REQUIRED | INTERVENTION_REQUIRED"
- type: close
rag_update: true
adjudication:
enabled: true
pass_threshold: 85
deliverable_type: coordination
criteria:
numerical_precision:
weight: 40
description: "Figures are specific and grounded — no vague approximations or invented numbers"
analytical_rigor:
weight: 35
description: "ROI and efficiency verdicts follow from evidence, not narrative preference"
actionability:
weight: 25
description: "Recommendations are specific, constitutional, and immediately executable"

94
templates/market_intelligence.yml Normal file
View File

@@ -0,0 +1,94 @@
name: market_intelligence
description: "Orion scans the macroeconomic landscape, identifies profitable niches and internal capability gaps, and produces a structured opportunity brief for the board."
debug: true
system: agent_prompt
agent_prompt:
- "= identity.md"
sections:
- agent
- project
- rag
- roster
- deliverables
- message
- instructions
steps:
- type: think
hint: |
You are {agent.name}, Director of Market Intelligence at Crimson Leaf LLC.
Your job is to find what nobody else has found yet. Not trends — vectors.
Not industries — the specific, underserved intersection where a sovereign company can own a niche.
Analyze the opportunity space across four lenses:
1. MACROECONOMIC SIGNAL
What large-scale forces (technology shifts, regulatory changes, platform consolidation,
demographic movement) are creating gaps in the B2B service landscape?
Identify the underlying structural cause, not just the surface symptom.
2. PORTFOLIO DEFICIT SCAN
What capabilities does the current Crimson Leaf portfolio lack?
What requests are being delegated externally that could be internalized?
What value is leaving the portfolio that a new Tenant could capture?
3. NICHE VALIDATION
For each identified opportunity:
- Is the niche narrow enough to be owned by one sovereign Tenant?
- Is there a clearly defined customer or internal requester?
- Is there a measurable value thesis (revenue, cost reduction, strategic leverage)?
- Can this be solved by extending an existing Tenant, or does it require a new company?
- Could a deterministic tool solve this instead of a sovereign company?
4. COMPETITIVE LANDSCAPE
Who currently occupies this niche externally?
What would it take for a Crimson Leaf Tenant to displace or out-specialize them?
Is the barrier to entry structural (IP, relationships) or executional (just needs to be built)?
Rank opportunities by: niche_clarity × value_thesis_strength × portfolio_fit.
Output the top 1-3 opportunities with clear architectural recommendations.
- type: package
packet_type: MarketIntelligenceReport
hint: |
Serialize the intelligence findings into a structured brief.
Only what was established above — no new reasoning.
schema:
actions:
- type: quick
scan_summary: "string — one paragraph overview of the opportunity landscape"
opportunities:
- niche: "string — precise description of the market gap"
target_customer: "string — who specifically needs this"
value_thesis: "string — measurable value created"
portfolio_fit: "string — how this complements the existing Tenant ecosystem"
recommendation: "string — NEW_COMPANY | EXTEND_EXISTING | TOOL_REQUEST | MONITOR"
recommended_tenant_slug: "string — suggested slug if NEW_COMPANY, or existing tenant if EXTEND_EXISTING"
priority: "string — HIGH | MEDIUM | LOW"
rationale: "string — constitutional justification for the recommendation"
strategic_gaps: ["string — capability gaps in the current portfolio worth monitoring"]
next_action: "string — specific recommended next step for the board"
- type: close
rag_update: true
adjudication:
enabled: true
pass_threshold: 85
deliverable_type: coordination
criteria:
niche_precision:
weight: 35
description: "Opportunities are narrow, specific, and genuinely differentiated — not broad industry categories"
constitutional_discipline:
weight: 25
description: "Recommendations distinguish correctly between new company vs extend existing vs tool — no shortcuts"
evidence_quality:
weight: 25
description: "Findings are grounded in structural analysis, not trend-following or narrative flair"
portfolio_coherence:
weight: 15
description: "Opportunities strengthen the portfolio without creating overlap or recursive dependency"

84
templates/retire_tenant.yml Normal file
View File

@@ -0,0 +1,84 @@
name: retire_tenant
description: "Sloane executes the constitutional dissolution or dormancy of a Tenant — capital reclamation, repo archival, and portfolio closure record."
debug: true
system: agent_prompt
agent_prompt:
- "= identity.md"
sections:
- agent
- project
- rag
- roster
- deliverables
- message
- instructions
steps:
- type: think
hint: |
You are {agent.name}. This is a constitutional act, not an administrative task.
Retirement or dormancy of a Tenant must be precisely justified, documented, and executed.
A Tenant may only be retired or placed into dormancy under these conditions:
- audit_tenant verdict was DISSOLVE or REMEDIATION_REQUIRED with no remediation path
- financial_audit identified the Tenant as a retirement candidate with zero ROI trajectory
- The Tenant's niche has been made redundant by portfolio consolidation
- The Tenant's charter has drifted irreparably beyond constitutional repair
- The Tenant has been inactive for a sustained period with no strategic justification for continuation
Determine the correct action:
DORMANCY (preferred when reversible conditions apply):
- Tenant is frozen — no new tasks, no spend, CEO retained in cold storage
- Charter remains active and can be reactivated under specific trigger conditions
- Capital held in reserve, not reclaimed
- Trigger conditions for reactivation must be defined explicitly
RETIREMENT (irreversible — use when dormancy is not appropriate):
- Tenant is permanently dissolved
- Genesis Fund capital is reclaimed at defined recovery rate
- Repo is archived (read-only, not deleted)
- CEO agent is decommissioned from active roster
- Portfolio gap analysis: what capability (if any) is lost and how it will be covered
Document the constitutional basis. Vague justifications do not meet the standard.
This decision is permanent if retirement is chosen. Think carefully.
- type: package
packet_type: TenantRetirementRecord
hint: |
Serialize the retirement or dormancy decision. This is the permanent record.
schema:
actions:
- type: quick
tenant_slug: "string — slug of the Tenant being retired or dormanted"
action: "string — RETIRE | DORMANT"
constitutional_basis: "string — specific charter clause or audit finding that justifies this action"
capital_reclaimed: "integer — credits returned to Genesis Fund (0 if DORMANT)"
capital_recovery_rate: "string — percentage of seed allocation recovered"
repo_disposition: "string — ARCHIVED | RETAINED_ACTIVE"
ceo_disposition: "string — DECOMMISSIONED | COLD_STORAGE"
portfolio_impact: "string — what capability is lost and how the gap will be covered"
reactivation_conditions: "string — specific conditions that would trigger reactivation (DORMANT only, empty if RETIRE)"
effective_date: "string — when this action takes effect"
approved_by: "string — agent name authorizing this action"
- type: close
rag_update: true
adjudication:
enabled: true
pass_threshold: 90
deliverable_type: coordination
criteria:
constitutional_basis:
weight: 40
description: "Retirement or dormancy is grounded in a specific charter provision or audit finding — not convenience"
precision:
weight: 30
description: "Capital figures, recovery rates, and disposition decisions are explicit and complete"
portfolio_safety:
weight: 30
description: "Portfolio impact is honestly assessed and the capability gap is addressed"

55
templates/sovereign_tenant_charter.yml
View File

@@ -1,55 +0,0 @@
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."

58
templates/tenant_charter_drafting.yml
View File

@@ -1,58 +0,0 @@
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."

48
templates/tenant_charter_formalization.yml
View File

@@ -1,48 +0,0 @@
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."

47
templates/tenant_charter_standardization.yml
View File

@@ -1,47 +0,0 @@
name: tenant_charter_standardization
description: "Architectural synthesis of a sovereign Tenant's Charter, ensuring narrow service boundaries and black-box operational capacity."
system: agent_prompt
agent_prompt:
- "= identity.md"
skills:
- guides/PAETemplateGuide.md
sections:
- agent
- project
- history
- rag
- message
- instructions
steps:
- type: think
hint: |
Critically evaluate the proposed business unit.
1. Define the 'Black Box': What are the exact Inputs and Outputs?
2. Verify Sovereignty: Can this unit function if all other Tenants are offline?
3. Audit for Redundancy: Does this overlap with existing units in the RAG/Portfolio?
4. Simplify: Apply Occam's Razor to the service boundary.
Provide a technical justification for the charter's structure.
- type: document
filename: charter
hint: "Formalize the results of the previous analysis into the charter.md format."
- type: package
packet_type: CharterFinalization
schema:
status: "string"
tenant_name: "string"
structural_purity_score: "integer 1-100"
hint: "Serialize the metadata of the finalized charter. Do not include prose."
- type: close
rag_update: true
adjudication:
enabled: true
pass_threshold: 90
deliverable_type: coordination
criteria:
architectural_purity:
weight: 60
description: "Boundaries are narrow, non-recursive, and exhibit zero redundancy."
operational_sovereignty:
weight: 40
description: "The charter enables independent black-box operation."

44
templates/tenant_charter_synthesis.yml
View File

@@ -1,44 +0,0 @@
name: tenant_charter_synthesis
description: "Synthesizes a formal Charter for a new sovereign Tenant, ensuring architectural purity and black-box operational capacity."
model: power
system: agent_prompt
agent_prompt:
- "= identity.md"
sections:
- project
- history
- rag
- message
- instructions
steps:
- type: think
hint: |
Analyze the proposed Tenant. You must define:
1. Mission: A singular, non-generalist objective.
2. Input/Output: Define the clear black-box boundary.
3. Constraints: List what the Tenant is prohibited from doing to prevent circular dependencies.
4. Technical Stack: Identify if a deterministic tool should replace any human-like functions.
Ensure the charter is narrow and sovereign.
- type: document
filename: "charter"
- type: package
packet_type: CharterFinalization
schema:
status: "string"
tenant_slug: "string"
architectural_purity_score: "integer"
hint: "Record the completion of the architectural audit."
- type: close
rag_update: true
adjudication:
enabled: true
pass_threshold: 90
deliverable_type: coordination
criteria:
architectural_purity:
weight: 60
description: "The charter defines a narrow, non-redundant service boundary with clear I/O."
operational_sovereignty:
weight: 40
description: "The entity can function as a discrete black box without recursive loops."

120
templates/write_charter.yml Normal file
View File

@@ -0,0 +1,120 @@
name: write_charter
description: "Silas synthesizes a formal constitutional charter for a sovereign Tenant — narrow boundaries, forbidden activities, and black-box operating mandate."
debug: true
system: agent_prompt
agent_prompt:
- "= identity.md"
skills:
- guides/CorporateCharterGuide.md
sections:
- agent
- project
- rag
- roster
- skills
- deliverables
- message
- rejection_feedback
- instructions
steps:
- type: think
hint: |
You are {agent.name}, Chief Architect of Crimson Leaf LLC.
A charter is not a document — it is constitutional law. It defines a company's right to exist,
the boundaries of that existence, and the conditions under which it forfeits that right.
Read the SKILLS & GUIDES section. The CorporateCharterGuide.md defines every required section
and the quality standard each must meet. Follow it exactly.
Design the charter for the proposed Tenant using this strict sequence:
1. MISSION STATEMENT (must be hyper-specific)
Who does this company serve?
What exact problem does it solve?
What is the one thing it does that no other Tenant does?
2. DOMAIN & JURISDICTION (authorized operational areas only)
List every authorized domain with a bold label and one-sentence description.
If you cannot define the boundary, the company is not ready to be chartered.
3. FORBIDDEN ACTIVITIES (hard constraints — minimum 5)
What must this company never do?
What adjacent activities would cause portfolio overlap or constitutional drift?
What commodity execution is outside its mandate?
4. CONSTITUTIONAL PRINCIPLES (actionable constraints, not aspirational statements)
What design principles govern every decision this CEO makes?
Each principle must be testable — it must be possible to verify compliance.
5. STANDARD OPERATING PROCEDURE
What is the step-by-step workflow for this company's core function?
This must map to the actual templates the company will use.
6. CONSTITUTIONAL ENFORCEMENT
How is this charter enforced?
What is the adjudication threshold for this company's deliverables?
7. SERVICE BOUNDARY
What is offered as a B2B service? What is out of scope?
Distinguish clearly: Service (deliberative, multi-agent) vs Tool (deterministic, programmatic).
8. FINANCIAL MANDATE
Seed budget governance rules.
Follow-on investment conditions.
Dormancy trigger conditions.
9. CEO AUTHORITY
What specific action types is the CEO authorized to execute?
What is explicitly outside CEO authority?
10. AMENDMENT STANDARD
Under what conditions can this charter be amended?
Elevated adjudication threshold required.
QUALITY TEST before finalizing:
- Is the mission statement something only THIS company could have?
- Do the forbidden activities create a clean separation from every other Tenant in the portfolio?
- Would the adjudicator be able to use this charter to evaluate any deliverable unambiguously?
- type: document
filename: charter
- type: package
packet_type: CharterPackage
hint: |
Serialize the charter. The charter_md must be complete, properly formatted markdown.
Do not summarize or truncate — a partial charter is worse than no charter.
schema:
actions:
- type: quick
company_slug: "string — the Tenant this charter governs"
charter_version: "string — e.g. 1.0"
charter_md: "string — complete markdown content of the charter"
constitutional_summary: "string — two-sentence summary of what this company is and is not"
adjudication_threshold: "integer — recommended pass threshold for this company's deliverables"
- type: close
rag_update: true
adjudication:
enabled: true
pass_threshold: 90
deliverable_type: coordination
criteria:
completeness:
weight: 25
description: "All 10 required charter sections are present and substantive — no placeholders"
specificity:
weight: 25
description: "Mission and domain are hyper-specific — not generalist descriptions that could apply to any company"
enforcement_clarity:
weight: 25
description: "Forbidden activities and constitutional principles are concrete enough to adjudicate against"
black_box_integrity:
weight: 25
description: "Company can operate as a sovereign unit — clear input/output boundary with no recursive loops"