Gesher · chat-first UI wireframe
The product surface the shifts are building at frontend/gesher/. ONE primary surface: the chat. Knowledge + conflicts live in a collapsible rail — never a separate tab universe. Built against the live Phase 0.5 backend (no new endpoints). Content below is the real seeded Bunbury data.
§ Screen 3 · the room — 95% of the product
Engineer lives here. Drop docs anywhere → facts merge into the project's canonical knowledge (rail updates live). Conflicts pinned top of rail — engineer always decides, never the AI. Ask for prose → cited paragraphs → export DOCX per turn.
Gesher
Project · Bunbury Outer Ring Rd S2 ▾
Discipline · Geotech ▾
AL
§ Project knowledge · geotech
22 populated
3 corroborated
1 engineer-locked
3 conflicts
§ Resolve these · sources disagree
design_cbr_value
A · 3.5
B · 1.8
Custom…
Skip
A from 01-proposal-P-LBC-0241.docx p3 · "Design CBR adopted as 3.5%"
B from 04-geotech-investigation.docx p7 · "Lowest measured CBR was 1.8% from BH-04"
report_date
A · 2026-02-07
B · 2025-11-12
Custom…
Skip
A from proposal p1 · B from investigation p1
report_reference_number
+ 1 more…
§ Fields
project_nameBunbury Outer Ring Road Stage 2✓×2
clientMain Roads WA✓×2
consulting_firmLieblich Civil Pty Ltd🔒
borehole_count8 (BH-01 → BH-08)
spt_n_upper_2m15 to 28
design_cbr_value— conflicted —⚠
groundwater_m3.80 to 6.10 bgl
uscs_classesSM · SC · CH · CL
…14 more · click any field to edit + see provenance
interactions: click field → inline edit (locks it 🔒) + provenance popover (every source: doc · page · quote · confidence). Rail collapses on mobile.
§ You
📄 04-geotech-investigation-report.docx
DOCX · 15 pages · extracting… done in 64s
✓ 22 facts → 15 new · 3 corroborated · 4 conflicts queued
§ You
Draft the subgrade conditions paragraph for the pavement design report.
§ Gesher
The Bunbury Outer Ring Road Stage 2 alignment between chainage 3200 and 6400 is predominantly underlain by medium-dense to dense sand with SPT N values of 15 to 28 in the upper 2 m, indicating competent subgrade conditions. An exception occurs at BH-04 (CH 4260), where a soft alluvial layer of grey silty clay is present from 1.80 m to 4.20 m depth with SPT N values of 3 to 7. Soils are classified as SM, SC, CH and CL per AS 1726-2017. The adopted design CBR is
[CONFLICT — RESOLVE: design_cbr_value]. Groundwater was encountered in all boreholes between 3.80 m and 6.10 m below ground level. The pavement boxing depth at BH-04 is
[ENGINEER TO CONFIRM: boxing depth].
§ Citations · every claim sourced
spt_n_upper_2m = 15 to 28 · 04-geotech-investigation.docx p4 · "SPT N values in upper 2 m ranged from 15 to 28"
soft_layer_borehole = BH-04 at CH 4260 · p6 · "Soft alluvial layer encountered at BH-04…"
uscs_classifications = SM, SC, CH, CL · p5 · "classified per AS 1726-2017…"
+ 5 more…
↻ Redraft
⬇ Export DOCX
§ You
remind me how to calculate gutter spread width
§ Gesher
GENERAL GUIDANCE · not sourced from your project docs · verify against current standards
Gutter spread width comes from the modified Manning's / Izzard approach in AGRD Part 5A: compute gutter flow from the contributing catchment (Q = C·i·A per ARR 2019), then solve spread T from Q = (0.375/n)·Z·S
L0.5·T
8/3 where Z is the inverse crossfall, n the gutter Manning's roughness, S
L the longitudinal grade. Check T against the lane-encroachment limits in your road authority's supplement (e.g. half a travel lane for minor events). Standards: AGRD Part 5A · ARR 2019 · QUDM §7 where applicable.
↻ More detail
⚠ 3 unresolved conflicts — drafter skipped those fields. Resolve in the rail ←
+ doc
Draft the groundwater management section…
Send ⌘↵
§ Screen 2 · project picker (first-run + switcher)
Cards show per-discipline knowledge chips so you see project health at a glance. "+ New project" → name + code → straight into an empty room.
Gesher
AL
§ Your projects
BORR-S2
Bunbury Outer Ring Rd S2
geotech · 22 facts
⚠ 3 conflicts
civil · 17 facts
Active 2h ago
FDU-S2-2026
Foreshore Drainage Upgrade
civil · 9 facts
Active yesterday
+ New project
empty state (no projects): one card-sized CTA — "Drop your project docs, get cited report prose. Never invented, always sourced." + new-project button.
§ Screen 1 · auth (minimal)
Gesher
Report drafting for engineers. Every claim cited.
§ Sign in
email
password
Sign in
No account? Sign up — email · password · your name · firm name.
§ What is deliberately NOT here
No register tabs (risks/budget/RFIs/meetings/drawings). No dashboards or charts. No template scanner. No form-filling workspaces. The old 20-tab app stays at /work/ untouched until cutover; this lives at /gesher/.