Intake · synthetic data · live

Feature requests, prioritized with a receipt.

Type what a customer or team is asking for. It gets shaped, de-duplicated against everything already in flight, scored on reach, impact, effort, and urgency — and every score comes with a receipt you can re-run. When a request is too vague to score honestly, it says so instead of guessing.

Deterministic · keyless · receipted — same words, same score.
Try

The structured fields (area, persona, impact, effort, reach, confidence) come from the intake form a real submitter fills. Leave them off and the engine will tell you what it needs rather than guess.

Scoredin a 4-request cluster
76priority — reach × impact × confidence ÷ effort, weighted by urgency
Duplicate check (by meaning)

Looks like a duplicate — it lands in a 4-request cluster already in flight.

shared meaning:sso
What it understood
IntentEnhance
Product areaAccess & security
Who it servesAccount admin
SegmentEnterprise
UrgencyCritical
ImpactTransformational
EffortL
Reach / quarter5,200
RegulatoryNone
How it scored — the receipt
Score breakdown
Reach score72.111
Impact score9.45
Effort (wks)8
Confidence0.8
Urgency ×1.7
Raw priority115.8464

DISPLAY( (reach_score × impact_score × confidence_score) / effort_score × urgency_weight ) → 0..100, order-preserving log map

Signed record
receipt sha3a7bf3e248a9cee9f406769a0ab2e12a1b3cf8e40f1a89ee547cc592610a5ea6
payload shadc579e226257127f7ae447ec9772219744b6aed35310117ba1afce0faed41b55
request fingerprint0761dc55a3b3bc3958054aeaa01c515a3dbbfdaa16ece3a905c87a1994bfc896
model fingerprintd8cd441f1240f7c718d67ae7d7595cf19f21d8340cd65c498fdcb5cdcc1a7452
ledger entry shacfe116fa5bee8fcbda225442b9c017e25650f79c7db6258f2cd33f1afe35c98e

Re-run the same request and every hash above is identical. Each entry is hash-chained to the one before it — change a past decision and the chain breaks.