Document repo structure + GBP snapshot workflow
This commit is contained in:
@@ -1,3 +1,21 @@
|
|||||||
# client-data-pss
|
# client-data-pss
|
||||||
|
|
||||||
Raw data, analysis, and monitoring for Phoenix Salon + Spa (DOP pilot client)
|
Raw data, analysis, and monitoring for **Phoenix Salon + Spa** (DOP pilot client).
|
||||||
|
|
||||||
|
## Structure
|
||||||
|
|
||||||
|
| Path | Purpose |
|
||||||
|
|------|---------|
|
||||||
|
| `raw/gbp-snapshots/` | **GBP snapshots** — point-in-time captures from clean audits. Fill via `TEMPLATE.md`, save as `YYYY-MM-DD-audit-N.md` |
|
||||||
|
| `raw/website-scrapes/` | Website crawls / captures |
|
||||||
|
| `raw/competitor-data/` | Competitor observations |
|
||||||
|
| `analysis/` | Interpretation — threats, opportunities, economics (NEVER raw data) |
|
||||||
|
| `monitoring/` | Ongoing trackers — reviews, ranks |
|
||||||
|
|
||||||
|
## GBP snapshot workflow
|
||||||
|
1. Copy `raw/gbp-snapshots/TEMPLATE.md` → new dated file
|
||||||
|
2. Run clean audit, fill every field with observed values
|
||||||
|
3. Use status vocabulary: `NOT_PRESENT` / `NOT_OBSERVED` / `Unknown`
|
||||||
|
4. Analysis goes in `analysis/` — never inside a snapshot
|
||||||
|
|
||||||
|
*Template aligned with `digital-operations-partner/docs/templates/gbp-snapshot-intake.md` v1.2.*
|
||||||
|
|||||||
Reference in New Issue
Block a user