TRAINING PAGE

Training page

Sandbox only. Not a production page.

Operator panel

/admin

Lightweight operator page for sponsorship status, free vs taken inventory, and activation instructions.

Start here

Use these owned routes first when you want the clearest path into guides, next steps, and local markets.

Enter password

This is a lightweight visibility gate for operators. It is not secure authentication.

What this page is for: give a VA one place to see what is free vs taken, what each product includes, exactly how to activate or turn off a sponsor, and how to get oriented in the training pack before touching the real repo. Open training/public site.

Current snapshot

Active vertical buyout

No

Vertical ownership record

None

Reserved city count

0

Free city count

13

Base city limit

10

Extra city policy

unlimited_with_explicit_declaration

Template requests loaded

1

Products you can sell

City Buyout

One city page. Sponsor owns the CTA layer and lead routing for that city.

Use data/buyouts.json to make it live.

State Buyout

One state page. Sponsor owns the CTA layer and lead routing for that state.

CTA above the directory becomes the sponsor feature surface when enabled.

Vertical Buyout

Homepage + guides + up to 10 cities + corresponding states.

Additional cities can be added as extras. PI excludes city pages.

Inventory and conflicts

City availability

CityStatusSponsor
Atlanta, GAFree
Charlotte, NCFree
Chicago, ILFree
Dallas, TXFree
Demo City, TXFree
Los Angeles, CAFree
Memphis, TNFree
New York City, NYFree
Orlando, FLFree
Philadelphia, PAFree
Phoenix, AZFree
Sandbox Metro, FLFree
Testville, CAFree

Statewide buyouts

StateSponsorBase / extraCity list
No statewide buyouts configured.

CTA and lead-routing status

CTA ownership rule

When bought out, the CTA layer routes to the active sponsor while public paths stay stable.

Runtime status

No live vertical buyout runtime record.

Lead target missing or not configured.

Directory CTA rule

If a page has a directory, the CTA block directly above it becomes the sponsor feature surface when directory takeover is enabled.

Activation checklist

  1. Check /admin to confirm what is free vs taken.
  2. Choose product: City Buyout, State Buyout, or Vertical Buyout.
  3. Create or update the sponsor record under data/sponsor_intake/sponsors/<slug>/.
  4. Drop logo, hero image, and directory CTA image into the sponsor assets folder.
  5. Update data/buyouts.json only when the sponsor should be live at runtime.
  6. Rebuild and run validation.
  7. Click-audit /for-providers/, /next-steps/, /request-assistance/, and all affected pages.

Runbooks: Sponsor Activation · Head VA Operations · VA Quick SOP

Add missing cities

Missing cities? Use data/templates/city_request.template.json and run node scripts/scaffold_city_from_request.js data/templates/city_request.template.json --apply.

The scaffold script adds the city to the pack city file, creates placeholder city content, and leaves a clear marker for follow-up edits before production use.

Then update data/buyouts.json if the new city belongs to a live city, state, or vertical buyout.

Head VA can also use GitHub → Actions → Add City Request to generate a PR from structured inputs instead of using the local terminal path.

Operator docs

START HERE: open on GitHub

Repo Architecture Primer: open on GitHub

LLM prompts: open on GitHub

Global Repository Operations Manual: open on GitHub

Listings Master Index: open on GitHub

Head VA Operations Runbook: open on GitHub

VA Quick SOP: open on GitHub

City Addition Runbook: open on GitHub

Sponsor Activation Runbook: open on GitHub

Head VA city creation paths

Local repo path

  1. Fill out data/templates/city_request.template.json
  2. Run node scripts/scaffold_city_from_request.js data/templates/city_request.template.json --apply
  3. Rebuild and validate
  4. Click-audit affected pages

GitHub path

  1. Open GitHub → Actions
  2. Run Add City Request
  3. Fill in the structured inputs
  4. Review the generated PR and merge after validation passes

Red flags

  • Do not treat this page as secure authentication.
  • Do not sell homepage or guide coverage under anything except a Vertical Buyout.
  • Do not exceed the vertical included-city limit of 10 cities without explicit extras.
  • Do not override an already reserved market silently.
  • Do not activate CTA takeover without a sponsor record and lead email.
Quick commands
npm run build PAGE_SET_FILE=data/page_sets/examples/uscis_medical_v1.json LKG_VALIDATE_DIST=1 npm run validate:all
Related search pathsAdditional owned routes for this topic

These routes support fanout/query coverage and keep owned paths visible, but they are intentionally secondary to the main framework and next-step flow.

Primary route