# Records guide

These tracked records are intentionally small and public-safe. Use public business URLs, public handles, and concise operating notes only. Private contacts, raw media, and account data belong in ignored local storage.

## `businesses.csv`

One row per business, place, attraction, or amenity under consideration.

- `business_id` is a stable lowercase slug used by the calendar and post records.
- `public_contact_channel` can be a public Instagram handle, public contact page, or `in-person`; never put email addresses or phone numbers here.
- `relationship_status` is `researching`, `interested`, `contacted`, `active`, `paused`, or `declined`.
- `permission_status` is `not-needed`, `researching`, `requested`, `granted`, `declined`, or `withdrawn`.

## `editorial-calendar.csv`

One row per idea or planned reel. `subject_id` normally equals a `business_id`; it may identify a non-business local place.

- `permission_status` uses the same vocabulary as `businesses.csv`.
- `publishing_status` is `idea`, `researching`, `in-production`, `approval-needed`, `approved`, `ready-for-manual-publish`, `published`, `held`, `removed`, or `declined`.
- `stagehand_package_ref` is a stable Stagehand package ID, URL, or local ignored path—not a copy of a delivery package.
- `post_record` is the repository-relative path created from the post template.

## Post records

Use `templates/post-record.md` for every intended or published reel. A post file holds the approval, source-asset references, account-specific copy, publishing record, and outcome notes for one post.