Components and headless

Supported exports

Use the approved overa-property-explorer artifact supplied for your integration. It is a private, unpublished package: these imports describe its delivered export map, not an instruction to install an imaginary registry release.

Branding and agency reports

The supplied artifact also exposes overa-property-explorer/theme/headless and explicit overa-property-explorer/components/insights/headless, /geography, /view and /style.css exports. The separately supplied @overa/insights artifact has the same report contracts and is not a public registry release. Its host supplies authenticated transport; never put a confidential backend key into browser props.

Client colours come from the published configuration, with Overa defaults when none are supplied. Installing a report view does not activate collection or release: both need separate, current, integration-bound operator authority. The five surfaces are overview, demand, stock gaps, engagement and conversions; sparse or unavailable evidence is withheld rather than invented.

Headless without a browser

The zone editor, map legend, map toolbar and Results actions expose explicit /headless exports. Import those paths in a supported plain Node runtime; browser view paths include CSS and require a DOM. The following example builds a request and presentation model without starting a map or network operation.

import { createMapLegendModel } from
  'overa-property-explorer/components/map-legend/headless';
import { createManagedEvaluationRequest } from
  'overa-property-explorer/components/zone-editor/headless';

export function preparePresentation(profile, constraints, evaluation = null) {
  // Profile and results come from the managed service, not a second rule engine.
  const request = createManagedEvaluationRequest({
    profile, constraints, domainRequirements: {}, clientRevision: 1,
  });
  const legend = createMapLegendModel({ constraints, evaluation });
  return { request, legend };
}

Compose without competing owners

Inject published capabilities, adapters and deliberate intents. Each view owns only its supplied container and uses that container's document. Dispose it on teardown. Serve the approved marker, toolbar, font and stylesheet assets from the permitted application origin.

Two editors sharing one applied collection and map need one createZoneCollectionEvaluationController. Search and naming ownership remain per editor, while evaluation revision and stale-response rejection stay shared. Do not reproduce matching rules in a component or use another tenant's state.

Street-level components require separately admitted provider adapters. A component import does not grant imagery, credentials, territory or provider spend. A complete standalone Map/Results package and native SDK are not supplied by these exports.