Triage board · synthetic data · live

Ranked by priority, with a receipt

The ranked board — every request with its score, tier, and duplicate flag.

22ranked rows6duplicate clusters · 10 held5held for review / refused37requests in flight
TierRanked by priority_score — not upvotes. Duplicates collapsed.
Now· 6
1
76score
Enterprise accounts need SSO via SAML so their admins can enforce single sign-on for all users
Access & securityAccount adminSales5,200 reach/q 3 requests · cluster
Now
2
72score
Add an audit log in the admin console so account admins can see who changed what, for SOC 2
Access & securityAccount adminCompliance1,700 reach/q regulatory
Now
3
72score
PCI-DSS: stop showing full card numbers anywhere in the billing admin views
BillingInternal operatorCompliance800 reach/q regulatory
Now
4
71score
Add MFA (two-factor) enforcement that account admins can require for all users in their workspa…
Access & securityAccount adminCompliance4,100 reach/q
Now
5
71score
Let support agents trigger a password reset notification email for an end customer from the adm…
NotificationsSupport agentSupport6,200 reach/q
Now
6
70score
Customers keep asking to export invoice data to CSV for their own accounting
BillingAccount adminSupport9,000 reach/q 4 requests · cluster
Now
Next· 7
7
69score
Add autocomplete to the search box so support agents find accounts faster
SearchSupport agentSupport4,800 reach/q 2 requests · cluster
Next
8
69score
Add a getting-started setup wizard to onboarding so new end customers activate faster
OnboardingEnd customerProduct14,000 reach/q
Next
9
69score
Send a push notification to end customers on the mobile app when their order status changes
NotificationsEnd customerProduct26,000 reach/q
Next
10
68score
Add an in-app onboarding checklist for account admins so they finish workspace setup
OnboardingAccount adminCustomer success5,400 reach/q
Next
11
66score
Bulk add users by uploading a CSV to the management console — onboarding big teams one user at…
Admin consoleAccount adminSales2,100 reach/q 2 requests · cluster
Next
12
64score
GDPR right-to-be-forgotten: let account admins delete a customer's personal data on request
Access & securityAccount adminCompliance1,200 reach/q regulatory
Next
13
61score
Add role-based access control so account admins can scope what support agents can see in the ad…
Access & securityAccount adminCompliance1,900 reach/q
Next
Later· 8
14
54score
Add a REST API endpoint so developer partners can pull reporting data programmatically
Integrations / APIDeveloper / partnerPartnerships900 reach/q 2 requests · cluster
Later
15
53score
Let finance teams schedule a recurring bulk data export of billing records to their data wareho…
Data exportFinance teamCustomer success1,300 reach/q
Later
16
53score
Add a dark mode theme to the mobile app for end customers who use it at night
Mobile appEnd customerProduct22,000 reach/q 3 requests · cluster
Later
17
51score
Add saved search filters so support agents can re-run common account lookups in one click
SearchSupport agentSupport3,900 reach/q
Later
18
48score
Let end customers export their own activity history as a downloadable CSV from the mobile app
Data exportEnd customerProduct15,000 reach/q
Later
19
47score
Let account admins white-label the onboarding emails with their own logo for end customers
OnboardingAccount adminSales1,000 reach/q
Later
20
47score
Add a weekly email digest of key reporting metrics for finance teams
NotificationsFinance teamCustomer success2,800 reach/q
Later
21
44score
Add a customizable analytics dashboard so account admins can pick which reporting widgets they…
Reporting & analyticsAccount adminProduct2,600 reach/q
Later
Backlog· 1
22
38score
Build a Zapier connector so developer partners can wire our events into their own workflows
Integrations / APIDeveloper / partnerPartnerships1,100 reach/q
Backlog

These requests can't be honestly scored yet — they're missing material fields or ground to more than one meaning. The engine returns REVIEW or REFUSE with the exact gaps, instead of guessing a number.

Needs review
Send an email alert when an invoice payment fails so the finance team knows about the billing p…
Grounded with ambiguity — held for a human, not scored on a guess.
What needs disambiguating
  • product areaRequest touches multiple product areas; cannot bind one.
  • A human reviewer can disambiguate the flagged field(s); re-ground once a single value is chosen.
The refusal is receipted too
Signed record
receipt shaf8341469d0aeaad7383634c1d21da71fbb4fe4588f6e0316739f87c02295f4fa
payload shad5a4aeae78b47b1a545459dc8a78c8c82e39e0a3a358662b5ec242c7d95fa640
request fingerprintfb6bd89964c1ed1f8b56f4dd8842bfcfd86442bbca8a3663d18b950368e874aa
model fingerprintd8cd441f1240f7c718d67ae7d7595cf19f21d8340cd65c498fdcb5cdcc1a7452
ledger entry sha7234ab54dfa0eba85d88148ac48c8742860a0900e200a26ea84b304142f91948

A refusal is a first-class, hash-chained outcome — the decision not to fabricate a score is itself on the ledger, re-provable byte-for-byte.

Needs reviewSearch
Search should be faster for both the support agent and the developer partner using the lookup
Grounded with ambiguity — held for a human, not scored on a guess.
What needs disambiguating
  • personaRequest names multiple personas; cannot bind one.
  • A human reviewer can disambiguate the flagged field(s); re-ground once a single value is chosen.
