Documentation
How Hyperlabel scores and labels hypercert activity records.
How it works
- 1.Hyperlabel uses Tap — Bluesky's official sync tool — to monitor the AT Protocol network for org.hypercerts.claim.activity records. Tap automatically discovers repos, backfills historical records from each PDS, and streams live events with cryptographic verification. This means records created before the labeler started are still scored.
- 2.When a record is detected it is immediately written to the activity log and appears in the dashboard with a ⟳ Detected label while evaluation is in progress.
- 3.The scoring engine evaluates the record against 9 quality criteria worth 100 points in total. Test signals are checked first — any record that looks like placeholder data is flagged immediately regardless of its numeric score.
- 4.A signed AT Protocol label is applied to the author's DID based on the score tier. The pending label is negated and replaced with the final quality label.
Scoring criteria
Each record is evaluated on 9 criteria for a maximum of 100 points.
| Criterion | Description | Max pts |
|---|---|---|
| Title quality | Meaningful, descriptive title | 15 |
| Summary quality | Clear short description | 15 |
| Description quality | Detailed description with sufficient length | 20 |
| Image | Has an attached image | 10 |
| Work scope | Defines work scope tags | 10 |
| Contributors | Lists contributors with weights and details | 15 |
| Locations | Has geographic locations | 5 |
| Date range | Specifies start and end dates | 5 |
| Rights | Defines usage rights | 5 |
| Total | 100 |
Penalties
Points are deducted when low-quality patterns are detected.
| Penalty | Trigger | Deduction |
|---|---|---|
| Repetition | High line or word repetition in description/summary (e.g. song lyrics, copypasta) | −5 to −15 |
| Duplicate fields | Summary identical to description (lazy copy-paste) | −20 |
Quality tiers
Scores map to four tiers. Test signals override the numeric score and always produce a “Likely Test” label.
Well-documented record with comprehensive activity details.
Adequate record with basic activity information filled in.
Minimal record — appears to be a work in progress.
Contains test or placeholder data (e.g. "Test", "asdf", lorem ipsum, repeated characters).
Test signal patterns
Records are automatically flagged as ⚠ Likely Test when the title or summary matches patterns such as: test, asdf, lorem ipsum, untitled, aaaa…, or when the title is identical to the summary and fewer than 50 characters.
🤖 ML classification
After scoring, each record is asynchronously classified by a HuggingFace zero-shot model (facebook/bart-large-mnli). The model classifies the combined title, summary, and description text into one of four categories:
- • meaningful project description — legitimate content
- • test or placeholder data — test/junk content
- • song lyrics or copypasta — copied or irrelevant text
- • spam or gibberish — nonsensical content
If the model classifies content as non-meaningful with > 40% confidence, the record is automatically downgraded to ⚠ Likely Test.
API endpoints
The labeler exposes a small REST API for the dashboard as well as the standard AT Protocol labeler XRPC endpoint.
Dashboard statistics — total counts, tier breakdown, 24h/7d activity.
curl https://hyperlabel-production.up.railway.app/api/stats
Recent activities with pagination and optional tier filtering. Valid tier values: all, pending, high-quality, standard, draft, likely-test.
curl "https://hyperlabel-production.up.railway.app/api/recent?limit=20&offset=0&tier=high-quality"
Query AT Protocol labels via the standard labeler endpoint. Supports uriPatterns and sources query params.
curl "https://hyperlabel-production.up.railway.app/xrpc/com.atproto.label.queryLabels?uriPatterns=did:plc:*"
AT Protocol integration
Hyperlabel is a fully compliant AT Protocol labeler. Any app that supports the labeler protocol can subscribe to or query its labels.
Labeler DID
did:plc:5rw6of6lry7ihmyhm323ycwn
Handle
einstein.climateai.org
- —Labels are served via the standard com.atproto.label.queryLabels XRPC endpoint and can be queried by any AT Protocol client.
- —Each label is signed with ed25519 and includes: source DID, target DID, label value, timestamp, and a cryptographic signature.
- —Apps can subscribe to the labeler to automatically receive quality signals for hypercert activity records and filter or sort them by tier.
- —Only one quality label is active per DID at a time. When a record is updated and re-scored, the previous label is negated before the new one is applied.