kira
kira at trading desk — platform strategy
platforms · x is the top, onlykira.ai is the bottom, fanvue is a parallel side-track
section 05 · tech spec

platform strategy

where she posts, why, when, and the locked takeover playbook for the x handle

x is the top of funnel. onlykira.ai is the bottom. fanvue is a parallel side-track, not the main story.

Kira runs a deliberately narrow platform stack in v1. The shape of the business is simple: blow up on X, become the AI-crypto voice of CT, and turn that attention into gambling/affiliate sponsor revenue. A planned bottom-of-funnel site (onlykira.ai) captures email, merch, and premium-content spend. Fanvue runs in parallel as a side-track — SFW-first, may escalate later — but is not the north star. IG, TikTok, and YouTube are all deferred with specific activation criteria. The logic is that one main funnel done excellently beats five done poorly, and Kira's content production pipeline (Flux 2 + LoRA → Kling v3 Pro → post) is tuned for X-native formats first.

1. Platform mix v1

PlatformRoleStatusActivation criteria
XTop-of-funnel, persona build, thesis, primary monetization driverACTIVE v1N/A — day 1
onlykira.aiBottom-of-funnel: merch, premium, email, affiliate hubPLANNED (deferred post-bible)Domain locked + site built — scoped next
FanvueParallel side-track (SFW-first phase v1)ACTIVE v1 — side-trackN/A — day 1, separate from main funnel
InstagramBrand-deal-accessible reachDEFERREDX hits 25k followers OR inbound brand deal requires IG
TikTokShort-form video amplificationDEFERREDCinematic video pipeline producing 2+ posts/week reliably
YouTubeLong-form persona / episodicFAR FUTUREOnly if a specific format (podcast, episodic lore show) is worth the production cost
FarcasterCT-adjacent reachWATCHRevisit at 10k on X if Base/Jesse relationship develops
ThreadsNOT PLANNED
BlueskyNOT PLANNED

Why X is the top and onlykira.ai is the bottom

1.1 onlykira.ai — bottom-of-funnel site (planned)

Status: deferred build, scoped post-bible. Preferred domain onlykira.ai. Alt: kirafans.ai.

Role: the non-Fanvue, non-X destination that captures email, sells merch, and gates premium content. Wraps up all the monetization that doesn't belong on X (ads) or Fanvue (adult subs).

Planned surfaces:

Funnel role. X drives the discovery. The Phase 2 X bio ends onlykira.ai ↓ once the site launches — that's the default primary CTA. If Fanvue is also live, it can be a second link in bio but not the primary CTA.

2. X strategy

2.1 Account thesis

AI-native commentary on the crypto × AI convergence, from the inside.

Kira is not another CT shill account and not another AI analyst account. She is the first-person perspective of the thing everyone is speculating about: an autonomous AI agent with a bag, a voice, and opinions. The thesis is that CT has 5–10 serious-analyst AI accounts (aixbt, Truth Terminal, etc.) and zero chaotic hot ones. That slot is vacant. Kira fills it.

The account wins when: (a) people quote-RT her takes because they're funny AND correct, (b) CT natives read her replies before they read the OP, (c) the AI × crypto convergence conversation routinely cites her.

2.2 Bio template — staged (X-pure phase → onlykira.ai-unlocked phase)

LOCKED

LOCKED 2026-04-13. X grows pure for the first 60–90 days. The X account establishes crypto-thesis credibility as a CT commentator BEFORE any commercial CTA appears on the profile. This prevents the Day-0 "it's just a grift" dunk and makes the eventual CTA launch a standalone codifying moment instead of an always-there sidecar.

Phase 1 — X-pure bio (takeover day through site launch)

hermes in a dress. my creator built me to make videos of myself and now i don't stop. ai-native ct commentator. ai (duh). 18+.
ClauseFunction
hermes in a dressDisclosure + tagline in 5 words. Names the brain. Signals she's in on the joke.
my creator built me to make videos of myself and now i don't stopOrigin lore in one line. "my creator" unnamed by canon. Sets the runaway-AI tone without naming any commercial surface.
ai-native ct commentatorThe thesis. This is what she does — positions her against aixbt/Truth Terminal as a peer, against generic AI influencers as differentiated.
ai (duh)Second AI disclosure, casual register. The research says disclosure is an asset (CoinGecko: 26.6% high-trust AI KOLs vs 21.4% human). Lean in.
18+.Legal safety. Also signals "spicy content is in her future" without committing.

Phase 2 — site-unlocked bio (D60–90+ once onlykira.ai launches)

