Cluster-Efficiency Dashboard

The big one — design documents we still need

Operations / completion engineers can directly help here.

What it is

To compute Cluster Efficiency (CE) for a stage, the dashboard needs that stage's perforation design: the number of clusters, the shots per cluster (perf holes per cluster), and the entry-hole diameter (EHD) — the perf hole size in inches (e.g. 0.42″, 0.465″). Together these define the open hole area, which is the core input to the CE physics.

We only use real, source-backed numbers — never estimates. So where these docs are missing, CE can't be shown for those stages.

The gap — ~8,254 stages across 5 clients

Client	Stages missing design
Occidental (OXY)	2,649
EQT	2,150
Teine	1,467
Kiwetinohk	1,209
Sabinal	779
Total	8,254

What we need from the team: the completion design package for these wells — any of the frac sequence / frac table, pump schedule, perforating design / Pad Info sheet, or gun-barrel diagram. These live in the client SharePoint / OneDrive folders.

Proof it works: We just did this for the RLacy Tower project. Its frac sequence in SharePoint gave the exact per-stage clusters + shots + 0.465″ entry-hole, and CE then computed correctly for all 6 wells. The same one-time step closes each of the 5 clients above — we just need to know where their design docs are (or have them dropped into SharePoint).

Engineering cleanup & improvements

Dev team — no outside input needed. These harden quality, performance, and polish; they don't block usage.

Correctness & test coverage

Re-point two stale automated checks. Two CI "guard" scripts test a deleted old version of the app, so they no longer guard the real code. Fix them to check the current data path — so the safety net actually catches regressions.
Turn on ~25 data-integrity checks in CI. We have checks that validate data wiring, but the pipeline wasn't running them — so they protected nothing. Wire them in to catch data breakage before deploy.
Math re-verification. Independently re-derive CE, frac gradient, ISIP, and water-hammer against a known "golden" reference and lock it into automated tests — proving the numbers are right and keeping them right.
Export round-trip test. Confirm CSV/HTML export and copy-summary reproduce the on-screen data exactly, in both US and metric units, across multiple projects.
Fix the browser end-to-end test in CI. It currently hangs in the CI environment so it's disabled; make it exit cleanly and re-enable it.

Make the app fully data-driven

Remove 3 hard-coded project references in the main app file. A few spots still branch on a specific project name instead of reading from the data catalog. Making them generic is the precondition for clean API/data export later.

Performance

Split the JavaScript bundle. The app loads two large code chunks up front (~597 KB + ~459 KB). Lazy-load the heavy views/charts so the first screen paints faster.
Migrate ~1,200 hard-coded color values to design tokens (~10 files). Consistent theming and far easier to restyle light/dark.
Split the 8,500-line main file into smaller modules. Maintainability. Higher-risk, done carefully.

UI / polish

Unify the accent colors. Two slightly different "cyan" values are in use — pick one. Also fix a dark-mode highlight that still shows an off-brand orange tint.

Help / documentation

Refresh the in-app Help docs so they describe the current features (project picker with coverage badges, CSV upload, Campaign view, bulk editor, unit toggle).
Remove a leftover unused code file (mcpClient.ts), kept only as a record — decide whether to delete it.

✓

Already done & live

For context — completed this session.

RLacy Tower now shows all 6 wells with real, source-backed perforation geometry and correct CE.
The help-desk chatbot works and can answer live data questions like "what are the design stats and CE for stage 13 on BPX Hodges?" — reading the real numbers from our database.
Chatbot conversations are private — each person's history stays in their own browser; no one sees anyone else's.
A clean-branded URL, cluster-efficiency.pages.dev, is live.
Fixed the CNPC Karamay catalog entry, re-indexed the code intelligence, and corrected an annular-area documentation value.