# GitHub And Vercel Launch Checklist

This checklist is for the moment when security QA and sweep are complete and the repo is approved for publication as a private GitHub repository.

## Preconditions

- Security QA signed off
- Repo-safe file boundary confirmed
- `modeldock_repo_ready` reviewed one final time
- Decision made about whether Vercel will host a portal or other public surface, not the full local infrastructure stack

## GitHub launch sequence

1. Create a new private GitHub repository
2. Initialize git from this directory only
3. Verify `.gitignore` is present before the first add
4. Review `git status`
5. Commit the curated initial contents
6. Push the default branch to GitHub
7. Confirm that no live secret or runtime-state files were included

## Vercel launch sequence

1. Decide what Vercel is actually hosting
2. Confirm the hosted surface is repo-safe and deployment-safe
3. Create the new Vercel project only after the GitHub repo is in place
4. Add only the environment variables required for the Vercel-hosted surface
5. Do not mirror local infrastructure secrets into Vercel unless they are genuinely needed there

## Explicit guardrails

- Do not publish from `/home/mark/modeldock`
- Do not commit `.env`
- Do not commit `state/`, `outputs/`, `receipts/`, or live sync state files
- Do not assume Vercel will host Open WebUI, LiteLLM, Flowise, Postgres, Redis, or Qdrant
- Keep the ingress contract separate from the Vercel hosting decision

## What I will do later when you approve

- create the private GitHub repo
- push the sanitized initial commit from `modeldock_repo_ready`
- create the Vercel project only for the approved repo-safe surface
- keep the local/private stack concerns separate from the public deployment surface