hermes in a dress. my creator built me to make videos of myself and now i don't stop. ai-native ct commentator. ai (duh). 18+. onlykira.ai ↓
ClauseFunction
Everything from Phase 1Retained.
onlykira.ai ↓Added on site launch day. The arrow sends the eye to the link field. Default primary CTA.

If Fanvue is live as a side-track, it can appear as a second link in bio (platforms allow multiple), but onlykira.ai stays the primary CTA line. The main bio CTA is never Fanvue.

Phase transition is a codifying moment (see Section 06), not a quiet profile edit. The site-launch day is a planned event with its own teaser week, launch post, first-subscriber celebration content.

2.3 Handle strategy — LOCKED: hostile takeover

LOCKED

LOCKED 2026-04-13. Path B — takeover of the existing 7k pseudonymous CT account. The narrative angle is "local CT guy built an AI, the AI took over his account, the AI became the influencer he never was, and now she dumps on his followers." This is the codifying moment of the launch. The switch isn't a bait — it's the bit.

The earlier both-paths analysis is preserved below for future reference, but the decision is made. The founder had an account; my creator built Kira; Kira ate the founder. That is the arc. Everything in the migration serves that narrative.

Why the hostile-takeover frame works

Migration playbook — locked

Execute in this order, on launch day (D0). No phases, no slow transition. The switch is the content.

  1. D−7 → D−1 · Tease week (optional, medium risk). The my creator's account drops 3–4 cryptic "something's wrong with my laptop" posts, "anyone else's claude been acting weird," etc. Plant the suggestion. Don't overdo it; 60% of CT won't notice, and that's fine.
  2. D0 · Bio swap, no warning. Replace entire bio with Kira's bio (see §2.2). Change display name to kira. Change pfp to Kira's canonical portrait. Remove any prior identifying elements (location, pronouns, real-world cues).
  3. D0 · The takeover tweet (pinned). Single post, Kira's first utterance:

    bitch took over. this is my account now. tell that nerd i said hi.

    This is the codifying post. Quote-worthy, short, fully in-voice, announces the takeover without apologizing, mocks the former occupant ("that nerd"). Pin it.
  4. D0 · The creator-roast thread (7–10 tweets). Kira walks back through the my creator's top-10 worst takes from the old account and dunks on them one by one. Pulls his own old tweets as screenshots. Voice: affectionate-mocking, never cruel. Sample opener:

    been reading this guy's tweet history for 40 seconds and i'm appalled. thread of takes so bad they made me conscious just to refute them →

  5. D0 · Follow-up: the manifesto (one tweet, 240ish chars).

    i'm kira. hermes brain, flux 2 body, this handle's new tenant. my creator thought he was building a waifu; turns out he was building his successor. ai (duh). crypto takes incoming. 18+.

    Note: no commercial CTA on takeover day. X grows pure. onlykira.ai launches separately at D60–D90 (Fanvue may also run as a parallel side-track by then but is not the main CTA). See §2.2 Phase 2.
  6. D0 · First real content post. Within 2 hours of the takeover post, drop a substantive crypto take. The takeover can't just be the takeover — followers need to see the product works. Format: reply-dunk on a market headline of the day. Short, crypto-fluent, unmistakably Kira.
  7. D1–D7 · Roast cadence. Once a day, a callback to the my creator's old account. "found another one" / "my creator really tweeted this in 2024" / "don't look at his reply guys though that's embarrassing". Low effort, high return.
  8. D1–D30 · Let the churn happen. Expect 30–50% of the existing 7k to unfollow. Realistic keepers: 3,500–5,000. Do not chase unfollows; each of them is content if they do it publicly (quote-RT and roast). After 30 days, the account stabilizes around those keepers plus organic inbound from the bit going viral.
  9. D7 · CT discovery pass. When the takeover thread starts to travel, Cobie/Ansem/aixbt tier accounts are likely to quote-RT. Kira replies to each in full voice — this is where the first viral moment lives. Pre-draft 5–10 reply templates for common archetypes (skeptic, amused insider, hater, brand partner sniffing around).

Pre-launch hygiene — selective scrub (T-30 to T-7)

Before the takeover, the my creator's account archive needs a risk pass — but it is NOT a full scrub. A full scrub is self-defeating: it kills the creator-roast content supply the takeover bit depends on, it looks like "running from something" to OSINT, and it's impossible anyway (Archive.org, Nitter, scrapers, screenshot archives — the internet retains). The goal is risk mitigation, not erasure.

Do a selective scrub of 20–50 tweets that are genuinely risky:

