Freeze the repo-side story
Make sure the release page, share kit, 30-second overview, and support/community links all reflect the same current-main truth.
Use this packet when the repo-side launch materials are ready and only manual platform actions remain.
This page is the handoff line between repo-owned preparation and real external activation. It keeps the materials, order of operations, and truthful no-claim boundary in one place.
What this packet is for
- Turn the current docs and media surfaces into a repeatable launch checklist
- Keep search-indexing, domain, video, and platform work clearly outside repo-side done claims unless fresh owner proof moves them forward
- Give a human operator one place to start when the next step is a public release, announcement, or demo post
Repo-side assets already ready
| Asset | Current repo-owned proof | Use it for |
|---|---|---|
| Front door and comparison pages | Home, Compare, FAQ | First-touch explanation and fit filtering |
| Support and community routing | Support, Community | Point new visitors to Q&A, Ideas, Show and tell, and announcements |
| Tagged release story | Release history plus GitHub releases | Explain what is tagged versus what only exists on current main |
| Short public explanation kit | Share kit and 30-second overview | Punchline, short demo, compare card, and short copy reuse |
| Reusable visuals | docs/assets/social-preview.png, docs/assets/run-flow.gif, docs/assets/upstream-vs-snapshot.png |
Cards, short clips, release notes, and announcement thumbnails |
Search Console prep
- Only if it still belongs in this launch plan: if you do not currently plan to use Search Console, or you do not yet have owner access to the target property, keep it in the external/manual bucket and skip it for this round
- Repo-side ready: sitemap.xml, robots.txt, canonical tags across the docs site, and the current Pages homepage link on the GitHub repo
- Still manual: ownership verification, sitemap submission, reindex requests, and any “already indexed” claim
Domain and canonical prep
- Repo-side ready: canonical URLs, `site.webmanifest`, and control-room-first wording that still fits the current Pages host
- Still manual: buying or switching domains, DNS / CNAME / redirect rollout, and verifying that the live canonical move actually works
Truthful snippets you can reuse
- One-line pitch: Use upstream for the engine. Use this repo for the local control room.
- 30-second pitch: Apple Notes Snapshot is a local-first macOS backup control room that keeps the upstream exporter, then adds scheduling, health checks, a token-gated Local Web API, AI Diagnose, and a read-only MCP surface.
- Builder-heavy pitch: The truthful builder entry points today are
notesctl, the same-machine Local Web API, and the read-only stdio-first MCP surface. It is not a public API or SDK platform. - Support routing line: Questions and setup blockers go to Q&A; public updates and release notes should still point people back to Support and Community.
Release and announcement prep
- Repo-side ready: release history, the share kit punchline and snippets, and the support/community routing pages that public posts can point back to
- Repo-controlled lane: GitHub releases and GitHub announcement discussions are closer than Search Console or DNS work because they stay inside the repo's own control plane, but they still need an authenticated owner session and a final human publish decision
- Still manual for the next public update: deciding the tagged truth, publishing the next GitHub release, posting the next announcement, and confirming that the public post matches the final tagged truth
Repo-controlled lane already landed
- Latest public GitHub release: the current tagged release is already live in GitHub releases.
- Latest announcement discussion: the latest public release announcement is already live in the announcements lane.
- Why this matters: this page separates repo-controlled actions that already happened from Search Console, DNS, video, and social actions that still require external control-plane access.
Video and clip prep
- Repo-side ready:
docs/assets/run-flow.gif,docs/assets/social-preview.png, and the short copy surfaces in the share kit and 30-second overview - Still manual: recording a new clip, selecting a thumbnail, exporting the final asset, and uploading it to any external platform
Social and share-kit prep
- Repo-side ready: the share kit, 30-second overview, and repo description already encode the current control-room-first story
- Still manual: tailoring the final post for each channel, attaching images, and pressing publish on any external social surface
Community and support routing prep
Suggested external activation order
Decide what counts as tagged release versus current-main preview
Do not let a public post imply that the latest tag already contains main-branch surfaces if it does not.
Prepare the public post body
Reuse the share kit punchline, short demo, compare card, and release snippet structure before you touch external platforms.
Run the manual platform actions
If those lanes are still in scope, Search Console submission, domain or canonical changes, video upload, and platform distribution all stay outside repo-side completion.
Route replies back into repo-owned lanes
Point support traffic to Q&A or Support, and point ongoing conversation to Community and announcements.
Operator checklist
- Confirm the repo-side story is frozen across Home, Releases, Share kit, 30-second overview, Support, and Community
- Confirm the latest public tag versus current-main wording is still truthful
- Choose which reusable assets and snippets the external post will use
- Run only the manual platform actions that still belong to the current launch plan
- Route replies back into the repo-owned support or community lane
External-only actions still required
- Search Console setup, resubmission, or indexing checks, if this round still depends on search-indexing work
- Domain purchase, canonical move, or redirect rollout
- Video export, upload, thumbnail selection, and platform metadata entry
- Publishing social posts or third-party listings
- Any follow-up measurement that depends on external traffic, search indexing, or platform moderation
What must be done by a human
A human still has to press the buttons that live outside this repo. When those lanes are in scope, that means Search Console, domain or redirect changes, video upload, social or listing posts, and the final judgment about whether external indexing or traffic actually happened.
Minimum human action packet
Use this table like a handoff envelope. If a platform is not chosen yet, the truthful next step is to choose the platform first instead of inventing a fake button path.
| Action | Exact URL | Required account or ownership | What is already prepared | Exact button or control | Proof to capture after action | Claim still forbidden first |
|---|---|---|---|---|---|---|
| Search Console ownership and sitemap submission | search.google.com/search-console | Google account that actually owns or can verify the target property | sitemap.xml, robots.txt, canonical tags, and the current Pages homepage link are already in place | If this lane is still in scope, use Start now, then Add property or the visible property picker, then open Sitemaps and click Submit | Capture the property view or sitemap row that shows the property exists and the sitemap submission result is visible under the signed-in owner account | Do not claim Search Console is configured or indexed before the owner sees the property and the submission result |
| GitHub Pages custom-domain or redirect work | GitHub Pages settings | GitHub repo owner session plus registrar or DNS ownership for the chosen domain | Canonical URLs, manifest, control-room-first wording, and the Pages homepage already exist | Use the Custom domain field, click Save, then enable Enforce HTTPS if GitHub Pages offers it after DNS finishes resolving | Capture the saved Pages settings state and the live HTTPS hostname resolving to the intended public site after DNS or redirect rollout completes | Do not claim a custom domain or canonical move is live before DNS and redirects resolve correctly |
| Video upload | No platform selected yet | Owner access to the chosen video or media account | The share kit, 30-second overview, social preview image, compare card, and run-flow clip already exist | Pick the platform first, then use that platform's Upload or Create action, choose the thumbnail, and publish the final metadata | Capture the live video URL and the published title or thumbnail state on the destination platform | Do not claim a live video or clip campaign before a platform URL exists |
| Social or third-party listings | No platform selected yet | Owner access to the target social account, listing profile, or community account | Truthful snippets, support routing, community routing, and release links are already prepared | Pick the channel first, then use that platform's Post, Publish, or equivalent final-submit control | Capture the live post or listing URL plus the published text or asset preview on the target surface | Do not claim a social or listing campaign exists before a live post URL exists |
What must not be claimed before external activation really happens
- Do not claim Search Console is configured unless a human actually did it
- Do not claim a new domain or canonical move is live unless DNS and redirects are truly switched
- Do not claim a video or social campaign exists unless it was actually posted
- Do not turn “repo-side launch prep ready” into “external launch complete”
- Do not let launch copy drift into hosted API, public SDK, OpenAPI, or generic AI platform language