Blog
The public layer got thicker without getting looser
The latest work was not a page-count sprint. It was a cleanup pass that made every published program managed by internal artifacts, then thickened the fields that help a buyer understand timing, repayment, and role fit without letting weak sources into the clean layer.
This update
The useful change was not more pages. It was cleaner coverage.
The public layer is still 248 program pages, but those pages now sit on a cleaner generated foundation and carry more of the fields buyers actually need.
The last stretch was less about adding new public pages and more about making the existing public set safer to keep updating. The important move was getting the publish layer back under control: every published program is now managed from internal artifacts, and the drift check reports zero legacy public records left outside that path.
That matters because stale public pages are not just old copy. They are a pipeline risk. If a page can survive outside the managed source path, it can keep reappearing after a publish pass even when the research layer already knows it should change. The cleanup work was about removing that class of problem before continuing to thicken the data.
What got thicker
Timing coverage made the biggest jump
Application timing is one of the hardest fields to fill safely, because many official pages tell buyers where to apply without saying how timing works.
The main coverage push was processingWindowSummary. That field now appears on 162 of 254 published programs.
The latest batches focused on official timing signals: lender reservation systems, rate-lock windows, first-come funding language, closing deadlines, post-approval document deadlines, and explicit processing estimates. Where the official page only said "contact a lender" without a window or deadline, the field stayed empty.
That is why some states moved fast and others did not. New Mexico, Hawaii, South Carolina, South Dakota, New York, Pennsylvania, Illinois, and Ohio all had enough official material for safe timing summaries in this pass. North Dakota and several South Dakota statewide pages still did not, so they stayed blank instead of getting invented timelines.
Why this helps a buyer
A firefighter should now see where the bottleneck sits
The goal is not just to say a program exists. The page should show which part of the process controls the next move.
If a firefighter is looking at a program, the useful question is rarely "does this page exist?" The useful question is "what has to happen before I can count on this assistance?"
For some programs, the answer is a participating lender reservation. For others, it is a city packet that has to be submitted weeks before settlement. Some programs depend on first-come funding. Some have a fixed rate-lock period. Some are currently closed because funds were used. Those are different buyer problems, and they should not be flattened into the same generic application paragraph.
That is the reason to keep thickening timing coverage. It moves the page from directory copy toward decision support without crossing into advice.
Current shape
The public layer is broader, but still guarded
The numbers are useful because they show which parts of the public layer are getting complete and which still need careful source work.
Published program pages
254 public program pages are live in the clean layer.
State governance records
50 state governance records are published, with 41 state pages eligible for indexing.
Timing summaries
162 programs now explain an application window, lender reservation step, deadline, or official no-window condition.
Repayment profiles
131 programs now have a useful repayment profile instead of the generic check-official-rules fallback.
Role-code coverage
72 programs now carry structured role codes for finder matching.
Under-review signals
44 records remain public as under-review signals instead of being promoted into false certainty.
Editorial rule
Coverage only counts when it can be refreshed
The next phase is more of the same: keep the generated layer clean, then fill fields in batches where official evidence is strong.
The rule now is stricter than "can we write a plausible sentence?" A field only belongs in the public layer if it can be traced to official source material and regenerated without manual rescue after publish.
That is the practical meaning of this round. The public layer did not just get thicker. It got more maintainable. That makes the next coverage batches safer, because new timing, role, and repayment fields can be added without re-opening the old legacy-drift problem.
Keep browsing
Where to go next
If you want to check the site itself instead of the writing around it, start here.
Programs
Browse the current public program pages directly.
States
Open the state directory to see where the public layer is thick and where it is still thin.
Methodology
Read the public methodology if you want the publishing and under-review rules.
Back to blog · Browse programs · Browse states · Read methodology