Proof that the funnel is deployed, crawlable, and being checked.

Launch Readiness

This section reads /.well-known/launch-readiness.json and shows which parts of the original goal are complete, ready, or still waiting for external domain/search-console actions.

Goal Completion Audit

This section reads /.well-known/goal-completion-audit.json and checks the original end-to-end goal without narrowing success to the preview deployment.

Owner Action Pack

This section reads /.well-known/owner-action-pack.json and turns the remaining final-domain blockers into exact owner-side actions, required proof, and refresh commands.

Domain Purchase Handoff

This section reads /.well-known/domain-purchase-handoff.json and shows the registrar, DNS, Search Console, and IndexNow checklist needed after buying the final domain.

Domain Purchase Fast Lane

This section reads /.well-known/domain-purchase-fast-lane.json and shows the fastest safe sequence from registrar checkout to DNS, HTTPS, Search Console, IndexNow, and first legal traffic experiment.

Domain Candidates

This section reads /.well-known/domain-candidates.json and shows fallback domains if the primary domain cannot be purchased during checkout.

Final Domain Consistency

This section reads /.well-known/final-domain-consistency.json and checks whether CNAME, robots.txt, sitemap, llms.txt, HTML canonical tags, and launch packets agree on the same final domain.

Final Domain Switch Plans

This section reads /.well-known/final-domain-switch-plans.json and shows dry-run replacement plans for available-signal domains. It does not mean a fallback domain has been selected.

Final Domain Switch Guard

This section reads /.well-known/final-domain-switch-guard.json and proves the fallback-domain replacement command has run in safe dry-run mode. It does not apply a domain switch unless --apply is explicitly used.

Traffic Measurement Gates

This section reads /.well-known/traffic-measurement-plan.json and defines what evidence counts as a working traffic funnel after final-domain launch.

Organic Proof

This section reads /.well-known/organic-proof.json and shows whether Search Console, analytics, referral, or manual evidence proves real post-launch organic traffic.

Final Domain Evidence

This section reads /.well-known/final-domain-evidence.json and shows owner-side proof items such as registrar receipt, DNS setup, Search Console verification, sitemap submission, IndexNow receipt, distribution evidence, and organic proof.

Evidence Intake

This section reads /.well-known/final-domain-evidence-intake.json and explains exactly what registrar, DNS, Search Console, IndexNow, distribution, and organic proof must be collected after final-domain launch.

Final Domain Evidence Draft

This section reads /.well-known/final-domain-evidence-draft.json and shows the safe draft input generated from RDAP, DNS, HTTP, Search Console, IndexNow, distribution, and organic proof sources. It does not overwrite owner evidence or mark unproven claims complete.

Final Domain Evidence Validation

This section reads /.well-known/final-domain-evidence-validation.json and checks that owner-side claims have receipts, dates, status codes, placement IDs, or search/analytics numbers before they can support completion.

Search Console Verification Plan

This section reads /.well-known/search-console-verification-plan.json and shows the exact DNS TXT / HTML file verification options, sitemap submission proof, URL inspection queue, and evidence fields needed after final-domain launch.

Search Console Owner Handoff

This section reads /.well-known/search-console-owner-handoff.json and turns the Google-side owner work into a short checklist: verify ownership, submit the sitemap, inspect priority URLs, and send back real evidence.

Search Console HTML File Guard

This section reads /.well-known/search-console-html-verification-file.json and proves whether a real owner-downloaded Google HTML verification file has been safely installed. It does not claim Search Console verification by itself.

Final Domain Monitor

This section reads /.well-known/final-domain-monitor.json and shows the owner-facing progress from domain purchase through DNS, HTTPS, Search Console, IndexNow, distribution, and organic proof.

Final Domain Watch

This section reads /.well-known/final-domain-watch.json and shows the safe polling command to run after buying the domain. Default watch mode does not change remote files.

Post-Launch Evidence Calendar

This section reads /.well-known/postlaunch-evidence-calendar.json and shows the Day 0, Day 1, Day 3, Day 7, Day 14, and Day 30 proof schedule after the final domain goes live.

Discovery Feeds

This section reads /.well-known/discovery-feeds.json and proves that RSS, Atom, and JSON Feed files exist for discovery, feed readers, directories, and owned update workflows.

Traffic Research Proof

This section reads /.well-known/traffic-research-proof.json and proves that the free-traffic strategy is source-backed, anti-spam, and tied to measurable experiments instead of fake search loops.

Social Launch Assets

This section reads /.well-known/social-launch-assets.json and proves that sitemap pages have share-preview metadata and a reusable launch card for legal community distribution.

Core URL Checks

Traffic Sources

Clean event-log summary from the VPS JSONL tracker. Test crawler and referral requests are classified here.

Funnel Events

Server-side activation events posted by the frontend. These prove generator/checker usage when the custom VPS server is active.

Campaign Tracking

UTM campaign counts from access logs. Use these to prove real community, README, newsletter, or partner-referral visits after launch.

Placement Attribution

This section reads /.well-known/campaign-attribution.json and maps planned distribution placements to observed utm_content values. Test or unplanned UTM content is shown separately so it is not counted as a successful placement.

Distribution Execution Pack

This section reads /.well-known/distribution-execution.json and shows the answer-first post drafts that are ready to use after final-domain launch. The full JSON includes the copy, tracked URL, search prompts, skip conditions, and evidence fields for each planned placement.

Distribution Launch Queue

This section reads /.well-known/distribution-launch-queue.json and turns the answer-first drafts into a post-launch checklist with evidence import commands. It is not proof by itself; only public placement URLs or observed UTM traffic count.

Directory Target Queue

This section reads /.well-known/directory-target-queue.json and shows verified or manual-review launch, AI tool directory, software directory, and developer community targets. It is a manual workflow; success still needs public evidence or UTM/referrer activity.

Launch Copy Pack

This section reads /.well-known/launch-copy-pack.json and shows answer-first launch copy with final-domain UTM links and evidence commands. It prepares distribution; it does not post or prove traffic by itself.

Distribution Evidence Intake Pack

This section reads /.well-known/distribution-evidence-intake-pack.json and shows the placeholder records, CSV/JSON templates, and commands needed to turn real public placements into validated evidence.

Distribution Evidence

This section reads /.well-known/distribution-evidence.json and records real posted placement URLs after final-domain launch. It does not count drafts, skipped posts, deleted spam, fake clicks, or self-clicks.

Traffic Experiment Queue

This section reads /.well-known/traffic-experiment-queue.json and ranks abnormal but legal free-traffic experiments by safety, speed to proof, compounding potential, and friction. It is not traffic proof; only validated public evidence, UTM attribution, Search Console, analytics, or activation events can prove success.

14-Day Traffic Sprint

This section reads /.well-known/traffic-sprint.json and turns planned legal distribution into a day-by-day execution board. It tracks planned placements, observed UTM evidence, and skip/review days without counting spam or test clicks as success.

First Traffic Proof Kit

This section reads /.well-known/first-traffic-proof-kit.json and shows the first post-launch actions, proof thresholds, and evidence commands needed to prove real traffic without fake searches or clicks.

Recent Events

Access Counts

Legacy HTTP log counts are kept for comparison. The traffic source table above is the cleaner proof source.