The problem is not “we need another influencer dashboard.” The problem is a named AI persona
(content identity, synthetic character, branded face) with no biometric ground truth. HunterRose
is an AI persona manager on meltuc.tech: create a persona, upload reference images, approve them,
and the app builds a 512-dimensional ArcFace fingerprint (insightface buffalo_l). Canonical embedding
is the L2-normalized mean of approved faces. Storage: Supabase bucket hunterrose-references,
jpg/jpeg/png/webp, 10 MB. Statuses: Incubating / Warming / Active / Paused / Retired. Archive is
soft-delete. Version 0.1.0: CRUD + embeddings live. LoRA train, asset generation, similarity review,
GPU spend, job page are schema only until RUNPOD_API_KEY. This landing
will not fake a GPU studio. Proof: dashboard counts + persona list + upload + approve/reject.
Long-term pipeline is five stages; only 1–2 are implemented. Honesty is the product on this page: do not sell RunPod output you cannot generate.
Not Midjourney, not Runway, not a generated-asset gallery. Five recent personas and status tiles.
CSS mock of a reference row. Approving embeds. Rejecting does not invent a face vector.
B1-03 through B1-08 pending credentials. Do not paste fake LoRA loss curves.
No CSV/JSON export endpoints, no cron in this blueprint. Bulk-delete personas API max 100. Login wall on app/personas.
Will not generate images without RunPod. Will not train LoRA in Flask. Will not store a fake embedding on reject. Public landing lists no faces.
meltuc.tech admin building persona ground truth for later generation. If you need an image factory today, this app is not ready.
If a card says pending, it is pending.
Login for /hunterrose/app. This page is not a gallery of identities.
Open HunterRoseRequires a MelTuc account. Create one free.
AI persona management — create, manage, and version AI personas with reference images. Health stays cheap. If this page disagrees with the signed-in app, trust the app — the product contract and tests enforce that rule.