# Operate and change Core

Who owns Core, what to check before a schema change and when to review these pages.

Owner: Pedro, the Systems owner. Open work for Core is tracked as Work Items in Systems Central, linked to the system Core Record Types.

## Before changing a field or table

Core feeds up to six systems, so a schema change is never local.

1. Find the consumers in [Architecture and ownership](/systems/core/architecture) and the field's page under [Entities](/systems/core/entities).
2. Renaming a field keeps its ID, but a mirror may show the new name, and n8n nodes or formulas that use names can break. Workflows that write by field ID, such as the booking workflow, are safe from renames.
3. Changing a type, such as Zipcode from number to text, can empty or reformat values in mirrors. Test in a copy first.
4. Removing a field or a link drops it from every mirror that includes it, and links between mirrors survive only when both tables stay mirrored.
5. Adding a field does not add it to a mirror; the consumer must include it in its sync.
6. Keep the description format: a human block followed by a `definition:` block. Field descriptions are the meaning shown on these pages.

## Review triggers

Update these pages when any of these change: a field, view or table in Core Record Types; an Airtable automation in the base; a consumer mirror or its sync; the booking or e-mail workflows in n8n; the rule that Core is the only writer of shared records, or any rule about who may write to Core.

## Routine checks

- Review Proposed and blank-Status rows in People and Organizations.
- Review Campaign › Orphans - Set lifecycle status and Step 1 - Review the campaign lifecycle.
- Scan Health check in People, Organizations, Address, Cities and States.
- Confirm Campaign — assign immutable coreId is still deployed after any automation change.