Canonical Paths

Canonical paths are semantic addresses in the built environment graph.

They make the system easy for agents because the same path appears in source code, documentation, compiler diagnostics, eval findings, repair hints, and patches.

Examples

site.main
site.main.parcels.pcl_001
site.main.parcels.pcl_001.boundary.edges.front
site.main.parcels.pcl_001.constraints.setbacks.front
site.main.terrain.existing.contours.c_420
site.main.envelopes.primary
buildings.b_001
buildings.b_001.systems.core.main
buildings.b_001.levels.l02.floorplate
buildings.b_001.units.u_204.spaces.bedroom_1

Rules

• Path segments use lower snake case.
• Collections use plural nouns: parcels, constraints, setbacks, buildings, levels, spaces, systems.
• Paths may address entities, relation groups, constraint groups, properties, metrics, or artifacts.
• Stable IDs still exist underneath paths for backend mapping and history.
• Agents should prefer targetPath in patches.
• Relative paths resolve against the nearest semantic parent.

Patch Target

{
  "type": "updateProperty",
  "targetPath": "site.main.parcels.pcl_001.constraints.setbacks.front",
  "params": {
    "distance": "5000mm"
  }
}

Eval Finding

{
  "rule": "planning.setback_distance",
  "targetId": "Constraint.SETBACK-001",
  "targetPath": "site.main.parcels.pcl_001.constraints.setbacks.front",
  "groupPath": "site.main.parcels.pcl_001.constraints.setbacks",
  "severity": "hard"
}