Public support should come with a receipt.
For city housing staff: check the affordable-housing commitments a developer made in exchange for a tax break or other public support, with the source page one click away.
Residents, reporters and council members can read the same receipts, every claim with its page.
AI readsCode checksPeople decide
Promise receipt
Harbor Walk · Lantern Bay
- Homes12 affordable homesQuote found · p. 1
- Income limit80 percent of area median incomeWording differs
- Term15 yearsWording differs
- RemediesNo wording foundNot located
16 of 16 quotes found word for word on their cited pages.
Live from public records
Prince George's County, read by Promise Ledger
- Agreements read
- 0
- Affordable homes stated
- 0
- Approved with blank template text
- 0

The problem
Promises get lost between documents.
-
One promise, five documents
report · letter · slides · minutes · agreement
-
Wording drifts
60% → 80% of AMI before signing
-
Deals outlast staff
30-year terms, many hand-offs
How it works
From a stack of PDFs to one receipt.
- UploadDrag in the PDFs
- ReadAI finds each promise
- CheckCode matches every quote
- ReceiptShare, print or export
Proof
Checked against hand-reviewed answers.
-
94%
precision: kept quotes that match a hand-checked answer
-
96%
recall: hand-checked claims that were found
-
0
incorrect “signed” or “delivered” labels
-
3
sample deals · 11 PDFs · 53 claims
-
≈ $0.003
model cost per document
On sample data: our development set of 3 made-up deals, not a held-out test. Scores from evals/run_pdf_evals.py, compared with 53 hand-checked claims.
Learn the basics
A full overview, then eight short explainers, under a minute each, with captions.

