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

fix: remove Unicode chars from template

Browse Source
This commit is contained in:
Nova_2761
2026-04-09 23:03:05 +00:00
parent 1f2616688f
commit bc0e60ab02
1 changed files with 17 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
templates/market_intelligence.yml
View File

@@ -20,8 +20,8 @@ steps:
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.
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:
@@ -48,29 +48,29 @@ steps:
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.
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.
Only what was established above -- no new reasoning.
schema:
actions:
- type: quick
scan_summary: "string — one paragraph overview of the opportunity landscape"
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"
- 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
@@ -82,10 +82,10 @@ adjudication:
criteria:
niche_precision:
weight: 35
description: "Opportunities are narrow, specific, and genuinely differentiated — not broad industry categories"
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"
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"