Research — Harnesses · cross-domain
Harnesses working across domains
A harness is a domain's compliance and compute functions exposed as MCP tools, the same tools as the API. These examples show one or several of them driven from a chat. Each is a scripted replay with illustrative values, not a live session; a person approves or dismisses every proposed change. Each card names the domains it touches and links to the interactive pages that show the underlying checks on their own.
Harness demos
- Illustrative, scripted
Review loop: one harness, one pole file
The overhead harness opens a pole project file, runs a strength analysis, proposes fixes, and a person approves or dismisses each before an export. Nothing is applied without that approval.
Domains touched
Overhead LineInteractive pages for the same checks
Watch the scripted demo → - Illustrative, scripted
In the application: approved fixes land in the open design file
After a person approves a fix, the harness makes the change inside the open design file through the design application’s own automation interface, in four scripted sessions: an overhead pole, an underground pad-mount, a substation drawing and a datacenter plant. Each shows what that application offers to reverse the change, including one case where it offers none. A model label can be switched without changing a single tool call.
Domains touched
Watch the scripted demo → - Illustrative, scripted
Stage by stage: generation to substation
A generation plant and then its substation walked through their design stages, one design basis entered once. Each stage reports valid, incomplete, failed, stale or missing, and nothing passes by default. The plant’s fault contribution reaches the substation as a versioned hand-off, a breaker that was adequate on the grid alone is not with the plant, and a verified fix sends every dependent stage stale before it is re-run. A short coda runs the same pattern on a transmission line. The numbers come from running the design workflows offline; the demo does not call the live routes.
Domains touched
Interactive pages for the same checks
Watch the scripted demo → - Illustrative, scripted
Grid to rack: one design, six harnesses
A grid-fed datacenter reviewed stage by stage: transmission tap line, substation bus scheme and fence, duct bank, hall power path, service-gear fault current against its interrupting rating, and liquid cooling. Each stage hands a result to the next.
Domains touched
Transmission StructureSubstationUndergroundAI-Factory Equipment DataBuilding ElectricalCircuit / GroundingThermalInteractive pages for the same checks
- Structure loading walk →
- Bus scheme and breaker count →
- Fence clearance →
- Duct bank: one feeder becomes four →
- Generation to rack: power path N-1 →
- Service entrance: the compliance walk →
- Fault current along a feeder →
- Liquid loop: lose a CDU →
- Pipe velocity regimes →
Harness maturity follows the domains underneath: most are draft and unvalidated, as each demo states.About harnesses ·All domains →