What is a content operating system?

A content operating system is a code-based infrastructure for creating, distributing, and compounding content across platforms. Instead of a content calendar or spreadsheet, you build voice rules, platform playbooks, and production pipelines in version-controlled files.

Voice DNA is the foundational layer of the 3-tier system. It encodes your cadence, vocabulary, anti-patterns, and identity markers into files that AI agents read before generating any content. Same voice, every platform, every time.

How do platform playbooks work?

Each platform gets its own playbook that inherits from your Voice DNA. The LinkedIn playbook knows paragraph structure, emoji usage, and CTA patterns. The TikTok playbook knows 16-second structures and hook formats. Same voice, different container.

How does the recursive feedback loop work?

Every published post teaches the system. Performance data feeds back into voice rules. When the anti-slop guide catches a new pattern, it gets added. When a hook style outperforms, it gets documented. The 100th post is easier than the 1st.

Can I build my own Content OS?

Absolutely. The wiki, how-to guides, and method page document the entire system. Start with Voice DNA (who you are), add platform playbooks (how you adapt), then build content ops (how you ship). Everything here is public.

← back to logs

$ cat ~/receipts/{date}.json

Auto-generated build receipt. Every item scanned from git commits, content drafts, finalized posts, and AI token usage. Not a screenshot. Not a mockup. Live data from the codebase.

DAILY TRACKER

D1 pts

Monday, Feb 23, 2026

commits

score

net lines

dirs touched

25.7M

tokens

$0.00

actual cost

$55.43

API equiv

X:1|LIN:1|OPS:1|OTH:1

... = 1 pts

Commits (1)

▸00:00CHOREchore: daily tracker scan 2026-02-22+1

chore: daily tracker scan 2026-02-22

7 files changed +631 -562 net +69

dirs: data/, docs/, website/

This Week

Mon02-231 commits1 ptsD

Tue02-2410 commits279 ptsC

Wed02-2537 commits678 ptsS

Thu02-2613 commits308 ptsB

Fri02-2722 commits470 ptsA

Sat02-2819 commits372 ptsB

Sun03-0124 commits523 ptsA+

Week total: 126 commits2631 pts

Analytics

DEV EQUIVALENT

Net lines:69

Dev-days:0.5

Cost equiv:$250

A mid-level developer writes ~150 lines of production code per day at ~$500/day (fully loaded). Today's 69 net lines represent approximately 0 developer-days of output — what a small team would produce in 0+ week.

COST

Actual cost:$0.00

API equivalent:$55.43

Pricing:max

TOKEN EFFICIENCY

Tokens/pt:25.7M

Tokens/commit:25.7M

Tokens/LOC:371.9K

Context util:100%

TOKEN USAGE

8 exact | 0 est

Sessions:8

Input:31.2K

Output:14.2K

Cache:24.7M / 896.5K

Total:25.7M

Cost:$55.43

BY MODEL

opus25.7M

SESSION LOG

claude-code 18:57 opus $2.89

claude-code 20:52 opus $4.36

claude-code 02:38 opus $9.26

claude-code 00:13 opus $25.49

claude-code 00:02 opus $2.17

claude-code 01:57 opus $2.24

claude-code 20:48 opus $2.33

claude-code 21:40 opus $6.68

1 pts from 1 commits | 69 net lines | $0.00 actual ($55.43 API equiv) | dev equiv: $250

← 2026-02-22 2026-02-24 →

generated 2026-02-24 05:00 | v4 auto-tokens + scoring | built with Cursor + Claude Code

active 13:58 – 19:07 | efficiency: 0.02 pts/s