Skip to main content

Bill8:Risk — Business Requirements & Functionality

Audience: product owners, business analysts, and anyone evaluating what Bill8:Risk does for the business. For architecture read README.md; for wire-level detail read DESIGN.md.

1. Business Purpose​

Bill8:Risk is the fraud-prevention layer. It delivers:

  • Pre-authorization screening — charges are screened before money moves, so a block prevents a bad charge rather than flagging it after.
  • Review queue — suspicious charges route to manual adjudication.

2. Business Scope (What the Service Provides)​

#CapabilityWhat the business gets
1RulesDeclarative predicates + actions
2ScreeningsAuditable evaluation results
3ReviewsManual adjudication queue

What the service does NOT own (business boundary):

Out of scopeOwned by
Payment executionBill8:Payments
Money movementBill8:Ledger

3. Business Capabilities​

CapabilityBusiness rule
Screen a chargeRules evaluate before money moves
ReviewA suspicious charge routes to manual adjudication

4. Business Events (Outbound)​

EventFires when
rule:created/updatedRule changes
screening:createdA screening runs
review:opened/resolvedA review lifecycle changes

5. Business Rules & Invariants​

  1. A rule's action is applied before the charge commits.
  2. Screening fails closed on evaluation error.

6. Target-User Roles & Use Cases​

PersonaDoes
MerchantConfigure rules
OperatorReview and adjudicate

7. KPIs / Success Criteria​

KPIMeasure
Fraud catch rateblocked/reviewed vs attempted
False-positive ratewrongly blocked / blocked

8. Dependencies & Reliance on Other Services​

RelianceOn
Event transportSentin8:Bus

9. Acceptance Criteria​

  1. A rule can block or review a charge before money moves.
  2. A review resolution propagates back to the charge.

10. Open Business Questions​

  • See backlog.md RSK-*.

Design attribution: bill8:risk and its underlying concepts were designed by Hamid Jahanzad Hamid@Jahanzad.com.