Homera RESO certification
Running production checks.
Loading provider, metadata, field coverage, sync, and infrastructure evidence.
Homera RESO certification
Loading provider, metadata, field coverage, sync, and infrastructure evidence.
This verdict uses live provider, Bridge mirror, OAuth, metadata, field coverage, and infrastructure evidence. External RESO identifiers and publication remain visible but never block Homera cert-ready status.
Cert-ready checks
Homera cert-ready
Ready
Technical evidence
not run
Published RESO state
unverified
No authoritative publication source connected
Managed immutable history
Official technical runs and RESO-controlled publication observations advance independently for each normalized scope. Operational and local preflight values are excluded.
These five stages preserve managed tool evidence when available. They remain separate from both Homera cert-ready status and RESO-published certification.
Cert-ready · External recipient unavailable · non-blocking
Homera preflight passed
Local provider, metadata-shape, and source-coverage diagnostics.
Core 2.0.0 technical evidence passed
Locally managed runner evidence with deployment provenance.
DD 2.0 metadata evidence passed
Managed standard names, types, lookups, and metadata evidence.
Strict variations check passed
The complete strict run proves no blocking unresolved mappings.
Availability and strict schema evidence passed
Managed sampling and strict payload-validation evidence.
Open any suite to see the exact pass condition and live result.
Authenticated service-document, metadata, and resource smoke checks. These are not official Core results.
Service document
Passed
Pass condition
Authenticated GET returns an OData 4.0 JSON service document with context and every expected EntitySet.
Evidence
HTTP 200 · 31 ms
$metadata endpoint
Passed
Pass condition
Authenticated GET returns HTTP 200 XML metadata.
Evidence
HTTP 200 · application/xml; charset=utf-8 · 16 ms
Property sample and count
Passed
Pass condition
GET with $top=1 and $count=true returns exactly one sample row, a positive consistent count, JSON, and OData-Version 4.0.
Evidence
HTTP 200 · 52,625 records · 75 ms
Office sample and count
Passed
Pass condition
GET with $top=1 and $count=true returns exactly one sample row, a positive consistent count, JSON, and OData-Version 4.0.
Evidence
HTTP 200 · 1,032 records · 128 ms
Member sample and count
Passed
Pass condition
GET with $top=1 and $count=true returns exactly one sample row, a positive consistent count, JSON, and OData-Version 4.0.
Evidence
HTTP 200 · 15,731 records · 65 ms
OpenHouse sample and count
Passed
Pass condition
GET with $top=1 and $count=true returns exactly one sample row, a positive consistent count, JSON, and OData-Version 4.0.
Evidence
HTTP 200 · 4,976 records · 61 ms
Lookup sample and count
Passed
Pass condition
GET with $top=1 and $count=true returns exactly one sample row, a positive consistent count, JSON, and OData-Version 4.0.
Evidence
HTTP 200 · 3,190 records · 58 ms
Local EDMX, entity-key, EntitySet, annotation-coverage, and facet diagnostics. Official DD metadata validation is tracked separately.
Metadata is non-empty XML
Passed
Pass condition
An EDMX document larger than 100 bytes is returned.
Evidence
18,711 bytes received
OData EDMX 4.0 root
Passed
Pass condition
The root declares EDMX version 4.0.
Evidence
edmx:Edmx Version=4.0
DataServices container
Passed
Pass condition
Metadata includes an edmx:DataServices container.
Evidence
edmx:DataServices present
Schema declaration
Passed
Pass condition
At least one OData Schema is declared.
Evidence
2 schema declaration(s)
Entity types declared
Passed
Pass condition
At least one EntityType is declared.
Evidence
5 entity type(s)
Property has a key
Passed
Pass condition
Each resource declares an OData Key.
Evidence
ListingKey is the key
Property key is a property
Passed
Pass condition
The declared key also exists as a Property.
Evidence
ListingKey
Office has a key
Passed
Pass condition
Each resource declares an OData Key.
Evidence
OfficeKey is the key
Office key is a property
Passed
Pass condition
The declared key also exists as a Property.
Evidence
OfficeKey
Member has a key
Passed
Pass condition
Each resource declares an OData Key.
Evidence
MemberKey is the key
Member key is a property
Passed
Pass condition
The declared key also exists as a Property.
Evidence
MemberKey
OpenHouse has a key
Passed
Pass condition
Each resource declares an OData Key.
Evidence
OpenHouseKey is the key
OpenHouse key is a property
Passed
Pass condition
The declared key also exists as a Property.
Evidence
OpenHouseKey
Lookup has a key
Passed
Pass condition
Each resource declares an OData Key.
Evidence
LookupKey is the key
Lookup key is a property
Passed
Pass condition
The declared key also exists as a Property.
Evidence
LookupKey
Property entity set advertised
Passed
Pass condition
The service advertises the required EntitySet.
Evidence
Homera.RESO.Property
Property entity type resolves
Passed
Pass condition
The EntitySet points to a declared EntityType.
Evidence
Property
Office entity set advertised
Passed
Pass condition
The service advertises the required EntitySet.
Evidence
Homera.RESO.Office
Office entity type resolves
Passed
Pass condition
The EntitySet points to a declared EntityType.
Evidence
Office
Member entity set advertised
Passed
Pass condition
The service advertises the required EntitySet.
Evidence
Homera.RESO.Member
Member entity type resolves
Passed
Pass condition
The EntitySet points to a declared EntityType.
Evidence
Member
OpenHouse entity set advertised
Passed
Pass condition
The service advertises the required EntitySet.
Evidence
Homera.RESO.OpenHouse
OpenHouse entity type resolves
Passed
Pass condition
The EntitySet points to a declared EntityType.
Evidence
OpenHouse
Lookup entity set advertised
Passed
Pass condition
The service advertises the required EntitySet.
Evidence
Homera.RESO.Lookup
Lookup entity type resolves
Passed
Pass condition
The EntitySet points to a declared EntityType.
Evidence
Lookup
LookupName annotation coverage
Passed
Pass condition
The metadata includes at least one RESO LookupName annotation for every Homera-advertised lookup-backed field.
Evidence
64/11 lookup-backed fields annotated
Decimal precision and scale facets
Passed
Pass condition
Every Edm.Decimal field declares both Precision and Scale.
Evidence
12 decimal field(s) checked
String length facets
Passed
Pass condition
Every Edm.String field declares MaxLength.
Evidence
90 string field(s) checked
Homera-advertised fields compared with upstream Bridge metadata refreshed 8/27/2026, 11:40:41 PM. This is not Data Dictionary conformance.
Property field coverage
Passed
Pass condition
Every field advertised in Homera metadata exists in the upstream dataset.
Evidence
124/124 fields present
Office field coverage
Passed
Pass condition
Every field advertised in Homera metadata exists in the upstream dataset.
Evidence
10/10 fields present
Member field coverage
Passed
Pass condition
Every field advertised in Homera metadata exists in the upstream dataset.
Evidence
19/19 fields present
OpenHouse field coverage
Passed
Pass condition
Every field advertised in Homera metadata exists in the upstream dataset.
Evidence
14/14 fields present
Lookup field coverage
Passed
Pass condition
Every field advertised in Homera metadata exists in the upstream dataset.
Evidence
6/6 fields present
Locally managed declarations for official-run artifacts and deployment provenance; not RESO-published status.
Official Web API Core 2.0.0
Not run
Pass condition
The official Core 2.0.0 runner exits successfully with zero failures and preserved provenance and artifacts.
Evidence
No managed official Core artifact record has been ingested.
Locally managed metadata, strict variations, availability, and schema evidence; not RESO-published status.
DD 2.0 metadata validation
Not run
Pass condition
The official Data Dictionary 2.0 result package proves this stage passed with retained provenance and artifacts.
Evidence
No managed official DD result has been ingested.
DD 2.0 strict variations check passed
Not run
Pass condition
The official Data Dictionary 2.0 result package proves this stage passed with retained provenance and artifacts.
Evidence
No managed official DD variations artifact has been ingested.
DD 2.0 data availability sampling
Not run
Pass condition
The official Data Dictionary 2.0 result package proves this stage passed with retained provenance and artifacts.
Evidence
No managed official DD availability result has been ingested.
DD 2.0 strict payload schema
Not run
Pass condition
The official Data Dictionary 2.0 result package proves this stage passed with retained provenance and artifacts.
Evidence
No managed official DD schema result has been ingested.
Operational freshness and retained-population evidence included in Homera cert-ready status.
Property operational sync
Passed
Pass condition
Bridge readiness confirms a complete, current generation whose exact and observed populations agree.
Evidence
ready · exact population 52,625 · observed population 52,625
Office operational sync
Passed
Pass condition
Bridge readiness confirms a complete, current generation whose exact and observed populations agree.
Evidence
ready · exact population 1,032 · observed population 1,032
Member operational sync
Passed
Pass condition
Bridge readiness confirms a complete, current generation whose exact and observed populations agree.
Evidence
ready · exact population 15,731 · observed population 15,731
OpenHouse operational sync
Passed
Pass condition
Bridge readiness confirms a complete, current generation whose exact and observed populations agree.
Evidence
ready · exact population 4,976 · observed population 4,976
OAuth and production dependency health included in Homera cert-ready status.
OAuth client credentials
Passed
Pass condition
The provider mints a bearer token without exposing credentials.
Evidence
OAuth token minted in 46 ms
Convex production health
Passed
Pass condition
The public dependency health endpoint returns HTTP 200.
Evidence
HTTP 200 · 80 ms
Recorded only if an authoritative source supplies them; availability does not affect Homera cert-ready status.
Provider UOI
Pending
Pass condition
If issued, an authoritative RESO source confirms the technology provider identifier.
Evidence
Unavailable and excluded from Homera cert-ready status
Recipient UOI
Pending
Pass condition
If issued, an authoritative RESO source confirms the recipient identifier.
Evidence
Unavailable and excluded from Homera cert-ready status
Provider USI
Pending
Pass condition
If issued, an authoritative RESO source confirms the provider system identifier.
Evidence
Unavailable and excluded from Homera cert-ready status
Reported separately when authoritative evidence exists; unavailable external workflow does not affect Homera cert-ready status.
Certification request opened
Pending
Pass condition
A certification request has been opened with RESO.
Evidence
Not recorded
Core run submitted
Pending
Pass condition
The official Core result package has been submitted.
Evidence
Not submitted
Core technical evidence passed
Pending
Pass condition
The locally managed Core run has complete zero-failure evidence.
Evidence
Awaiting managed technical evidence
DD run submitted
Pending
Pass condition
The official DD result package has been submitted.
Evidence
Not submitted
DD technical evidence passed
Pending
Pass condition
All managed DD 2.0 stages have complete passing technical evidence.
Evidence
Awaiting managed technical evidence
Recipient notified
Pending
Pass condition
The certification recipient has been notified.
Evidence
Not recorded
Recipient reviewed
Pending
Pass condition
The certification recipient has reviewed the submitted results.
Evidence
Not recorded
Terms accepted
Pending
Pass condition
Certification terms have been accepted.
Evidence
Not recorded
Passed Current
Pending
Pass condition
RESO has accepted the technical results as Passed Current.
Evidence
Not recorded
Certified Current and published
Pending
Pass condition
The recipient approval is complete and RESO has published certification.
Evidence
Not recorded
Certification report URL
Pending
Pass condition
A published RESO certification report URL is recorded.
Evidence
Not recorded
Certification status date
Pending
Pass condition
The current certification status date is recorded.
Evidence
Not recorded
Membership or fee status
Pending
Pass condition
Membership eligibility or the applicable nonmember fee state is recorded.
Evidence
Not recorded
Cert-ready boundary
Keep Bridge evidence current
All required mirrored resources, metadata, lookups, counts, and Property search cardinality must remain coherent and fresh.
Preserve exact-build proof
Bind passing checks and tool output to the deployed commit, deployment identity, configuration, and retained artifacts.
Keep external status separate
Unavailable RESO identifiers, acceptance, terms, and publication are informational and never change Homera’s cert-ready verdict.