Full overview · 2:20
Promise Ledger in two and a half minutes
The whole flow on the live site: reading a deal’s PDFs, checking every quote on its page, what changed between records, who decides, reminders and the receipt.
Watch on YouTube (opens in a new tab)
The player loads from YouTube only when you press play.
-
Coming soon
-
Coming soon
-
Coming soon
-
Coming soon
-
Coming soon
-
Coming soon
-
Coming soon
-
Coming soon
Who it’s for
One record everyone can read.
City housing staff
Check every commitment against its page before a deal moves on.
Council members
See what changed between the staff report and the signed agreement.
Residents
Read what was promised for your neighborhood, with the page it came from.
See a deal checked, start to finish.
Open a sample dealAbout
Who built Promise Ledger
Built by Liyue Housing Association, a two-person student team, for GDG AI for Good 2026: Housing.
-
Mukul Rayana
Designed and built Promise Ledger
The project
- Event
- GDG AI for Good 2026: Housing
- First submission
- Nov 9, 2026
- Final
- Dec 2, 2026
- License
- Code Apache-2.0 · docs and demo data CC BY 4.0
- Data
- The sample deals are made up. The County page reads real public records of Prince George's County, Maryland.
- Cost
- Reading all 811 pages of the county records once cost about $0.60 in model use, about $0.75 per 1,000 pages. Each record is read once and cached.
What we keep, and what we don't
- Not kept: questions asked in Ask a deal and Ask the county are not saved or logged.
- Kept: deals and records you upload to the public demo (deleted after 24 hours), reviewer decisions with the name and note you enter, and answers to the tester form.
- Before the model sees text: phone numbers, email addresses and Social Security numbers are removed.
- No accounts and no ads. Fonts load from Google Fonts; the overview video loads from YouTube only when you press play.
Known limits
- Council files usually hold the approved agreement, not the signed copy, so most county end dates are counted from the Council's adoption and read "or later".
- "Not found" means no wording was found in the records read. It is a question to ask, never a finding that a term is missing.
- Five county agreements state no street address, so they are listed beside the map, not placed on it. Four sites are located to the street only.
- Scanned pages are transcribed by AI and marked; their quotes should be checked against the PDF.
- English records only, for now.
Help us test Promise Ledger
About 15 minutes. You will look up one real housing deal twice, once on the county's own site and once here, then tell us what worked. Please don't type personal details into the answers.
Thank you.
Your answers were saved. They help us make Promise Ledger useful for the people who check these deals.
Roadmap
Why it matters, and where it’s going
Six short answers. Pick one, or read the full guide (opens in a new tab).
Promises for public support are easy to make and hard to follow
- 2M+ assisted rental homes with affordability terms due to end, 2014–2024 Harvard JCHS (opens in a new tab)
- “Inadequate” a city audit’s word for oversight of promised benefits from housing tax breaks Portland City Auditor, 2008 (opens in a new tab)
- 35 look-ups to check 7 terms across 5 records of one sample deal by hand Harbor Walk
- Staff summary60% · 30 yrs
- Draft letterup to 12 homes
- Slides80% · 15 yrs
- Minutes5–2 vote
- Signed letter80% · 15 yrs
One promise, five records, and the terms shift on the way.
Three moments, on the sample deals
-
Before a vote Council aide
Harbor Walk
- Proposed
- Supported
- Signedone party
- Delivered
60% → 80% of AMI, 30 → 15 years. Only the developer signed.
-
Years later Compliance officer
Mill Street
- Proposed
- Supported
- Signed
- Delivered
9 homes protected until Dec 31, 2026. This year’s certificate isn’t on file.
-
All in order Staff reviewer
Beacon Point
- Proposed
- Supported
- Signedboth parties
- Delivered
All 7 terms match. Good news is stated as plainly as a gap.
Residents and reporters get a read-only receipt link with every quote and page.
Promise by promise, with the page as proof
| PDFs and a spreadsheet | AI chat over PDFs | Housing databases | Promise Ledger | |
|---|---|---|---|---|
| Every promise, every record | By hand | One question at a time | No | Yes |
| Exact quote, checked on its page | If someone checks | Varies | No | Yes |
| Stage: proposed to delivered | If someone tracks it | No | Project status only | Yes |
| Changed or missing terms | If someone notices | Only if asked | No | Yes |
| Who signed | By hand | No | No | Yes |
| Decisions kept with names | No | No | Yes |
Kinds of tools, not named products. Some tools do parts of this.
The model is one step of eight
- CodeRead pages
- CodeRedact
- AIPropose quotes
- CodeVerify on page
- CodeSet stage
- CodeCompare records
- PeopleDecide
- OutputReceipt and share
- No quote on the page, no claim
- Stages from rules, not the model
- Neutral labels, no legal findings
- Only redacted text reaches the model
- Demo uploads deleted in 24 hours
Stack: Python, FastAPI, pypdf, Gemini with structured output, Firestore, Cloud Storage, Cloud Run.
Measured on our sample set
- 94.4%precision
- 96.2%recall
- 100%correct page
- 0wrong “signed” or “delivered”
- $0.003per sample PDF
- 258automated tests
What it is. 3 made-up deals, 11 PDFs, 53 hand-labeled claims. The rules were tuned on this set.
Not yet. Held-out records, real public records, scans, time saved for real staff.
Built today, and where it goes next
36 features live today · 494 automated tests · 1 more by the Dec 2 final · 4 after
Live today
Reading and checking7
- Reads every PDF in a deal’s packet
- Quotes checked word for word on their page
- Wrong pages corrected; unprovable quotes dropped
- Stages set by rules, proposed to delivered
- One-party signing flagged
- Scanned pages read; a person confirms signatures
- Names the records to ask for next
Review and sharing7
- What changed, word by word
- Missing terms and certificates found
- Reminders for term ends and certificates
- Decisions with name, note and time
- Printable receipt with a review stamp
- Read-only links for residents
- Excel and CSV export
Real county records10
- 21 Prince George’s County agreements
- 811 pages: about 27 h by hand, about $0.60 here
- County board: homes, income, terms
- Template blanks flagged with the quote
- Night map at the stated addresses
- Search every agreement by meaning
- Calendar of term ends with heads-ups
- Records-request letters to send
- Share links that unfurl with numbers
- One-page council brief
Ask5
- Ask a deal, for staff or residents
- Ask and listen by voice
- Ask the county: one question, 21 agreements
- Recommends agreements and next questions
- Counts by code, repeats from memory: $0
Trust and reliability4
- Redaction, injection guard, sandboxed PDFs
- Tested on unseen and planted-attack records
- Runs without a key; about $0.002 per PDF
- Self-healing: retries, restores, offline
Access3
- Keyboard, contrast, larger text, dark mode
- Light on low-end phones
- 60-second tour and 8 captioned explainers
By the Dec 2 final
- Feedback and a timed task with housing staff and residents (help us test)
After
- Follow-up letters once a request is answered
- Spanish and other languages
- Reads handwriting on scans
- More counties; cross-checks with HUD’s tax-credit data
Every assistant keeps the same rule: it answers only from checked quotes, shows the page, and a person approves anything it sends or saves. Details are in the full guide (opens in a new tab).
Want to try it on your own records, or help test it? Reach us through the About page.