The refusal is receipted too
Signed record
receipt sha1b54b961f3fcbfa1f94ad0ed2a1826768870554609d3e60fca577bfeff53e77f
payload sha1f930c22ce6ce0152c90adddc2978063fcf52ed80d23cf8070b5e36167b93ce5
request fingerprintd29465f0009f13b0807da7ab5e756b38cdc6058369391f0856baaaf8df3e3558
model fingerprintd8cd441f1240f7c718d67ae7d7595cf19f21d8340cd65c498fdcb5cdcc1a7452
ledger entry sha28f3740c1cd43c264e890aa54c56929cc75f2a3e227d466e11b2f63866151679

A refusal is a first-class, hash-chained outcome — the decision not to fabricate a score is itself on the ledger, re-provable byte-for-byte.

Can't score yetReporting & analytics
Make the dashboard better
Missing 5 required fields — refused a score rather than fabricate one.
What's missing
  • delivery confidenceDelivery confidence not provided (0.5 / 0.8 / 1.0).
  • effort bandNo effort signal — cannot size build cost without guessing.
  • impact bandNo impact signal — cannot size business impact without guessing.
  • reach users per quarterNo reach figure — cannot compute how many users are affected.
  • value confidenceValue confidence not provided (0.5 / 0.8 / 1.0).
  • Provide the missing field(s) on the request, then re-run.
  • Do not estimate the missing value — source it or leave the request in REVIEW.
The refusal is receipted too
Signed record
receipt sha75e8ec55ade1ff714a7771157415ee00ea87872e361b4ddafe59506015e24605
payload sha2ef88396769300323b2a4bc04514eb84876c32375c56149e420483a1cce9082f
request fingerprint0c3093d3e45e21b336e754ebb9d259b5bd8a1ac22486d5ed0499979501706945
model fingerprintd8cd441f1240f7c718d67ae7d7595cf19f21d8340cd65c498fdcb5cdcc1a7452
ledger entry shab42675bd1c7513eb37e21212cfa900d4eecea38de61673a32f7faca7c5804e64

A refusal is a first-class, hash-chained outcome — the decision not to fabricate a score is itself on the ledger, re-provable byte-for-byte.

Can't score yet
It would be nice to improve the overall experience for everyone somehow
Missing 5 required fields — refused a score rather than fabricate one.
What's missing
  • effort bandNo effort signal — cannot size build cost without guessing.
  • impact bandNo impact signal — cannot size business impact without guessing.
  • personaCould not identify which user/persona this serves.
  • product areaCould not bind the request to any governed product area.
  • reach users per quarterNo reach figure — cannot compute how many users are affected.
  • Provide the missing field(s) on the request, then re-run.
  • Do not estimate the missing value — source it or leave the request in REVIEW.
The refusal is receipted too
Signed record
receipt shac0da4e841ef74af1b196e6b62e5e3ed0abde3670e68b860d47cd8333ce865a3a
payload shabd8149d4da47a2264c4e3e44b26e2151480a232886092287a23dfa60f6fa4c84
request fingerprint42fa0c9d9598f49c20e4ddce7d4ef9fa905e1814c6e5ed4194d09652a32d5ed3
model fingerprintd8cd441f1240f7c718d67ae7d7595cf19f21d8340cd65c498fdcb5cdcc1a7452
ledger entry sha63f9f3f01109d31312816593d934ccf1093279c9ed16e73b4ecb5bb60598a1eb

A refusal is a first-class, hash-chained outcome — the decision not to fabricate a score is itself on the ledger, re-provable byte-for-byte.

Can't score yetReporting & analytics
Add more reporting filters to the analytics dashboard for the finance team
Missing 3 required fields — refused a score rather than fabricate one.
What's missing
  • delivery confidenceDelivery confidence not provided (0.5 / 0.8 / 1.0).
  • reach users per quarterNo reach figure — cannot compute how many users are affected.
  • value confidenceValue confidence not provided (0.5 / 0.8 / 1.0).
  • Provide the missing field(s) on the request, then re-run.
  • Do not estimate the missing value — source it or leave the request in REVIEW.
The refusal is receipted too
Signed record
receipt shab828ec5521e84caa4a637728c5ffe9919ddcdcd974baccdb9a5fdbdd9aa67ee1
payload shaf69f81819d434eeed3324e2456dab7582eff08ba715f16f035726a59591cfeb0
request fingerprint0534aea1e720e3bee10e72e80c3af3d5098491df1f5c28a731bda52dec11cef8
model fingerprintd8cd441f1240f7c718d67ae7d7595cf19f21d8340cd65c498fdcb5cdcc1a7452
ledger entry shafcf25a71530d36421e047aef31ff03bca1ce13b38e65279ae045fef2a52260dc

A refusal is a first-class, hash-chained outcome — the decision not to fabricate a score is itself on the ledger, re-provable byte-for-byte.

How this board is built

Every row is ranked by the deterministic priority_score — a 0–100 log-map of reach × impact × confidence ÷ effort, weighted by urgency — computed by the governed model, not by votes. Near-duplicates are collapsed by meaninginto one cluster row, represented by the highest-scoring member; expand a clustered row to see every member and the engine's keep / hold call. The tier buckets are a reading lens over the same score:

Nowscore ≥ 70
Next55–69
Later40–54
Backlog< 40
Provenance
governed model fingerprintd8cd441f1240f7c718d67ae7d7595cf19f21d8340cd65c498fdcb5cdcc1a7452
ledger head sha28f3740c1cd43c264e890aa54c56929cc75f2a3e227d466e11b2f63866151679

The ledger verdict is PASS across 37 entries — every scored, reviewed, and refused outcome is hash-chained. Re-run the corpus and every score, cluster, and hash on this board is identical.