# Registration Pilot Readiness Checklist

Use this before opening any real GroundMesh registration or declared-joining path beyond simple
public contact.

## 1) Scope is narrow and honest
- The pilot has a named purpose.
- The pilot has a limited cohort, circle, geography, or invitation path.
- The first promise is smaller than the long-term mission.
- The public copy clearly says this is a pilot if that is the truth.

## 2) Consent and privacy are defined
- The requested data fields are the minimum truly needed.
- The participant can understand what becomes public, private, or review-only.
- There is a clear consent statement.
- There is a removal or correction path.
- The storage location and access boundaries are known.

## 3) Moderation and verification exist
- Someone is explicitly responsible for reviewing submissions.
- There is a rule for what gets accepted, paused, rejected, or escalated.
- There is a way to flag unclear, harmful, or suspicious submissions.
- Verification is proportional to the promise being made.

## 4) Operations are real
- The contact or intake path is monitored.
- Expected response timing is known.
- There is a fallback if the primary steward is unavailable.
- There is a simple logging trail for what happened and why.

## 5) Technical handling is ready
- The intake surface is separate from the static public docs if sensitive handling is involved.
- Basic failure, spam, and duplicate handling are considered.
- A rollback path exists if the pilot starts causing confusion or harm.
- The path has been tested with a small internal or trusted-circle dry run.

## 6) Launch discipline holds
- The pilot opens only after the above items are honestly green.
- The launch is reviewed after the first real submissions.
- Expansion happens only after demonstrated handling, not excitement alone.