Skip to content
Seven-layer architecture

One data spine. Two products: operations and valuation.

Every layer below is a real engineering surface with its own protocols, contracts, and failure modes. The stack is designed so operations pays for the sensors, and valuation emerges as a signed by-product of data we were already paid to collect.

End-to-end flow

Cumulative flow across all seven layers

L-0Field sensingInputs
Physical phenomena: vibration, tilt, voltage, current, water, CO₂, temperature, motion.
Process
On-node ADC sampling → thresholded encoding → LoRaWAN uplink; gateway buffers on WAN loss.
Outputs
Compact binary frames tagged with devEUI, timestamp, and RSSI/SNR — ready for decoding.
L-1Ingestion & market da…Inputs
LoRaWAN frames from gateways + nightly market-data files and APIs.
Process
Decode → validate → dedupe → insert into hypertable; ETL normalises leases and comps onto property_id.
Outputs
Unified time-series rows: readings, leases, transactions, comparables.
L-2Asset & twin modelInputs
Component catalogue, documents, maintenance history, incoming readings.
Process
Map readings to components → apply subsystem weights → compute per-subsystem and composite BHI.
Outputs
Versioned BHI score with subsystem breakdown and confidence flags.
L-3Valuation engineInputs
BHI · NOI (measured) · comparables · cost baseline.
Process
Run three estimators independently → weight by data quality → blend → emit CI.
Outputs
Valuation + confidence interval + explainable contribution breakdown.
L-4Trust & complianceInputs
Readings, computed scores, valuation snapshots.
Process
Hash → batch → Merkle root → anchor → valuer signs.
Outputs
Signed, anchored report with verifiable hash path.
L-5ApplicationsInputs
User role · organisation · query parameters.
Process
RLS view materialises role-appropriate slice → UI composes KPIs.
Outputs
Role-scoped dashboard, alerts, exports, and signed reports.
L-6Roll-outInputs
Design-partner buildings and pilot KPIs.
Process
Instrument → measure → publish · widen coverage each phase.
Outputs
Case evidence, portfolio benchmarks, open signed city index.
InputsProcessOutputsTap a row to open its layer
100%
L-4

Trust & compliance

Hash chain + Merkle batching + anchoring. Licensed valuer sign-off (RERA / RICS under IVS).

h0h1h2h3h4h5h6h7H0H1H2H3HH0HH1Merkle root · anchoredSHA-256 per reading · hourly batch · daily public anchorRERA · RICS · IVS
100%

Every reading is hashed with SHA-256 on ingest. Hourly, the platform folds the hour's hashes into a Merkle tree and stores the intermediate nodes. Daily, the root is anchored to a public ledger so any report can be re-verified in a browser at /trust/verify without trusting our servers. Certified valuations carry an additional licensed-valuer signature (RERA in the UAE, RICS globally, under IVS 2022), binding the human judgement to the exact data snapshot and methodology version that produced the number.

Specifications
  • Hash: SHA-256 per reading · content-addressed
  • Batching: hourly Merkle tree · nodes retained
  • Anchor: daily public root · verifiable in-browser
  • Signing: RERA / RICS certified valuer under IVS 2022
  • Verification: /trust/verify · client-side recompute
  • Audit trail: every event stamped and searchable
Inputs

Readings, computed scores, valuation snapshots.

Process

Hash → batch → Merkle root → anchor → valuer signs.

Outputs

Signed, anchored report with verifiable hash path.

5 / 7