Amicus · Internal

Stand-Ups

Every firm we've stood up on the app3 platform — its URLs, its Layer-2 data coverage, live server vitals, and deploy state. The control panel for the stand-up fleet.

0 selected Tick firms in any section, then Parameters (fill card fields via Sonnet) or Print (build the Slides deck). Prospects are skipped — stand them up first.

Add a domain — seed a pre-stand-up

Queues a firm for stand-up (stored in this browser). It shows as a striped pending row with zero provisions until its real data bundle is built and the tenant is wired in the registry.

Firm name Slug / subdomain Website Vertical

Visited

0 firms with a site visit / email / follow-up logged — shown only here (pulled out of the fleet, prospects, and the to-contact list below)

Printed ◆

0 firms whose leave-behind card is printed (Google Slides deck generated) but not yet visited — check them off and Print above, and they move here

Ready

stood-up firms not yet visited — URLs, Layer-2 coverage, vitals, deploy state

	Firm	URLs	Back end	Deploy	Paid ads	Server vitals	Layer-2 provisions

Stand-Downs

domains we've stood down — tracked on account_defs.standdown_at; tracking only, the subdomain stays deployed until removed separately · Restore returns it to the fleet

Standups ★

0 firms marked prime on the attorney map queued to stand up · green rows are already stood up — edit any variable and Save to drive it (live from amicus_pipeline2.account_defs)

Drop-Offs

which leave-behind pieces were physically left with each firm · piece titles from pdf2.amicusdata.dev (+ the v1 cover cards)

Firm Piece (pdf2 page) Note

The 5 Layer-2 provisions

KW Explorer — keyword taxonomy tree (owned / gated / gaps).
BL Deep — referring domains / anchors / history; count = ref-domains.
BL Full List — the complete page-level backlink list; count = links.
Citations — NAP fidelity matrix; count = live directory sources.
Site Assets — copy + deduped images harvested from the firm's own site (clients/<slug>/assets/ via collect_site_assets.py); count = images kept.

Baseline data from the main pipeline (Keywords · Reviews · GBP Profile · Map Grid) is excluded — this matrix tracks only the Layer-2 overlay enhancements the stand-up adds.

How to read the columns

URLs — WEB the firm's public site · APP the app3 data app (<slug>.amicusdata.dev, demo/demo) · .IO the static marketing homepage where one exists.
Back end — CF Pages project, BQ org_id, pipeline profile, auth.
Server vitals — Lighthouse Perf / SEO / Accessibility / Best-Practices + LCP, the same badge the map/home module surfaces. ≥90 green, 50–89 amber, <50 red.
Paid ads — derived: the firm's domain/CID present in the market Google-Ads advertiser roster (cadence_data.json). Absence ≠ proof they never advertise.

Operating the panel

Data is read live from the repo: file presence → provision checkmarks, home_data.json → vitals.
Re-run python standups_site/_build/build_standups_data.py after any stand-up, then redeploy.
Add domain queues a pre-stand-up locally — the seed for the full stand-up run (see pipeline2/STANDUP_SESSION_RESUME.md).
Full runbook: pipeline2/STANDUP_OPERATIONS.md.