Terms first
Every source is approved against its published terms before it is asked anything. The terms are archived and read again every week. If they change, the source stops counting until a person approves it again.
Edson Technologies
Inspexius™
The property evidence register.
Inspexius answers questions about property the way a careful reviewer would: with the record, where the record came from, and the date it speaks to. Where it cannot answer, it says why.
From the Latin inspexi: “I have inspected.”
- Question
- Flood hazard zone
- Answer
- Found Zone X
- Cites
sha256:9f2c…e41a, archived before it was read- At
features[0].attributes.FLD_ZONE- As of
- The map’s effective date, not the download’s
- Under
- The publisher’s own terms, archived and re-read every week
- Rule
flood.zone, version 4
§ 1
What it is
Inspexius answers a fixed set of questions about land: which property and which parcel an address means, what the government’s maps say about its ground, who holds it of record, what the record says stands on it, what it is assessed at, and how its market is moving.
Each answer is evidence, not just a value. A found fact carries the fingerprint of the archived file or response it came from, the place inside that file, the date the record speaks to, the terms the file was obtained under, and the version of the rule that read it. A reviewer can open the bytes. An auditor can replay the rule.
§ 2
Four answers. Never silence.
“No data” reads as “no problem”, which is the most dangerous thing a review can say. Inspexius cannot say it. Every answer is one of four, and a found answer without a citation is refused by the register itself.
- Found
A value, with the archived bytes it came from.
- Not found
The source was asked, and holds nothing.
- Not covered
No approved source answers this question here. Said first, not discovered later.
- Unavailable
Asked and not answered, with a reason that says why.
Absence is never a fact. Where records disagree, they are never averaged: the stronger record answers, and the dissent is shown beside it.
§ 3
Through the front door
Inspexius takes only what publishers publish for the asking, on their own terms, and it keeps the receipts.
An identified visitor
Every request says who is asking, and links to a page that explains it. robots.txt is honoured, and so is the pace a host asks for. No logins, no CAPTCHAs, no rotating addresses, no disguise.
Bytes before facts
What a source returns is archived before it is read, in a store the application cannot rewrite. A fact whose bytes are gone is refused.
Land, not people
The parcel is the subject. A person is never the key, and a name is never accepted as a question. Where a county withholds an owner’s name, Inspexius withholds it too, and says that it was withheld.
Withdrawal, never erasure
When a source must be withdrawn, its facts are set aside and every answer that stood on them is asked again. The register still shows what it once said, and on what.
Rules decide
Answers come from deterministic, versioned rules. No model decides an answer, and a new source is a reviewed file, not new code.
§ 4
What it is not
Inspexius gathers the public record and says exactly what it says. It does not stand in for the people and products that value, certify or insure.
- Not an appraisal, and not an automated valuation model.
- Not a flood determination. It reports what FEMA’s map says, cited to the map, and certifies nothing.
- Not a title search, and not title insurance.
- Not for credit decisions.
§ 5
Who runs it
Inspexius is an internal system operated by Edson Technologies. It is not offered as a product, and it does not sell or redistribute data.