Glossary

API endpoint that evaluates user eligibility for a float advance.

API endpoint that evaluates user eligibility for a loan product.

Lambda function that executes business rules against user data. Triggered by SQS messages from the API Lambda.

Lambda function that aggregates rule outcomes into final eligibility decisions. Triggered after all rules have been evaluated.

Lambda function that creates historical evaluation records when a float is successfully disbursed.

Lambda function that manages default FloatProfile creation for new users.

A single business logic check that evaluates one aspect of user eligibility (e.g., account age, deposit frequency, balance requirements).

Go interface (Rule) that all business rules must implement, defining Execute() and Name() methods.

A YAML-defined collection of rules with a priority level and configuration. Multiple rulebooks can exist for A/B testing or different user segments.

The result of executing a single rule, stored in DynamoDB with pass/fail status and reasoning.

The final aggregated outcome of all rule executions for a given eligibility check, including approved/denied status and the deciding rulebook.

Rulebook logic where certain mandatory rules must pass regardless of other rule outcomes. Used to enforce critical eligibility requirements.

Rule-specific configuration values defined in rulebook YAML files (e.g., minimum account age in days, required deposit count).

Continuous Float Increase - a system that automatically increases user float limits based on positive repayment and subscription history.

A score from 0-8 based on the user’s history of successful float repayments. Higher ranks qualify for larger float amounts.

A score from 0-8 based on the user’s history of completed subscription payments. Used in combination with Float Rank for CFI eligibility.

A table of criteria that determines CFI eligibility. Each row specifies minimum Float Rank, Subscription Rank, balance, and previous float requirements for a given tier.

Boolean flag on FloatProfile indicating whether the user is enrolled in the Continuous Float Increase program.

DynamoDB entity storing user float eligibility configuration, CFI status, ranks, and limit information. Primary key: PROFILE#{userId}.

DynamoDB entity representing the outcome of a complete rules evaluation. Includes approval status, deciding rulebook, and timestamp. TTL: 32 days.

DynamoDB entity storing the result of a single rule execution. Includes pass/fail status, rule name, and detailed message. TTL: 32 days.

DynamoDB entity that temporarily overrides a user’s FloatProfile settings for testing or special cases. Has a configurable TTL.

DynamoDB entity caching rulebook configurations to reduce load times. TTL: 60 minutes.

Pattern where eligibility checks return HTTP 202 immediately and process rules asynchronously via SQS. Clients poll for results.

When a recent evaluation result (< 7 days old) exists and can be returned immediately without re-running rules.

When no recent evaluation exists, triggering the async rule evaluation pipeline.

Design principle ensuring that processing the same event multiple times produces the same result without side effects.