AI Savage SOPContent engine method

A working operating manual for turning source packs into fleet skills, UGC tools, RAG docs, and deployable company systems.

Start with the method

Open the UGC pipeline

Source pack discipline

Inventory assets, preserve ownership, keep all heavy media in the correct host, and build only the scoped tracks.

Production wrappers

Wrap existing scripts behind a web UI, keep provider keys server-side, and ship proof artifacts with each deploy.

RAG ready SOPs

Turn every repeatable process into versioned docs that can be indexed into a vector store.

1. Install skills

Copy only SKILL.md-bearing assets into the fleet skill source of truth, sanitize secrets, and keep plugin duplicates deduped.

2. Build tools

Use the AFS Next.js and Supabase shell for live tools, server-side keys, proof pages, and simple operational UI.

3. Document operations

Create SOP docs and a vector store so future agents can search the method instead of guessing from memory.

Delivery Contract

Every AI Savage deliverable needs:

A source path and owner.
A live or local proof surface.
A clear verification level.
An Obsidian vault with a README and MOC.
A Discord progress line when the track changes state.

Host Split

Hetzner handles build, local proof generation, Vercel deploys, and vault creation for T1, T2, T3, and T6. Windows handles Paperclip companies and per-company Discord channels separately.