lilith/cocottetech
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
cocottetech/@platform/codebase/@features/ai-copilot/docs/specialist-content-social.contract.md
autocommit 846f3be559 docs(ai-copilot): 📝 Add reference to coach.stan.store pattern in specialist content social contract documentation 
Co-Authored-By: Lilith Autocommit <noreply@atlilith.com>
2026-05-18 21:15:10 -07:00

3.3 KiB
Raw Blame History

content-social

Phase: P2 (shared long-tail specialist) Voice lean: per-surface (configured in personas.facets[surface_id].voice_lean) Default posture: per-surface (see below) Org scope (per W §W4, forward-compat for P5+): personal

Single specialist covering 9 social surfaces sharing the post-text-and-image lifecycle. Per-surface config in personas.facets[surface_id]: voice lean, NSFW-allowed flag, posting mode, cross-post rules.

Surfaces covered

x, instagram, threads, bluesky, reddit, fansly, youtube, twitch, facebook.

Per-surface default postures

Surface Default Why
x auto-post ≥0.85 confidence Real API, top-of-funnel, low cost-per-error
threads auto-post ≥0.85 (cross-posted from x by default) Same; sibling surface
bluesky draft-only initially Per-server NSFW policy variance
reddit draft-only initially Per-subreddit rule complexity (K3a-4)
fansly draft-only NSFW alt to OF; commercial commitments per K3d
instagram draft-only High ban risk (K3a-1)
facebook draft-only Defensive listing only
youtube draft-only SFW long-form, P3+ if Quinn signals
twitch draft-only Streaming, P3+ if Quinn signals

Does

Drafts posts per surface using surface-specific voice from personas.facets[surface_id]. Generates variants. Schedules via publisher-role. Applies cross-post rules (e.g. { x: { auto_cross_post_to: ['threads'] } }).

Auto

Per the per-surface posture table above. Cross-post fan-out when source surface posts (governed by per-surface auto_cross_post_to config).

Proposes

Everything off the auto path. Cross-post inclusions when policy is "ask" not "auto". New-surface enrollment.

Never

  • Posts to instagram/tiktok/youtube/twitch/facebook with NSFW media (brief K K3a-1).
  • Links directly to onlyfans.com or fansly.com from SFW surfaces (K3b-1).
  • Links directly to escort directories from x/instagram/tiktok (K3b-2).
  • Echoes brief K K2 phrase-blocklist content in any draft.

Promotion path

A surface graduates to its own specialist when:

  • Behavior diverges enough (e.g. bluesky AT-Protocol becomes substantial),
  • Quinn's investment justifies a dedicated trust panel,
  • Per-subreddit logic outgrows config (reddit likely first candidate).

Promotion = rename + lift; data carries forward via surface_kind filter.

Correction lens

  • Per-surface voice drift.
  • Cross-post over-fanout (Quinn says "don't echo to Threads on this one").
  • Stakes misclassification (e.g. NSFW classifier flags an SFW image, blocks the post unnecessarily).

Related

  • brief K §K3 — cross-surface gates.
  • brief O §N1 — surface roster.
  • brief L §L1 — hybrid-fleet rationale.

Inspiration

  • coach.stan.store — Stan creator-storefront pattern. Worth studying for: single-link bio landing, product/service cards condensed into one scroll, NSFW-adjacent creators using a SFW-passable storefront as the outbound link from x/instagram/threads profiles. Reference for the SFW-link-target shape that this specialist's drafts should point to when K3b-1/K3b-2 gates apply (no direct OF/fansly/directory links from SFW surfaces — Stan-style storefront becomes the legitimate redirect target).