# amity-pb-ppc-dashboard — operating profile

Repository: webhostingdoo/amity-pb-ppc-dashboard
Source revision: 6bc885880348aab1ed8dceee1c99ebe2d031e2ce
HQ revision: bc9bd4733aecd8862c6a00e7db10853d2f3fc245
Scanned: 2026-10-23T16:21:36.889Z
Result: scanned

Static source evidence only. Runtime health, credential provisioning and current use are not verified. Secret values and raw source excerpts are excluded.

## Runtime & build

- **Browser document** — HTML source is present. Browser compatibility, hosting and live data access are unverified. (direct)
  - [public/index.html:1](https://github.com/webhostingdoo/amity-pb-ppc-dashboard/blob/6bc885880348aab1ed8dceee1c99ebe2d031e2ce/public/index.html#L1) · observed-code

To establish: Which runtime versions, build steps and operating systems are required?

## Providers & services

No evidence found in the inspected files. This does not establish absence.

To establish: Which provider accounts, plans and service owners are required?

## Secrets & configuration

No evidence found in the inspected files. This does not establish absence.

To establish: Where are these named requirements provisioned, and who owns rotation? Values are never collected.

## Schedules & background work

No evidence found in the inspected files. This does not establish absence.

To establish: Which declared jobs are enabled, in which environment, with what timezone and retry policy?

## APIs & webhooks

- **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)
  - [public/index.html:369](https://github.com/webhostingdoo/amity-pb-ppc-dashboard/blob/6bc885880348aab1ed8dceee1c99ebe2d031e2ce/public/index.html#L369) · observed-code
- **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)
  - [public/index.html:780](https://github.com/webhostingdoo/amity-pb-ppc-dashboard/blob/6bc885880348aab1ed8dceee1c99ebe2d031e2ce/public/index.html#L780) · observed-code
- **Attribution parameter: gclid** — Parameter-name reference only; no attribution values collected. Capture, forwarding, consent and retention require review. (inferred)
  - [public/index.html:187](https://github.com/webhostingdoo/amity-pb-ppc-dashboard/blob/6bc885880348aab1ed8dceee1c99ebe2d031e2ce/public/index.html#L187) · observed-code

To establish: Who calls each interface, with which authentication, quotas and write permissions?

## Data & storage

No evidence found in the inspected files. This does not establish absence.

To establish: Who owns the data, migrations, retention, backups and restoration?

## Identity & permissions

No evidence found in the inspected files. This does not establish absence.

To establish: Which human, service and tenant roles can read or write each resource?

## Errors & monitoring

No evidence found in the inspected files. This does not establish absence.

To establish: Where do errors and alerts go, who receives them, and are sensitive fields scrubbed?

## Hosting & delivery

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

To establish: Which project/environment is deployed, and does its source match this revision?

## Devices & execution access

No evidence found in the inspected files. This does not establish absence.

To establish: Does operation need a browser, mobile device, local PC, filesystem or remote computer? Who grants access?

## Troubleshooting & recovery

- **recovery guidance** — Documentation section present. Instructions were not executed; inspect the linked section for context. (inferred)
  - [CLAUDE.md:70](https://github.com/webhostingdoo/amity-pb-ppc-dashboard/blob/6bc885880348aab1ed8dceee1c99ebe2d031e2ce/CLAUDE.md#L70) · source-reported
- **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)
  - [CLAUDE.md:1](https://github.com/webhostingdoo/amity-pb-ppc-dashboard/blob/6bc885880348aab1ed8dceee1c99ebe2d031e2ce/CLAUDE.md#L1) · source-reported

To establish: Which runbook, health checks, rollback and recovery procedure have been exercised?

## Tests & ownership

No evidence found in the inspected files. This does not establish absence.

To establish: Who maintains this app, what is actually in use, and which checks establish acceptance?

## Coverage and limitations

3 files inspected of 3 eligible; 1 excluded/outside scope; 0 failed reads.

- 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.
