Technical (Integration and Data)

Integration principle

• structured inputs (case artifacts)
• structured outputs (trace packs, governance summaries, decision-relevant signals)
• auditability as a first-class output

Output artifacts (examples)

• inference structure: hypotheses, checks, assumptions, uncertainties
• review prompts: what an independent reviewer must be able to verify
• decision-relevant signals: explicitly derived, with provenance

Data handling (PoC-ready)

• minimal data principle
• pseudonymisation where possible
• explicit separation of evidence vs interpretation vs recommendation

System blueprint (technical core)

The following elements describe the core of the system blueprint used in enterprise deployments:

Genesis Code

An immutable, normative rule set defining how building-related findings are interpreted, with controlled governance for changes.

Modular architecture

Domain modules (e.g., thermo-hygro, moisture/mould, structural moisture behaviour) implement the Genesis Code and expose standard interfaces.

Deterministic policy layer

Transparent decision trees and policy rules; documents triggered rules and discarded alternatives for explainability.

Hash-secured audit trail

Time-stamped logs linked to case identifiers, protected by hash values to safeguard integrity and enable reconstruction.

Data model

Uniform schema for case metadata, measurement series, image references, and outcomes; extensible without breaking integrations.

Integration interfaces

APIs / structured files / manual entry depending on scenario; outputs as structured objects and/or human-readable reports.

Deployment options

On-premise, private cloud, or hybrid setups aligned with data residency, security, monitoring and IT governance requirements.

Deployment (discussion-based)

Deployment and data residency options should be aligned with the organisation’s governance and ICT requirements.

Next step

Boundary

BDA Genesis does not automate coverage, liability or claims decisions.