First-party ICU evidence
Published ICU journals and experiments point to retained build/research evidence. Claims are scoped to what that evidence actually supports, and missing measurements stay unrecorded.
Journals · Trust
Evidence origin stays visible.
A future community layer can add useful projects without turning member assertions into ICU-verified facts.
Future community contributions
Contributor claims will remain attributed to the contributor and start as unverified. Moderator approval may permit publication; it does not silently convert an assertion into a verified product, commercial, or outcome fact.
Community status in O028
| Capability | Status |
|---|---|
| Member project submissions | Inactive; no public form or endpoint |
| Uploads | Inactive |
| Voting / request rankings | Inactive |
| Authentication & member profiles | Inactive |
| Moderation operations | Private schema prepared; no operator/service active |
| Creator marketplace / seller payments | Inactive; later commerce tasks own activation |
Privacy baseline
The base project-record model does not require legal names, email addresses, phone numbers, street addresses, precise location, or other private identifying information in public content. A future authenticated service would keep operational account/moderation identifiers private from the public record.
Compatibility note
The O028 origin boundary remains intact
The new platform layer adds source identity, freshness, rights, publication eligibility, and unresolved review states without changing O028’s first-party/community origin classifications or activating community submission flows.