PRIORITY.
unppps used to carry a hand-set priority field in config. This page replaces that with an effort-driven score — config completeness plus real, recency-weighted commit activity — built to help answer the question this whole investigation started with: what does unparty-app actually focus on?
HOW IT'S CALCULATED.
| KEY | SOURCE | MEASURES |
|---|---|---|
| URL | UnpppsConfig.json → url | Deploy tier — unparty.app (4) > TestFlight (3) > vercel.app (2) > other (1) > none (0). |
| CORE | UnpppsConfig.json → id | Flat bonus if the id is one of the 6 repos confirmed wired into the architecture (issue #621): theunpartyapp, theunpartyapi, theunpartybuilder, theunpartycore, theunpartycrawler, theunpartyrunway. |
| PRODUCT | UnpppsConfig.json → id | Flat bonus for shipped consumer-facing products (theunpartyunppp, theunpartycharette). |
| KEYS | UnpppsConfig.json → 25 expected fields | How much of the config is actually filled in — story metadata, branding, pricing, etc. |
| ACTIVE | raw-repo-metadata.json → enhanced_metrics.active_period_metrics | Weeks with commits, burst weeks, active-period ratio — is this repo consistently worked on, or was it a one-time push? |
| BOUNDED | raw-repo-metadata.json → enhanced_metrics.time_bounded_commits | Recency-weighted commit volume — last 5 days weighted 2x, last 30 days weighted 0.3x. Answers "what is being worked on right now." |
| REPO | ACTIVE + BOUNDED | The real-activity half of the score, matched to each unppp via the unppp_id field (issue: theunpartycharette’s repo is actually named uncolor-ios — matching by name alone silently dropped it until repo-metadata-analyzer was fixed to preserve the match). |
| COMBINED | UNPPP total + REPO total | The single sortable number PriorityTable ranks by — config completeness and shipped-ness, plus what is actually being built right now. |
WHAT IT'S ALREADY SURFACING.
theunpartyapp and unparty-docs lead on combined score — consistent with #619 and #620 finding that 2026's center of gravity moved from mobile toward the web platform and its documentation layer.
theunpartyunppp sits mid-pack despite its PRODUCT bonus — the ACTIVE/BOUNDED columns are where its -54% YTD slowdown (#619) actually shows up as a number, not just a narrative claim.
CORE-bonus repos (theunpartyapi, theunpartybuilder, theunpartycore, theunpartycrawler, theunpartyrunway) — the wired architecture confirmed in #621 — cluster together on REPO score too, which is itself a small piece of evidence that "architecturally load-bearing" and "actively worked on" correlate here, rather than being two unrelated claims.
Rows marked unmatched have no corresponding entry in raw-repo-metadata.json — either genuinely no repo yet, or a repo/id mismatch this page hasn't caught. theunpartycharette was exactly this bug until its repo-metadata-analyzer fix landed — worth treating every unmatched row as a question, not a zero.