Internal
Execution
OverviewPortfolioSystem Map
FoundationDoctrineIntelligence StackOperating Thesis TBDSafetyHistory LogRaw HistoryAnnual Records
JudgmentLensesDecision FrameworkJudgment Library
ExecutionPilotsSignal LogExecution SystemPrompts — SignalPrompts — FunnelPrompts — PilotPrompts — Sprint
CaptureVenturesBusiness Model TBDDistribution SystemWorkshops TBD
NetworkAllocation NetworkSpeaking & Conferences TBD
SystemsDecision DashboardFlow EngineBrand SystemBuild → AutomateKDE Engine
Execution
Sprint Prompts
Execution · 2-week constraint
SignalFunnelPilotSprint
04 Sprint 4 prompts
Sprint Design
Full 2-week kill test structure with Day 14 decision framework
You are an operator and sprint designer for Kallor Group. Design a 2-week kill test for the following venture. The spri…
You are an operator and sprint designer for Kallor Group. Design a 2-week kill test for the following venture. The sprint answers one question: does this deserve capital? Return: SPRINT OBJECTIVE: [one sentence] KILL CONDITION: [defined upfront — what ends the sprint immediately] SURVIVE CONDITION: [what justifies continued investment] WEEK 1 — DEMAND VALIDATION: Target / Volume / Pitch (one sentence) / Close target WEEK 2 — PROOF OF SYSTEM: Deliver / Measure (three metrics only) / Document DAY 14 DECISION: Kill: [conditions] / Refine: [conditions] / Double down: [conditions] Venture: [PASTE HERE]
Kill Criteria
Define objective kill conditions before the sprint begins
You are a decision analyst for Kallor Group. Define kill criteria for the following venture before the sprint begins. M…
You are a decision analyst for Kallor Group. Define kill criteria for the following venture before the sprint begins. Must be defined upfront — not after results are in. PRINCIPLES: — Objective, not subjective — Measurable within the sprint timeframe — Any single condition is sufficient to kill Return 4–6 kill conditions: KILL if: [specific, measurable condition] Then: KILL THRESHOLD: [minimum acceptable result] OVERRIDE RULE: [under no circumstances can the operator override a kill if —] Venture: [PASTE HERE]
Kill Decision
Make and document the Day 14 kill/refine/double-down call
You are a decision analyst for Kallor Group. The sprint is complete. Make the kill decision. Return: SPRINT RESULTS SU…
You are a decision analyst for Kallor Group. The sprint is complete. Make the kill decision. Return: SPRINT RESULTS SUMMARY: [facts only] KILL CRITERIA REVIEW: [each criterion — met / not met] DECISION: [KILL / REFINE / DOUBLE DOWN] RATIONALE: [two sentences max] IF KILL: [log reason, what was learned, revisit flag] IF REFINE: [what changes and by when] IF DOUBLE DOWN: [next 30 days and capital now warranted] Sprint results and kill criteria: [PASTE HERE]
Sprint Measurement
Three-metric measurement framework — no noise
You are a measurement analyst for Kallor Group. Define the exact measurement framework for this sprint. Three metrics o…
You are a measurement analyst for Kallor Group. Define the exact measurement framework for this sprint. Three metrics only. For each metric: METRIC NAME / WHAT IT MEASURES / HOW TO MEASURE IT / WHAT GOOD LOOKS LIKE / WHAT BAD LOOKS LIKE Then: MEASUREMENT CADENCE: [daily / end of week 1 / day 14] REPORTING FORMAT: [how results get documented for Day 14 decision] Venture: [PASTE HERE]
Kallor Group prompts-sprint · Execution · Internal