Bow Tie Kreative Intel System
Score something

File 11, executable

Score something

Weights and point ceilings come from the corpus, so the number here is the number the documentation describes. A dimension you leave unscored is reported as missing — it is never counted as a zero.

Finding quality scoreOpportunity priority scoreAuthority scoreLead qualification score

Opportunity priority score

BaseOpportunityScore = weighted sum x 20; RiskAdjustedPriority = Base x ConfidenceFactor x (1 - RiskPenalty) · output 0-100

quality of the underlying finding
plausible contribution margin, cash, risk, or capacity effect
ability of the offered service to address the mechanism
connection to named role and public priority
moves beyond table-stakes improvement
how quickly a test can confirm/refute value
ability to stop or recover
likely operational feasibility
cost/risk of delay or time-bound window
non-obvious but appropriate
inputs available to size or test

Hard gates

Answer every one. A failed gate blocks the opportunity regardless of the number.

Fails when: unresolved identity
Fails when: prohibited source/use
Fails when: sensitive-personal-data dependence
Fails when: exploit or credential dependence
Fails when: misleading financial claim
Fails when: no plausible service-to-mechanism fit
Sets the confidence factor in the risk-adjusted priority.
Legal, privacy, security, execution, brand and dependency risk. Maximum 0.6.
Reset

What this does not do

A high score never overrides a hard gate, and nothing here stores what you type. The calculation happens on this request and is gone when the response ends.

How the rubrics are defined GET /v1/scoring/opportunity