WHAT IS VERIFIED, WHAT IS FORMING, WHAT IS PENDING
Community activity without invented proof
JYC will not turn estimates into facts. Public counts require a documented source, staff review, and a privacy-safe minimum. Missing data appears as pending—not as zero success and never as a made-up number.
PERMISSION RECORD NEEDED
Hero photography
The current image is already published by JYC, but this upgrade cannot independently verify a written display release.
FORMING FROM REAL INTEREST
Recurring pods of 6–10
The pod-interest workflow is live. No active roster is presented until a host, participants, dates, and consent are confirmed.
AWAITING VERIFIED CLOSEOUTS
Attendance and return counts
No eligible private feedback responses have been recorded yet.
MODERATION QUEUE OPEN
Community moments
No permission-confirmed moment has been published through the moderation tool yet.
WEEKLY DELIVERY LIVE · ADVANCED ROUTING STAGED
Alert controls
Browser and email opt-ins are available. County, type, frequency, quiet-hour, and channel planning can be saved on-device, but targeted server delivery is not claimed as active.
PUBLISHED ON CONFIRMED EVENT PAGE
Event costs
JYC displays cost details on the confirmed event page after staff publishes them. Planning or incomplete listings remain labeled pending; no amount is inferred.
SOURCE METADATA INCOMPLETE
Testimonials
11 existing testimonials are published; recency, general location, and separate display-permission metadata still require staff verification.
THE PUBLICATION RULE
Evidence first, privacy by default
- Collect less. Ask only for information needed to improve an event or form a group.
- Separate purposes. Private feedback never becomes a public testimonial without a new choice.
- Verify the source. Attendance, cost, permission, and return claims need a named staff review.
- Protect small groups. Public aggregates wait for at least five eligible responses.
- Show uncertainty. Pending, forming, and unverified are valid public states.
WHY THE SITE WORKS THIS WAY
