Our properties are the top of the funnel.

We run two kinds of reference property. Both are built only from documents that are already public. A buyer reads one for the answer, and a share of those readers turn out to need someone to do the work.

1. Manual and catalog lookup pages

A maker already publishes its own manual or parts catalog. We take one question that is genuinely answered inside that book and build a page that shows the steps and the page number. A code that is not in that book comes back empty — we do not invent fault codes.

These pages are read by the people who maintain, repair, specify and buy the equipment. When a plant needs a part sourced, a load moved or a panel replaced, that reader is the buyer.

2. Reports from public records

We take a public federal file, clean it, count it, and publish a page with inline charts, readable tables and the CSV behind them. The published page names the file it came from and the day it was pulled, because agencies revise their data.

Files we read: occupational injury and inspection records, awards and contract announcements, corporate and nonprofit filings. Nothing private, nothing scraped from behind a login, nothing that identifies an individual.

How a reader becomes an inquiry

1. A buyer arrives at a property from search, looking for a specific answer.
2. By the time they read the page, we know the equipment, the market and the job they are dealing with.
3. If the page tells them the work is beyond a manual, we offer one plain route to have it done — a short form in their own words.
4. We check the submission, then deliver it to one client whose service area and scope match.

What we publish, and how it may be reused

• Charts. Drawn inline, so they load as page content and stay readable in an archive.
• Tables. The counts behind every chart, not just the summary line.
• CSV. The same numbers as a file you can open in a spreadsheet.
• Method notes. Which file, which fields, which filter, which day.

Charts, tables and CSV from our report pages may be republished free of charge with attribution. One line is enough: name the site and the file, for example "Source: analysis of federal OSHA severe injury reports".

What we will not do

We do not publish anything that identifies an injured person, a patient, a minor or a private individual. We do not use private or leaked data. We do not publish a number without naming its source, and we date every pull, because agencies revise their files. We are not the equipment maker whose manual our pages read, and naming a maker does not mean the maker works with us or endorses us.

Seeing a number that looks wrong

Tell us which page and which figure. Corrections, cuts that are not on the page, and questions: tony@dilisights.com.