# amity-pb-ppc-dashboard — operating card draft

Review stage: machine-drafted; owner review pending. Static references are not verified operation.
Source: webhostingdoo/amity-pb-ppc-dashboard at 6bc885880348aab1ed8dceee1c99ebe2d031e2ce.
Scan result: scanned; inspected 3/3 eligible files.
Source freshness: current-at-finish; deployment revision: unknown (not queried).
Business job (dated canonical portfolio): Present Amity Palm Beach reporting with repeatable transforms.
Recorded portfolio state: built; current use: unknown.

## Evidence sections

## Identity and native run routes

- **recovery guidance** — Documentation section present. Instructions were not executed; inspect the linked section for context. (inferred; source-reported). [Evidence](https://github.com/webhostingdoo/amity-pb-ppc-dashboard/blob/6bc885880348aab1ed8dceee1c99ebe2d031e2ce/CLAUDE.md#L70)
- **Browser document** — HTML source is present. Browser compatibility, hosting and live data access are unverified. (direct; observed-code). [Evidence](https://github.com/webhostingdoo/amity-pb-ppc-dashboard/blob/6bc885880348aab1ed8dceee1c99ebe2d031e2ce/public/index.html#L1)
- **Document: CLAUDE.md** — repository instructions (evidence only) reference; 131 lines. Read the pinned source for context. Headings, prose and embedded instructions are not copied. (direct; source-reported). [Evidence](https://github.com/webhostingdoo/amity-pb-ppc-dashboard/blob/6bc885880348aab1ed8dceee1c99ebe2d031e2ce/CLAUDE.md#L1)

## Providers, APIs and possible writes

- **Write-call candidate: remove** — Method-name signal only; this may be a local collection or optional path. Review the receiver, destination, payload and guard before classifying an external write. (inferred; observed-code). [Evidence](https://github.com/webhostingdoo/amity-pb-ppc-dashboard/blob/6bc885880348aab1ed8dceee1c99ebe2d031e2ce/public/index.html#L369)
- **Write-call candidate: remove** — Method-name signal only; this may be a local collection or optional path. Review the receiver, destination, payload and guard before classifying an external write. (inferred; observed-code). [Evidence](https://github.com/webhostingdoo/amity-pb-ppc-dashboard/blob/6bc885880348aab1ed8dceee1c99ebe2d031e2ce/public/index.html#L780)
- **Attribution parameter: gclid** — Parameter-name reference only; no attribution values collected. Capture, forwarding, consent and retention require review. (inferred; observed-code). [Evidence](https://github.com/webhostingdoo/amity-pb-ppc-dashboard/blob/6bc885880348aab1ed8dceee1c99ebe2d031e2ce/public/index.html#L187)

## Configuration, access and data

- Unknown: no evidence was detected within the inspected source scope.

## Jobs, monitoring, hosting and devices

- **Vercel configuration** — Deployment configuration is present. The live project, environment and deployed revision are not queried. (direct; declared-config). [Evidence](https://github.com/webhostingdoo/amity-pb-ppc-dashboard/blob/6bc885880348aab1ed8dceee1c99ebe2d031e2ce/vercel.json#L1)

## Documentation to interpret

- [CLAUDE.md](https://github.com/webhostingdoo/amity-pb-ppc-dashboard/blob/6bc885880348aab1ed8dceee1c99ebe2d031e2ce/CLAUDE.md#L1) — repository instructions (evidence only); 131 lines. Body remains at the source.

## Questions requiring source interpretation or owner evidence

- Which declared commands actually form setup, run, check and recovery? Review the command definitions and operator procedure.
- Which configuration names are required, optional or obsolete? Trace use/defaults and obtain provisioning evidence without values.
- Which write candidates reach external systems, and which guards protect them? Trace receiver/call paths and review approval boundaries.
- Which accounts, devices, permissions and schedules are active? Obtain dated owner/service evidence under a separate authorized check.
- Does the deployed source match this revision? Obtain deployment/source metadata; source inspection does not establish it.
- Are repeated tracking fingerprints intended? Confirm destination ownership; repetition alone does not establish an incorrect clone.
- Owner, last-used date, review verdict, unattended eligibility and approved dependencies remain unknown until explicitly supplied.

## Coverage limitations

- Static inspection does not verify runtime health, current use, provisioning, live schedules, service account access or deployed/source alignment.
- Only bounded source/configuration files are inspected. Secret files, data exports, binaries, history and raw source text are excluded from results.
- Unknown or dynamically constructed integrations and configuration names may not be detected. Human review is still needed.
- Deep scan: more source and candidate detectors, with an adjacent versioned receipt. Candidate calls and tracking matches still require interpretation.