Skip to content

CII-BUILD Batch 01 — Climate context intake and engineering-risk translation #4

Description

@simon947161

Parent

Issue #3 — CII-BUILD Phase 0.

Objective

Define the controlled handoff from ClimateOS evidence into BuildingOS without allowing a global climate signal to become a direct site, compliance or damage conclusion.

Deliverables

  • docs/integration/CLIMATEOS_CLIMATE_CONTEXT_INTAKE_CONTRACT_V0_1.md
  • docs/risk/CLIMATE_DRIVER_TO_BUILDING_RISK_TRANSLATION_V0_1.md
  • static Australian example
  • China placeholder-jurisdiction example with no fabricated legal or compliance result

Intake objects

  • climate driver state
  • regional climate tendency
  • local hazard candidate
  • observed event evidence
  • spatial boundary and scale
  • observation/forecast window
  • confidence and uncertainty
  • provider/model provenance
  • evidence passport reference

Translation chain

climate driver → regional tendency → environmental condition → site hazard → building exposure → vulnerability → engineering behaviour → observed evidence

Initial risk pathways

  • drought and reactive-soil movement
  • extreme rainfall and flooding
  • heat
  • bushfire weather
  • wind and tropical-cyclone exposure
  • water-supply stress

Guardrails

  • BuildingOS does not diagnose ENSO, IOD, SAM or cyclone tracks.
  • No climate index directly triggers a compliance conclusion.
  • No inferred building damage without observed evidence.
  • Jurisdiction-specific rules remain separate from physical-risk translation.

Acceptance criteria

  • Every stage is represented as a separate object or explicit relationship.
  • Provenance, uncertainty, spatial scale and validity period survive the handoff.
  • Missing site evidence produces an unresolved/conditional state, not a conclusion.
  • Contract remains provider-neutral and does not hard-code MAZU or any other source.

Execution mode

Static documentation, schemas, examples and tests only. Draft PR; do not merge without Founder review.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions