[EPIC] GeoPlatform Synchronization

**What:**
Establish a regular coordination cadence between Data.gov and GeoPlatform.gov to keep both programs aligned on metadata quality, timing, and any upstream changes that could affect GeoPlatform's consumption of Data.gov metadata.

**Why:**
GeoPlatform currently pulls Data.gov metadata as a starting point and supplements it with direct-from-source dataset content. This makes Data.gov an upstream dependency for GeoPlatform, which is close to a policy requirement via FGDC. Despite mutual intent to coordinate, no standing rhythm exists -- both teams are under-resourced and the relationship stays on the "we should" list. A lightweight standing sync would prevent surprises (harvester changes, metadata schema updates, platform transitions) from hitting GeoPlatform without warning, and vice versa.

**Done When:**
- A standing sync is scheduled with GeoPlatform and FGDC partners (even if quarterly to start)
- A shared point of contact is confirmed on both sides
- Both teams have visibility into each other's near-term roadmap items that could affect the metadata flow

**Notes:**
- GeoPlatform pulls Data.gov metadata first, then often supplements with direct source data -- Data.gov is upstream but not the only input
- DCAT-US 3.0 transition is a near-term risk: if Data.gov metadata structure changes, GeoPlatform's harvest could break or degrade -- they need advance notice
- Keep scope light: this is a relationship/coordination epic, not a build. Resist scope creep toward technical integration work until the rhythm is established and both teams have bandwidth
- Similar pattern to the SAP integration exploration but at a different maturity level -- GeoPlatform integration is already live, SAP is conceptual

## Tasks

- [x] Identify current GeoPlatform point of contact and confirm they are the right person for a coordination relationship
- [x] Draft a short outreach message to GeoPlatform proposing a standing sync (quarterly to start)
- [x] Confirm FGDC partner point of contact and whether they should be included in the sync or kept as a separate touchpoint
- [ ] Document the current metadata flow: what Data.gov fields GeoPlatform consumes, at what frequency, and via what mechanism
- [x] Share Data.gov's DCAT-US 3.0 transition timeline with GeoPlatform as an early heads-up
- [ ] Ask GeoPlatform if there are known pain points or gaps in what they currently receive from Data.gov
- [ ] Agree on a minimal shared artifact -- even a one-pager -- that captures the relationship, the data flow, and each team's point of contact, so institutional knowledge doesn't live only in people's heads
- [x] Schedule the first sync and set a recurring cadence