Documentation outreach,
recorded in public time
CROVIA offers optional documentation enhancement packages to AI maintainers. We record public replies and timeline changes without judging intent or compliance. Everything shown here is tied to verifiable, public records.
What this is
- Neutral documentation suggestions, delivered publicly.
- Timestamped outreach records with traceable links.
- Continuous monitoring for visible documentation changes.
What this is not
- No accusations or judgments about compliance.
- No private messages or undisclosed sources.
- No claims of causality — only temporal sequencing.
Safety controls
- Strict rate limits, cooldown windows, and dedupe.
- 1 target per org in GitHub outreach list.
- All activity logged and reproducible.
How the outreach record works
We analyze model cards and public metadata to compute a completeness score and identify missing disclosure sections.
We open a public GitHub issue (or historical HF discussion) with optional enhancements, citations, and checklists.
We log public replies and closures as status updates. This is a timeline record, not a verdict.
Platform transition notice
Outreach channel shift: HuggingFace → GitHub
In early 2026, CROVIA's outreach shifted from HuggingFace Discussions to GitHub Issues. This change was necessitated by access limitations encountered on the HuggingFace platform for this account. This is a factual observation — platform access policies are the prerogative of each provider. We document this shift transparently because it affects the channel distribution visible in our records.
Both channels are included in all statistics. Every record links to its original public thread for independent verification.
Observatory (post-outreach drift)
We continuously scan for model card disclosure drift. When changes are observed after outreach, we record a temporal sequence (not causality).
Correlations require a time gap and specific disclosure fields (training section / declared datasets). This is conservative by design.
All observatory entries are backed by public links and DDF hash changes. If no correlations are shown, monitoring is still active.
Recent suggestions
| Target | Completeness | Provenance | Documentation | Offered | Days | Status |
|---|---|---|---|---|---|---|
| Loading... | ||||||
Methodology & neutrality
Outreach entries are generated from real logs and public links. Each suggestion includes a completeness_score derived from documentation analysis. We separate provenance_status (explicit data provenance) from documentation_status (overall completeness). We track days_pending to show time since the offer. We do not claim causality; we only record what was publicly visible and when it happened.