Try it
This calls the live rules engine on Google Cloud Cloud RunWhat it is. Google Cloud's service for running containers. Each release of the rules engine becomes a tagged revision.Why it matters. Old revisions stay addressable, so a past decision can be re-run against the exact code that made it. Deployed by the GitLab pipeline with no stored keys., the same one the pipeline deploys. Enter a household and see the decision with every step and its citation. The incomes and costs you enter are not stored or logged; for monitoring, the engine records only each decision's month, household size and result in GitLab Observability.
The decision will appear here.
Show the API call
curl -X POST https://decider-1049098106598.us-central1.run.app/decide \
-H 'content-type: application/json' \
-d '{...}'Full reference: https://decider-1049098106598.us-central1.run.app/docs
Check your own decisions
Already running a benefits system? Upload decisions it made, with what it paid, and Lookback recalculates each one under the law. You get back who was underpaid and by how much, who was wrongly denied, and which months are past the twelve-month limit. Overpayments are listed for a person and never totalled as a debt. Nothing you upload is stored; the file goes straight to the rules engine and the answer comes straight back.
Columns: id, household_size, period (YYYY-MM), earned_income, unearned_income, shelter_costs, medical_expenses, dependent_care, child_support_paid, elderly_or_disabled, homeless, categorically_eligible (yes or no), recorded_eligible (yes or no), recorded_amount. Dollar amounts per month. Up to 10,000 rows. The sample households are constructed.
Bring your own
Your rules
Any service that answers POST /decide with eligibility, an amount and reason codes, and GET /version with a digest, can be replayed by Lookback. The contract is in the technical design.
Your GitLab project
The flow is published in the AI Catalog as "Lookback: appeal to fix". Enable it on your project, add the mention trigger, and copy the lookback stage from .gitlab-ci.yml.
Your data
Check past decisions above, or call POST /check directly. For the full loop, a decision ledger is JSONL with inputs, outputs and the code version per record; lookback/record.py shows the shape and ledger.cli verify checks the chain.