Validate
AI-assistedAI finds themes in approved founder material.
Drafts content from a founder-owned corpus, gates every publication, and learns only from observed audience response.
User-selected scenario, not an expected outcome.
Current level 3/5. Potential level 4/5 in 1–3 months.
AI finds themes in approved founder material.
AI drafts variants; the founder approves voice and facts.
Every post and reply requires human approval.
AI organizes the content asset and response brief.
The founder owns audience relationships and monetization decisions.
Approval applies to the exact action once. It is not blanket permission.
Approve the exact post, platform, timing, and any reply before publication.
Approve sponsor, affiliate, or endorsement terms and disclosures.
SETUP: Provide only founder-owned or licensed notes, transcripts, examples, and product facts. Define audience, three content pillars, voice constraints, banned claims, disclosure rules, weekly capacity, and a metrics ledger. Do not publish anything automatically. EACH CYCLE: (1) Select one useful idea from the approved corpus. (2) Preserve the founder's actual reasoning and flag every factual or experiential claim for verification. (3) Draft three platform-appropriate versions with a clear lesson, concrete example, and honest next step. (4) Run voice, source, confidentiality, rights, and claim checks. (5) Queue the exact post for human approval; the human chooses whether and where to publish. (6) Draft replies only when asked and require approval for each. (7) Record actual impressions, saves, replies, qualified conversations, and revenue only from platform or human-supplied data. (8) Update topics and format from observed signals, not invented performance. STOP on unverifiable claims, unclear rights, confidentiality risk, unsustainable cadence, or the declared negative-response threshold. ESCALATE legal, reputational, regulated, sponsor, affiliate, and endorsement questions. SETUP 1. Approved corpus 2. Audience and pillars 3. Voice and claims rules 4. Cadence 5. Metrics ledger RECURRING CYCLE 1. Select source idea 2. Draft three variants 3. Fact and rights check 4. Wait for publication approval 5. Record observed response 6. Update queue STATE TRACKING 1. Source item 2. Claim status 3. Draft 4. Platform 5. Approval 6. Published URL supplied by human 7. Observed metrics 8. Next action APPROVAL POINTS 1. Publish — Explicit approval: Approve the exact post, platform, timing, and any reply before publication. 2. Contract — Explicit approval: Approve sponsor, affiliate, or endorsement terms and disclosures. STOP CONDITIONS 1. Unverifiable claim 2. Rights/confidentiality issue 3. Capacity or negative-signal threshold exceeded ESCALATION RULES 1. Escalate legal and reputational claims 2. Escalate sponsor and endorsement disclosures
Projected scenarios never appear here as observed outcomes.
Content loop is complete but has no recorded publishing cycles.
No model test date recorded
Catalog baseline; exact version must be recorded at first test
A founder with real expertise or operating notes but limited publishing capacity. · Turn approved source material into a sustainable, evidence-aware publishing cadence.