Real Estate AI agent · Affordable housing
Affordable-Housing Compliance AI Agent
Build the evidence file behind each household under the programme rules that unit sits in, run the correction clock the agency opens, and hold the annual pack for the owner, who certifies.
- Typical delivery
- 4–6 weeks
- Deployment
- Your stack
- Agency-set date
- Owner certifies
- After launch
- Agent Care
What this agent does
Builds the file, not the certification
In
- 01
A household moves in, and the certification evidence behind that occupancy is pulled from the system of record.
- 02
A recertification falls due, and the anniversary, the notices sent and the verifications are lined up against it.
Reason
- 03
A household income passes the applicable limit, and the available unit rule at §42(g)(2)(D)(ii) goes on watch.
- 04
A unit is read against the set-aside elected on Form 8609 Part II, not the designation typed in the rent roll.
- 05
A utility allowance changes, and the gross rents it touches are re-checked on the 26 CFR 1.42-10 clock.
Decide
- 06
A verification ages past what the allocating agency will accept, and the gap is flagged rather than filled.
- 07
A finding lands, and the agency correction period runs as a dated clock into the Form 8823 window behind it.
Out
- 08
A file closes and is kept on its own rule — six years, or twenty-one where it is a first-year household file.
- 09
Execute write actions only inside the approval boundaries agreed during implementation.
Product statement
The agent assembles the evidence; the owner certifies on all twelve propositions in 26 CFR 1.42-5(c)(1), under penalties of perjury.
Example workflow
One household, move-in to certification
- 1Household file receivedTenant income certification, verifications, lease and unit designation
- 2Evidence assembledIncome and asset verifications, the utility allowance in force and the set-aside of record
- 3Status proposedUnit status, cited evidence and confidence
- 4Controls appliedProgramme-rule checks, agency dates and correction clocks, staleness tests and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nothing is certified at any of them — the agent is assembling, and the owner lane opens at the confidence gate.
Goes to the named owner representative.
Adds a compliance-manager read first.
Owner sign-off
The file is held with its cited evidence, its open gaps and the confidence.
Approve · Amend · Send to compliance review
Approved — released to the pack
- 6Compliance systems updatedOnly where write access and approval policy allow it
- 7Outcome evaluatedEvidence completeness, agency findings, correction outcomes and post-certification amendments
Amendments
Each amendment made in review is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required
8 items
- Certifying annual compliance to the allocating agency.
- Determining whether a household qualifies for a unit.
- Making or altering the minimum set-aside election.
- Signing Form HUD-50059 or any owner certification.
Automation boundary
Agent acts unaided
- ✓Assemble the income and verification evidence behind a household.
- ✓Show unit and building status against the test on file.
- ✓Run the clocks the agency sets, and mark what has slipped.
- ✓Flag the gap the reviewer must close, and hold the file open.
Writes land inside the boundaries agreed at implementation, and never ahead of the owner signature.
- Deciding to terminate assistance or a tenancy.
- Setting the utility allowance a building will use.
- Answering an agency finding for the ownership entity.
- Changes to programme, agency or retention rules.
Example output
One household file, annotated
Everything the agent assembles stays attached to the record it came from, and stays after certification.
Compliance-file output · single household
Illustrative example- Household
- Two-bed credit unit
- Proposed status
- Recertification due; income now above the applicable limit
- Verification age
- 11 months
- Evidence of record
- Employer verification
- Confidence
- 89%
- Rule applied
- Indiana LIHTC — HOTMA from 1/1/24
As received
Taken from the tenant file and the verification in it — nothing on this side is written by the agent.
Evidence cited
- Employment verification
- Prior certification
- Utility allowance sheet
Why this status
The unit holds its status only if the next comparable unit is let to a qualifying household — §42(g)(2)(D)(ii).
What the score decides
Below the configured threshold the file picks up a compliance-manager read before the owner sees it.
Action
ApproveAmendSend to compliance reviewValue
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value lands
Value 01 – 04
Every household
From the tenant file
Build from the file, not the ledger
Ask whether the rent could lawfully be charged under the programme, not whether the household paid it.
Perjury sits on the owner
Recertification evidence for households already in place arrives assembled and dated.
Send review where the risk sits
Open findings come first, because the agency files Form 8823 after the correction period ends, corrected or not.
Build an evidence trail
The household, the evidence beneath it and the owner who certified stay on the file.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Property management
- Yardi Voyager
- RealPage
- MRI
- Entrata
Affordable compliance
- Yardi Affordable
- Bostonpost
- Tenmast
- Emphasys Elite
Agency and HUD systems
- HUD TRACS
- iMAX
- Agency compliance portals
Agent
Affordable-housing compliance
- Reads the file
- Assembles the evidence
- Holds for sign-off
Documents and retention
- Tenant files
- certifications
- SharePoint
- document stores
Observability & evaluation
- OpenTelemetry
- Langfuse
- Supported monitoring/evaluation sources
Integration availability depends on the client's existing systems and API access.
Agent controls
Six layers between the model and the certification
Six shells, read outermost first. What none of them holds is named in the map below.
L6 · Outermost — last line of defence
Inward → L1 · closest to the model
- L1 – L2
- Test whether a file may stand
- L3
- Puts the signature in an owner's hands
- L4 – L5
- Keep the household and the evidence behind it
- L6
- Holds the file at uncertified when signals degrade
How Nestack evaluates it
Evaluate the whole compliance cycle — not only the finished pack.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the pack the agency reads
- E1Final-output evaluationDid each proposition in the pack rest on evidence cited in the file?
- E2Step-level evaluationDid the agent use the right programme, agency calendar and rule version?
- E3Tool evaluationDid it read and write the correct household and the correct unit?
- E4Confidence calibrationDo low-confidence files actually attract more reviewer amendments?
- E5Slice evaluationHow does performance change across specific set-aside and household types?
- E6Business outcomeHow many files needed an amendment, or a correction after the owner had certified?
Floor — the outcome the owner answers for
Failure modes
Where each failure originates in the agent
Seven failure modes, each placed at the stage where it starts.
Agent lifecycle
Direction of processing →
01 · Retrieval
1 mode
- FH-03
Stale verification
Income read from a verification the agency will not accept.
Stage gathers
Tenant files, verifications, elections and agency rules
02 · Reasoning
2 modes
- FH-04
Available-unit blind spot
A comparable unit is let while a household sits over the limit.
- FH-06
Wrong set-aside test
Status measured against a test the owner never elected.
Stage proposes
Unit status, cited evidence, gaps and confidence
03 · Tool / write
2 modes
- FH-02
Clock templated too long
Correction window run on the federal ceiling.
- FH-05
Early retention purge
A first-year file goes on the general schedule.
Stage writes
Only where write access and approval policy allow it
04 · Output
1 mode
- FH-01
Uncited proposition
A certified statement rests on evidence not in the file.
Stage returns
The file the owner certifies and the agency reads
05 · Change / Version
1 mode
- FH-07
Silent rule drift
A rule or calendar change widens what the file will assert.
Stage tracks
Model, prompt, programme rules and agency dates
- Sev-1 · a file leaves the boundary
- Sev-2 · a wrong status reaches the pack
- Sev-3 · evidence ages, file routes to review
Affected slices
One set-aside can carry most of the exposure
A property-level evidence-completeness figure can read well while one set-aside or household type carries most of the open gaps. Nestack reports completeness by slice, not only in total.
Slice performance — reported separately, not only in aggregate
Illustrative example| Slice | Failure rate | Lift | Lift vs. threshold | Status |
|---|---|---|---|---|
| Over-income households | 8.7% | 3.7× | Review | |
| Average-income set-aside | 6.4% | 2.7× | Review | |
| Mixed-finance households | 3.5% | 1.5× | Watch | |
| Stable-income households | 1.2% | 0.5× | Normal |
Bar: gap-rate lift vs. stable-income baseline · scale 0–4.0× · tick marks the 2.0× review threshold
2 of 4 slices over threshold
Evidence-linked improvement
Each cycle closes by adding a case
A cycle closes when the missed recertification is a regression case. That suite is what the next year certified is measured against.
Improvement cycle · five stages
Switchback — the path turns at Improve and returns at Learn
- 01
Detect
Evidence completeness falls in a set-aside slice.
- 02
Diagnose
The unit that was compliant on paper and not in fact is read back through its file until the cause narrows to one.
- 03
Improve
The fix carries a number, and the files that forced it travel with it.
- 04
Verify
Nothing goes out until every touched household case has passed again.
- 05
Learn
It is kept permanently, and the eligibility rules are amended alongside it.
Learn → Detect
The return edge. The next cycle is detected against a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, file workflow, evaluation, integration, then production validation and handover.
Workstream
Week 1Week 2Week 3Week 4Week 5Week 6
- 01Compliance workflow discovery and boundary definition.Week 1
- 02Property and agency source assessment.Week 1, Week 2
- 03Programme rule, agency calendar and retention mapping.Week 1, Week 2
- 04Tenant-file ingestion and normalisation.Week 2
- 05Evidence assembly and citation binding.Week 2, Week 3
- 06Confidence scoring and gap routing.Week 3
- 07Owner sign-off workflow.Week 3, Week 4
- 08Property and agency system integration.Week 5
- 09Eligibility and recertification cases.Week 4, Week 5
- 10Guardrails and owner-certification controls.Week 4
- 11Household-trail instrumentation.Week 5, Week 6
- 12Deployment, documentation and Agent Care handover.Week 6
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel
Final scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
| Capability✓ in scope · — not at this tier | PilotOne property, one agency | ProductionProduction property systems | AdvancedMultiple states / programmes |
|---|---|---|---|
| Introduced at Pilot | |||
| Assembly to your files and rules | ✓ | ✓ | ✓ |
| Owner sign-off hold | ✓ | ✓ | ✓ |
| Evidence-completeness baseline | ✓ | ✓ | ✓ |
| Introduced at Production | |||
| Reporting by set-aside | — | ✓ | ✓ |
| Review workflow in your systems | — | ✓ | ✓ |
| Approved write-back | — | ✓ | ✓ |
| Property-system integration | — | ✓ | ✓ |
| Introduced at Advanced | |||
| Mixed-finance rule sets | — | — | ✓ |
| Multi-stage owner reviews | — | — | ✓ |
| High unit counts | — | — | ✓ |
| Multi-programme certification controls | — | — | ✓ |
| Build price | From $5,000 | From $8,000 | Custom quote |
- Final build price
- Confirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.
- Separate from build
- Build pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bring
We build with it
01Your tenant files and unit designations
→Tenant-file ingestion and evidence mapping
Week 102Representative certified households
→Assembly baseline, citation binding and gap detection
Week 203Your programme rules and agency calendars
→Programme, agency-calendar and retention mapping
Week 104Access to relevant APIs, feeds or exports
→Property and agency source assessment, then integration setup
Week 205Files you would not want sampled
→Correction cases and the evaluation suite
Week 406What no owner certification may assume
→Confidence scoring, gap routing, guardrails and sign-off controls
Week 307Named owner representatives to review files
→Owner sign-off workflow, then pilot and production validation
Weeks 5–6
Nothing else is required
Deployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Weeks the work truly needs set each of these widths, which is why the fifth band is not one but two.
Phase
W1
W2
W3
W4
W5
W6
- DiscoveryW1
- BuildW2 – W3
- EvaluateW4 – W5
- Pilot & LaunchW5 – W6
Week focus
W1Compliance workflow discovery, rule mapping and the automation boundary
W2Source integration and the assembly baseline
W3File workflow, confidence logic and sign-off controls
W4Evaluation suite, correction-clock checks and failure-mode testing
W5Agency-system integration, pilot files and targeted corrections
W6One certification year run under the ownership entity, then Agent Care handover
- Reading the band
- Each bar sits only on the weeks its work is named in. The week 5 overlap is real work, not padding.
- At the end of W6
- The final checks clear on live files and monitoring moves to Agent Care.
- Duration
- Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Real Estate AI agent
Build a compliance-file agent around the owner certification.
Show us your programme mix, your agency calendars and who signs. Ask who certifies at the end of it, and the answer does not move: the owner does, under penalties of perjury, on all twelve propositions in 26 CFR 1.42-5(c)(1). We map the assembly workflow, run the correction clock into the Form 8823 window the agency opens no earlier than that period ends and no later than 45 days after it, and name what stays with a person.
- Typical delivery
- 4–6 weeks
- Deployment
- Your unit files
- Agency-set date
- Owner certifies
- After launch
- Agent Care available
Nestack Agents · Affordable-housing compliance
AGT-RE-16 · Agent Care available after launch