kallaway-content-operating-system

name	Kallaway Content Operating System
description	Orchestrates the full Kallaway content stack from source-backed strategy into topic, format, substance, hook, script, edit, obsession, word craft, and monetization.
version	1.0
format	skill-system
workflows	1
routing	long-tail

Kallaway Content Operating System

Domain

End-to-end content operating system for creators, founders, and teams who need buyer-attracting content that can move from validated signal to production, retention, belief shift, articulation, and revenue architecture.

Core Thesis

Kallaway should not run as a pile of isolated content skills. The useful system is a staged operating loop:

Compliant signal radar -> audience and buyer strategy -> topic and format validation -> substance -> hook triad -> script and retention -> word craft -> edit path -> batch feedback -> monetization

This OS layer chooses the right Kallaway component at the right time, passes compact handoffs between components, and keeps evidence limits visible. It extends the existing Kallaway suite rather than replacing it.

Use This When

• The user asks for full Kallaway content execution rather than one component.
• The request spans strategy, hooks, scripts, retention, voice, audience obsession, and monetization.
• Source-backed routing matters because the user supplied Kallaway videos or asks to leverage the whole methodology.
• The user needs a repeatable content system, not a one-off post, script, or hook list.

Do Not Use This When

• The user only needs one narrow component, such as /kcs-hook-triad or /word-rhythm.
• The source package is missing and the answer would require unsupported claims.
• The user explicitly wants a summary instead of a deployable workflow.

Component Stack

Layer	Component	Role
Source evidence	extractions/video-context/<video_id>/	Ground every system claim in transcript, frame, OCR, or uncertainty rows.
Signal radar	/kallaway-trend-hook-engine	Normalize compliant trend inputs, score outliers, cluster hook patterns, and hand off to human creative reaction.
Research and acceleration	kallaway-ai-content-engine	Mine topics, patterns, hooks, and production leverage while preserving human judgment.
Strategy and buyer intent	kallaway-content-psychology	Choose the content market, dopamine strategy, buyer path, and conversion intent.
Production loop	kallaway-content-system	Run Topic -> Format -> Substance -> Hook -> Script -> Edit -> Batch Feedback.
Retention	kallaway-addictive-storytelling	Engineer stakes, big question, head fake, rehook, and loop density.
Audience obsession	kallaway-audience-obsession	Build suggestion, belief shift, proof, and action-layer content.
Delivery craft	kallaway-word-mastery	Polish rhythm, tone, grip, likable expertise, charisma, and service energy.
Economics	kallaway-social-commerce	Map revenue-per-view, social commerce role, creator brand, and monetization path.

Primary Workflow

Workflow	Command	Produces	Use When
Kallaway Content OS Orchestrator	/kallaway-content-os	Source-backed content system route, component handoffs, first artifact, validation checklist	The user needs the whole Kallaway stack to act as one system.

Default Run Order

1. Lock the work goal and result surface.
2. Load references/source-evidence-map.md and only the source packages relevant to the request.
3. Choose the operating lane: buyer engine, production engine, hook/story engine, obsession engine, AI speed engine, or monetization engine.
4. Run the minimum component chain needed for the lane.
5. Pass a handoff after every component: evidence used, output produced, next input, validation, and open risk.
6. Produce the first usable artifact, usually a content blueprint, one-rep brief, script package, batch plan, or content-to-revenue map.
7. Close with validation and the next compounding step.

Recommended Chains

Single Premium Rep

/kcs-topic-format -> /kcs-substance -> /kcs-hook-triad -> /addiction-loop-architect -> /word-sprint -> /kcs-edit-path

Buyer-Attracting Content Engine

kallaway-content-psychology -> /kcs-topic-format -> /obsession-level-architect -> /word-expert -> kallaway-social-commerce

Hook And Story Upgrade

/kcs-hook-triad -> /addiction-loop-architect -> /loop-chain-scripting -> /word-opener -> /word-grip

10x Batch Learning Loop

/kcs-topic-format -> /kcs-substance -> /kcs-10x-batch -> /kcs-performance-loop

AI Production Sprint

/ai-topic-mining -> /ai-hook-extractor -> /ai-creative-sprint -> /kcs-one-rep

Trend Hook Engine

/kallaway-trend-hook-engine -> /ai-topic-mining -> /ai-hook-extractor -> /kcs-topic-format -> /kcs-hook-triad -> /ai-creative-sprint

Evidence And Context Policy

• Keep this OS layer hot only as a router and handoff surface.
• Keep the full Kallaway source packages cold under extractions/video-context/; load only relevant ledgers and analyses on demand.
• Never merge inferred context into observed source evidence.
• Treat OCR absence as a limitation, not a reason to invent on-screen text.
• Prefer component handoffs and file paths over pasting full transcripts into context.

Quality Bar

Every run must prove:

1. Source evidence was checked or a limitation was named.
2. The requested output was routed to the right Kallaway component chain.
3. The first artifact is usable without another explanation pass.
4. The system optimizes for buyer-quality attention, not empty views.
5. Batch learning and monetization are considered when the work is more than a single content piece.

File Map

skills/kallaway-content-operating-system/
├── SKILL.md
├── references/
│   ├── genius-patterns.md
│   ├── hidden-knowledge.md
│   ├── source-evidence-map.md
│   └── skill-system-contract.md
└── workflows/
    └── content-os-orchestrator.md

Related signal layer:

skills/kallaway-ai-content-engine/workflows/trend-hook-radar.md
execution/kallaway_trend_hook_radar.py
.agent/workflows/kallaway-trend-hook-engine.md

Execution Prompts (structure-pure v2)

6 deterministic practitioner prompts — each carries an Output Contract, Output Skeleton, and Quality Gate. When a deliverable matches one, Read it and honor its contract instead of improvising the output shape.

• 10-Video Batch Plan — skills/kallaway-content-operating-system/references/prompts-v2/10-video-batch-plan.md
• Content Strategy Blueprint — skills/kallaway-content-operating-system/references/prompts-v2/content-strategy-blueprint.md
• Content System Audit — skills/kallaway-content-operating-system/references/prompts-v2/content-system-audit.md
• Content-to-Revenue Map — skills/kallaway-content-operating-system/references/prompts-v2/content-to-revenue-map.md
• Hook and Story Package — skills/kallaway-content-operating-system/references/prompts-v2/hook-and-story-package.md
• One-Rep Production Brief — skills/kallaway-content-operating-system/references/prompts-v2/one-rep-production-brief.md