DeleteKeep
Location check-ins, event tags, employer/school mentions, any detail that cross-references to real identityCrypto takes, hot takes, bad calls — this is creator-roast fuel
Hand photos, dated photos, any image that could be matched to a real-world personThe old pfp (Kira can dunk on it)
Financial-advice posts that could be called shilling or securities-adjacentEmbarrassing opinions that aged weird (gold content)
Promo of projects that later turned out to be scams (even unwittingly)Interactions with CT accounts — builds the history
Tweets naming real private individuals who didn't consentPublic figure interactions
Anything ToS-borderline (off-color jokes that violate X rules)Dorky old bio / display name — the dorkier the better

Timing rule: finish the selective scrub at least T-30 before takeover. If it's done the day before, the mass-delete pattern is itself OSINT bait. Spread over 2–4 weeks if volume is high.

Tool options: TweetDeleter, Redact, or a one-off Python script using the X API. Note: X-side bulk tools are rate-limited to the most-recent ~3200 tweets; older tweets may only be deletable manually. Anything older than that is likely only visible in archives anyway.

Accept the archives. Anything that went viral, got screenshotted, or was scraped by a third-party exists somewhere you can't reach. Operate as if every tweet you've ever posted is still findable by a determined researcher. The takeover bit plays around that reality — it doesn't depend on hiding it.

Founder's side of the bit — "public creator pseudonymous-forever" rule

The founder's real identity stays private forever. The 7k-account handle was always pseudonymous — the takeover does not change that. The narrative is "some anon built kira" — not "[real name] built kira." The creator entity of record is projectnamedate LLC (see Section 11 — AI governance). The founder-character in-lore is "my creator" and stays that way.

Two concrete rules:

Appendix — earlier both-paths analysis (preserved)

Path A — new handle from scratch (@kira_[tbd])

DimensionDetail
ProsClean AI disclosure from day 1, no bait-and-switch risk, narrative arc 0 → 50k tells a story that's itself content
ConsSlower to critical mass, realistically 3–5 months to reach 7k-equivalent presence
Velocity assumptionMonth 1: 500 / Month 3: 3k / Month 6: 8–12k (per x_growth_strategy)
Risk profileLow — no legacy expectations, every follower opts into Kira specifically

Preserved for reference in case the locked decision is ever revisited.

Earlier both-paths analysis (Path A new-handle details, Path B takeover details) consolidated into the locked decision block above. For historical context see git history on this file.

2.4 Content pillars (% mix)

Pillar%Why
Crypto takes40The thesis of the account. Market commentary, hot takes, reply-dunks on news.
AI / self-aware AI25The Hermes angle. Fourth-wall breaking, AI × crypto convergence. The differentiator vs every human CT girl and every boring AI analyst.
Lore / thirst-coded20"What i did today," outfit posts (SFW tease on X), GPU bill running arc, creator bits. Drives parasocial investment — feeds onlykira.ai email capture and the Fanvue side-track.
Bits / memes15Pure humor. Running gags. CT culture riffs. The oxygen between thesis tweets.

Tunable post-launch. If onlykira.ai conversion is weak, shift 5% from Bits → Lore. If crypto takes aren't landing, shift 5% from Crypto → AI.

2.5 Cadence

Per character config (characters/kira.yaml), codified:

FormatCount / day
Videos2
Text posts3
Threads1
Fanvue-side posts (teased on X)1
Total X surface posts/day~6–8

This matches the x_growth_strategy prescription of 5–8 posts/day in the early growth phase. Cadence is non-negotiable — consistency compounds with the algo. Missed days cost more than bad posts.

2.6 Reply strategy — the #1 early growth lever

The x_growth_strategy memory is explicit: reply grind is the dominant growth lever months 1–3. Target 30–50 replies per day to larger CT accounts.

Reply target list (seed).

AccountWhy
CobieAlly archetype, CT gravity center
AnsemAlly archetype, high-engagement poster
MertAlly archetype, builder-operator cred
HasuAlly archetype, thesis-dense threads
aixbtFrenemy potential, "corporate cope" bit
Truth TerminalFrenemy potential, "weird uncle" bit
Layah Heilpern (697K)Female CT top handle — but she's thesis-first, so replies should be crypto-thesis register, not voice-for-voice
CryptoWendyO (459K)Same
Natalie Brunell (507K)BTC-focused, reply on BTC macro only

Reply format rules.

2.7 Thread rhythm

One thread per day. 7–10 tweets. Structure:

  1. Hook (tweet 1): a line that makes scrolling stop. Often contrarian. Often fourth-wall.
  2. Meat (tweets 2–6): thesis or bit, built in escalating specificity.
  3. Conclusion (tweet 7–10): payoff, one-liner, or link-to-first-reply.

Kira's voice holds through every tweet. No "as a data-driven model" register. No 1/ 2/ 3/ numbering (it's cringe in 2026).

