Launch Control

The Studio Projects route models project publication state, featured media, hero copy, CTA rules, media showcase entries, markdown source attachments, editable Problem and Approach copy, public content cards, Project Notes fields, and section-level switches.

The synthetic KYC prototype is captured into 11 Media Showcase frames, copied as a public click-through prototype, wired to /work/citi-kyc-review-flow, and seeded into project-scoped Virtual Kirk with explicit synthetic-data and publication boundaries.

The Rock This case page now has a Project Notes / Chat panel with signed-session access, projectSlug-scoped Virtual Kirk answers, recent-turn follow-up context, source chips, blocked-topic guardrails, and a monitor-style typed response reveal.

Copy, navigation, taxonomy, screenshots, media records, sitemap URLs, and site-owned assets are packaged locally.

Home, work, studio, archive, case pages, Ask Kirk, resume, contact, and status now share the fixed-width black/red system.

The Work route now has an interactive signal map, media/data/retrieval theater, and evidence decoder that maps Citi dashboard artifacts and FiOS media controls into source-backed interface readouts.

The home page now removes the WebGL globe and top-right signal boxes; the Citi/default hero starts with the accepted large headline while Featured Work card clicks switch the headline, poster/video-ready surface, supporting metadata, and case CTA.

site/src/data/home-hero.ts now owns the Featured Work hero slide copy, poster fallbacks, Cloudflare-ready video source fields, motion briefs, and per-project loop-video asks.

The Studio route now separates Goodnight eNight verified Story Builder proof from Rock This secondary-source staging, with inputs, generation, review, output, proof gates, and next real asset needs.

The Goodnight eNight and Rock This case pages now have source-context cards and signal constellations: Goodnight uses official product/FAQ/terms/credits proof, while Rock This stays clearly secondary-source staged until primary product links arrive.

Recent Citi, Goodnight eNight, Rock This, final staged scene decisions, latest resume wording, and source-publication approvals still need Kirk review.

The targeted WordPress files/database archive is present in archive/server-site/final/; the only optional archive decision is whether to preserve the full cPanel account backup too.

Citi, Verizon/Fios, Goodnight eNight, Netflix-inspired interaction patterns, OpenAI APIs, and animation standards now have a source-backed planning brief; Rock This still needs a primary product source.

The launch checker and preview UI verifier cover rebuilt routes, representative legacy redirects, API boundaries, status panels, and final-art decision state.

The prototype now distinguishes baseline Motion work, CSS scroll-linked reveals, View Transition experiments, optional GSAP timelines, future Three.js scenes, and asset-driven Rive/dotLottie microinteractions.

The Status route now exposes live, selected, planned, and deferred stack layers for Next.js, Vercel, Sanity, Clerk, Supabase, OpenAI, GPT Image workflow, Motion, Three.js, GSAP, and data visualization.

The private handoff now reports 7 configured service groups, 0 missing groups, and deferred Sanity without exposing secret values.

site/vercel.json runs npm run build on Vercel, npm run verify:launch remains the local pre-deploy gate, package engines allow Node 20-24, and .vercelignore keeps local QA artifacts and env files out of deploy uploads.

npm run sync:dns-cutover records current public DNS, configured Vercel apex/www targets, GoDaddy nameservers, pre-cutover steps, post-cutover checks, and rollback instructions without changing DNS.

The Status, Work, case-study theater, and Studio surfaces now use CSS view timelines, and internal app links use progressive View Transition API navigation with reduced-motion and unsupported-browser fallbacks.

The Work command center now has a Case Poster Relay where each project poster is a named View Transition surface that can expand into the matching case-theater hero media layer when the browser supports it.

All final-scene folders have complete hero/poster/artifact slots; Rock This and Rock This Music are source-backed candidate decisions, while Citi, FiOS, Goodnight eNight, and Virtual Kirk are staged for approval or source-approved replacement.

The Status route now shows a hero-candidate review reel, and npm run approve:final-scene can list, approve, keep as candidate, reject, or return final-scene metadata to candidate review with an optional --sync refresh.

/status#final-art-decision-queue now combines candidate review, source coverage, proof asks, boundaries, exact drop paths, and approve/keep-candidate/reject --sync commands for Citi, FiOS, Goodnight eNight, Rock This, Rock This Music, and Virtual Kirk.

/status#kirk-input-queue and docs/kirk-input-queue.md now collect the launch-blocking handoff items, accepted input formats, drop paths, and verification commands in one place.

npm run export:cms-content now emits a Sanity-ready NDJSON seed, JSON review manifest, inferred schema contract, and review flags from archive, case-study, redirect, asset, resume, and Virtual Kirk corpus sources.

Supabase tables, usage RPC, and approved-corpus seed export are specified; the API can persist interview sessions, consent events, session-only transcript turns, and durable question windows when production service credentials are configured.

The Ask Kirk hero now visualizes the required access pass, approved corpus, guardrail, transcript, and source-backed answer flow as a reduced-motion-aware Three.js scene.

The Citi and FiOS case pages now include an animated signal constellation that maps archived artifacts, public context boundaries, evidence proof, signal weight, and launch-gap readouts into the case theater.

The local approved corpus now exports to a reviewable JSON manifest and an idempotent Supabase upsert seed for public, signed-in, and recruiter modes.

The Resume route now maps provisional claims to source lanes, proof boundaries, readiness signals, missing inputs, the Markdown draft, and the provisional PDF before final approval.