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

D44 pts

Saturday, Mar 28, 2026

commits

score

3,582

net lines

dirs touched

tokens

$0.00

actual cost

$0.00

API equiv

WEB:4|LIN:1

feat: claude daily digest 2026-03-27 +15 · feat: nio.log 2026-03-28 — automated daily post +10 · feat: daily LinkedIn posts 2026-03-28 +15 · ... = 44 pts

Commits (7)

▸00:19INFRAfeat: claude daily digest 2026-03-27+15

feat: claude daily digest 2026-03-27

2 files changed +1325 -0 net +1325

dirs: content/

▸00:20CHOREchore: daily tracker scan 2026-03-27+1

chore: daily tracker scan 2026-03-27

10 files changed +1554 -157 net +1397

dirs: data/, website/

▸08:01SHIPfeat: nio.log 2026-03-28 — automated daily post+10

feat: nio.log 2026-03-28 — automated daily post

1 file changed +53 -0 net +53

dirs: content/

▸08:22CHOREchore: sync Reddit cache — 35 posts (2026-03-28 08:22)+1

chore: sync Reddit cache — 35 posts (2026-03-28 08:22)

1 file changed +32 -16 net +16

dirs: website/

▸09:09INFRAfeat: daily LinkedIn posts 2026-03-28+15

feat: daily LinkedIn posts 2026-03-28

2 files changed +758 -0 net +758

dirs: data/

▸20:22CHOREchore: sync Reddit cache — 37 posts (2026-03-28 20:22)+1

chore: sync Reddit cache — 37 posts (2026-03-28 20:22)

1 file changed +43 -11 net +32

dirs: website/

▸23:05CHOREchore: contentos optimizer - 2 improvements (2026-03-29)+1

chore: contentos optimizer - 2 improvements (2026-03-29)

1 file changed +116 -115 net +1

dirs: website/

This Week

Mon03-2331 commits100 ptsD

Tue03-2431 commits125 ptsD

Wed03-2530 commits93 ptsD

Thu03-2623 commits37 ptsD

Fri03-2716 commits131 ptsD

Sat03-287 commits44 ptsD

Sun03-296 commits43 ptsD

Week total: 144 commits573 pts

Analytics

DEV EQUIVALENT

Net lines:3,582

Dev-days:23.9

Cost equiv:$11,950

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

COST

Actual cost:$0.00

API equivalent:$0.00

Pricing:max

TOKEN EFFICIENCY

Tokens/pt:0

Tokens/commit:0

Tokens/LOC:0

Context util:0%

TOKEN USAGE

0 exact | 0 est

Sessions:0

Input:0

Output:0

Cache:0 / 0

Total:0

Cost:$0.00

BY MODEL

SESSION LOG

44 pts from 7 commits | 3,582 net lines | $0.00 actual ($0.00 API equiv) | dev equiv: $11,950

← 2026-03-27 2026-03-29 →

generated 2026-03-29 04:00 | v4 auto-tokens + scoring | built with Cursor + Claude Code

active 00:20 – 23:58