Early enquiry · AI interpretation · Interface topology sketch v0

How well can AI make sense of interfaces, topology and system architecture? This variant makes one interpretation of the shared fictional brief available for inspection. Vary assumed bands and levels, inspect signed distances from the site centre, and export SVG views.

← All six Tangled Triangle variantsLater enquiry: local-to-global compatibility →

Back to Tangled Triangle

Interface Topology Sketch (v0) — Control Centre Site with Canal / Road Bridge / Rail Viaduct / OHL / Mine

Conceptual geometry/topology only: a triangular site bounded by a canal (south), a road on the west (crossing the canal), and a railway alignment NW→SE along the hypotenuse, carried on viaduct. Under the site: mining passage at depth; above: high voltage overhead line N→S. Use the toggles/sliders to explore the controlling envelopes and to “read” interface pressure points.
Plan: boundaries & corridors
Section: vertical stack
Assumptions: parametric, editable

Plan (schematic)

Hover features for interface notes • Click a section cut to update the section view

Section (schematic)

Shows a controlling vertical “stack” rather than exact chainage

Controls (envelopes & visibility)

Numbers are illustrative drawing inputs. Verified site requirements and separate engineering checks would be needed for design use.

Show / hide constraints

Key parameters

Canal buffer (m)
Road buffer (m)
Rail buffer (m)
OHL corridor half-width (m)
Mine influence radius (m)

Vertical stack (section)

Road deck height (m)
Rail deck height (m)
OHL conductor height (m)
Mine depth to crown (m)
Canal bed depth (m)

Read-out (distance from the site centre to assumed bands)

The figures rank up to four visible bands by distance from the triangle’s centre to the assumed band edge. A negative value means that centre lies inside the band. This is a geometric illustration, not a ranking of engineering risks or a buildable-area calculation. In section, compare the assumed heights and depths. This drawing does not calculate which constraint governs a feasible design or select a foundation strategy.

Concept notes (topology → interfaces)

These are the seeds for your later interface register.
Topology of boundaries. You have a hydraulic/amenity edge (canal) on the south, a transport edge (road) on the west, and a high-consequence linear edge (rail corridor) on the diagonal. Vertically, the site is “sandwiched” between legacy subsurface and electrical exclusion.
Interface pressure points.
  • South-west corner: canal + road bridge abutments + flood/overbank + access constraints (compound interface).
  • Diagonal boundary: rail viaduct piers/embankment + possession/access + stray current/EMC considerations (hard interface).
  • Overhead line crossing: establish asset-specific constraints for buildings, cranes, earthing/bonding and work near the line; identify the relevant permissions.
  • Mining passage: investigate ground response and agree risk allocation, monitoring and acceptance criteria; the sketch sets no settlement limit.
Suggested section choice. The cut is deliberately a controlling envelope (composite) rather than a literal chainage: it’s a way to reason early about “how many vertical masters” the building has.
Legend: Canal Road Rail OHL Mine Changing a band changes the sketch; it does not establish permission to build or verify a clearance. Use site-specific evidence for any later design assessment.
If you want this to become a working project manager aid, the next step is to add: import of survey (DXF/GeoJSON), clearance rulesets, and auto-generated interface register from the geometry.