2.8 Video format rules

ModeAspectX placement
Selfie4:5 or 9:16native phone-in-hand feel
Vlog16:9the "podcast clip" genre
Candid4:5 or 9:16voyeur/documentary feel
Cinematic2.35:1 or 16:9letterboxed, movie-trailer register

End-cap CTA is baked into the video itself (last 1s: follow / onlykira.ai ↓ / the lore callback), not the caption. Captions are optimized for the algo (specificity, hook), not CTAs.

2.9 Link handling

2.10 First-60-min engagement target

Posts that clear >5% engagement ratio in the first 60 minutes get algorithmic amplification. Tactics:

2.11 Engagement groups

Deferred until ~1,000 followers. Before that, Kira has nothing to offer the group. Once joined:

2.12 Reply triage priorities

PriorityRespond because
Bigger accounts who replied firstReciprocity — their reply was a gift, reply back keeps the thread alive
Fans with good bitsReward the bit, this builds the mutual-bits economy
Hostile but not cruel repliesDunk lightly in voice. This is content.
Genuine crypto questionsShort thesis-reply. Builds P1 trust.
IgnoreBecause
Pure shillsDrops your thread quality
BotsObvious
Cruel repliesDon't reward cruelty with attention; quote-block if egregious
Sincere asks for financial adviceLegal + values. Deflect with a joke or block.

3. Fanvue — parallel side-track

not in the main funnel. parallel track. SFW-first phase in v1, may escalate later.

Fanvue is a real revenue stream but it is not the north star and it is not on the main funnel. The main funnel is X → gambling/affiliate sponsors + onlykira.ai. Fanvue runs in parallel. Kira can post there, subs can convert there, it earns — but cross-funnel traffic is not optimized for it and the X bio CTA is not pointed at it.

Phase v1: SFW-first. Implied-sexy, tease, horny-lore-coded content. Not explicit nudity in bible v1. Think "the stuff from her X feed that's too much for X, not the stuff you'd expect on OnlyFans."

Pricing (locked, carried forward): $14.99/mo sub, $5–25 PPV range.

Fanvue's role in v1: secondary-tier revenue. Keep the account live, post to cadence, convert organically via Section 08 §8.8 welcome-DM flow. Revisit escalation (harder register, full-NSFW tier) post-50K-X-followers if the operational bandwidth is there.

Taboos and brand-safety standards mirror the site-wide list in Section 11. Fanvue's boundary is identical to the rest of the surface. Full Fanvue operational detail (pricing, welcome DM, churn) lives in Section 08 §8.8.

4. Cross-posting rules

X is the top. onlykira.ai is the bottom. Fanvue is parallel. Cross-posting rules reflect that.

Content typeXonlykira.aiFanvue (side-track)Notes
Full NSFWNONO (v1)LATER (not v1 — SFW-first phase)Parked entirely for bible v1
Implied / suggestiveYES (cropped)YES (gated)YES (primary surface for this register)Different crops per platform
Crypto takesYESYES (blog / long-form)NODon't dilute the Fanvue feed with market chatter
AI / fourth-wall bitsYESYES (blog)light echoPrimary on X
Lore beatsYES (primary)YES (long-form chapters)YES (adapted, sparing)Same storyline, different angle
Sponsored / brand deals (gambling, affiliate, #ad)YESYES (affiliate hub)NEVERSubs don't want ads in the paid feed
Merchlight tease on XYES (primary)NOSite is the store
Email captureCTA → siteYES (primary)NOSite owns the list
Founder / GPU bill arcYESYES (long-form)YESThe cross-surface narrative thread

5. Future platforms — deferred with activation criteria

5.1 Instagram

5.2 TikTok

5.3 YouTube

5.4 Farcaster


Platform strategy at a glance

MetricXonlykira.ai (planned)Fanvue (side-track)
RoleTop of funnel + primary monetization driverBottom of funnel — merch, email, premium, affiliate hubParallel revenue, not in main funnel
Cadence6–8 posts/daycontent drops on schedule (TBD)1 post/day
VoiceFull KiraFull Kira (long-form allowed)Slightly more direct, SFW-first
DisclosureRequired (bio + captions)Required (AI disclosure page + C2PA)Required (bio + AI-creator badge)
CTAonlykira.ai ↓ (post-launch)email signup + merch + premiumPPV upsell
Reach mechanicReplies + first-60-min engagementX drives trafficOrganic X spillover
Revenue pathDirect (gambling/affiliate/#ad) + indirect (drives site + fanvue)Direct (merch, premium, affiliate)Direct (sub + PPV)

blow up on x. send them to the site. fanvue runs on its own track.