Artemis DEP Sewer Utility Intelligence Bridge — RC7 Publication QA + Capture Studio

Quantity takeoff

DEP Sewer Utility Standards Lens

Purpose: make this public demo unmistakably about a realistic sewer utility system. Artemis is using representative DEP-style sewer standard families as the sample domain, then showing how standard-driven geometry can feed quantity takeoff, ERP cost codes, field production, schedule, cashflow, variance, risk, opportunity, and executive reporting.

Pipe families

RCP · VCP · HE-RCP

Pipe family and size selections drive outside envelope, trench geometry, bedding/cradle/encasement factors, LF quantities, and cost-code mapping.

Structures

Manholes · Catch Basins

Manhole and catch-basin families define structure count, excavation allowances, concrete, risers, leads, and inspection/sequence logic.

Pipe zone

Bedding · Cradle · Encasement

The demo treats pipe-zone assumptions as geometry drivers so users can trace how standard details become QTO and cost categories.

Open cut / support

Trench · Sheeting · OSHA

Depth, width, soil, groundwater, support system, and open-trench buffer drive excavation, sheeting, disposal, production, and risk signals.

Restoration

Backfill · Pavement · Surface

Backfill, pavement area, asphalt tonnage, and restoration quantities connect the utility model to completion and billing templates.

Commercial bridge

QTO → ERP → Cashflow

Standard-driven quantities become L/M/C/S/E/R cost-code rows, SOV support, production curves, cashflow, variance and forecast signals.

Standards-to-controls flow

1. Standards basisRepresentative DEP sewer details define pipe/structure families, pipe-zone logic, excavation/restoration assumptions and QA boundaries.

2. GeometryThe model converts selected utility standards into station-based 3D geometry: pipe, trench, MH, CB, leads, backfill and pavement.

3. QuantityGeometry drives LF, CY, SF, SY, TON, EA and structure quantities with formula audit visibility.

4. ERP bridgeQuantities are organized into labor, material, consumable, subcontract, equipment and revenue/billing categories.

5. Field bridgeDaily production and actual cost records update earned value, productivity, billing progress and project forecast signals.

6. Executive lensCashflow, variance, risk, opportunity and forecast range move with the same construction simulation and quantity logic.

DEP sewer utility demo boundaries

Item	Public demo treatment	Reason
DEP standards	Representative standard-family logic, not official design approval.	Shows method without implying agency certification.
Geometry	Parametric and quantity-driven; not survey control or sealed design.	Good for demonstration, estimation logic and workflow design.
Quantities	Derived from model assumptions and visible formulas.	Useful for QTO/SOV templates, subject to contract reconciliation.
ERP / CMiC bridge	Demonstrates L/M/C/S/E/R mapping and exports.	Shows how field/project models can communicate with ERP structures.
Risk / opportunity	Scenario and randomized trend simulation.	Executive visibility; not a replacement for project controls judgment.

Public-safe disclaimer: Representative demonstration only. Not sealed design, not survey control, not official agency approval, not payment certification, and not a substitute for contract reconciliation.

Category roll-up

Schedule of Values — billing unit prices

Cumulative curves sampled at period ends

DEP-Style Open-Cut Construction Sequence

Activity register, Gantt storytelling, construction-front playback, and cash/EVM status stay synchronized to the same working-day clock.

Planned activity window Complete through selected day Playback day Click any bar to inspect its activity and linked model element.

Activity register — construction, controls, and element links

Activity forecast (EAC / ETC / TCPI)

Satellite mode

Optional

kept outside core 3D/QTO engine

Source of truth

Lat/Lon

start/end alignment inputs drive map line

Regression risk

Low

map layer fails gracefully

Satellite layer is optional. Enter a provider/token or use the schematic alignment fallback.

Satellite overlay rules

Safe architecture: keep satellite imagery as a geospatial context layer, not as a required model dependency. The 3D model, QTO, cost codes, field log, schedule, and cashflow must continue to run even when map libraries or tile services are unavailable.

Layer	Purpose	Regression guard
3D model	Geometry/QTO/selection	Never depends on satellite tiles
Satellite map	Site context and presentation	Optional Leaflet layer
Alignment polyline	Start/end lat/lon visualization	Fallback SVG/schematic if map fails
Export	GIS/KMZ/GeoJSON future	Use separate export function

Future GIS upgrades

GeoJSON export for pipe centerline, manholes, catch basins, work zones, and station ticks.
QGIS workflow note: import GeoJSON, set CRS, overlay with survey/base maps, then verify against contract drawings.
Optional MapLibre/Cesium mode later for larger corridors and 3D terrain.

What it is

An Artemis Field-to-ERP and Geometry-to-Cashflow demonstration system showing how controlled construction geometry can connect field production, quantities, cost codes, ERP-style structures, schedule, EVM, cashflow, risk, opportunity, variance, and executive decision support.

What it is not

Not sealed design, not survey control, not official agency approval, not a BIM replacement, not payment certification, and not an automatic pay estimate without contract reconciliation.

Best demo flow

Open with DEP Standards Lens, then Executive Control Room.
Fit model and show labels.
Select a pipe, manhole, trench, or restoration family.
Show QTO → cost codes → schedule → cashflow.
Finish with Geometry QA and known assumptions.

Benefits

Connects design geometry to cost and revenue.
Turns field logs into EVM signals.
Makes CMiC-style L/M/C/S/E/R coding visible.
Supports executive presentation and estimator review.

LinkedIn message

Artemis builds custom AI-assisted intelligence bridges between real operations and management systems. This construction demonstration shows how field reality, geometry, quantity, ERP logic, cashflow, risk, opportunity, variance, and trends can speak the same language.

Artemis program names

Field-to-ERP Bridge: field progress, labor, equipment, material, and revenue logic structured for management systems.
Geometry-to-Cashflow System: geometry and quantities connected to cost, billing, cash position, and forecast variance.
Field-to-Finance Intelligence: operational reality translated into commercial visibility.
Dynamic Controls Bridge: risk, opportunity, variance, and trends monitored as conditions change.

Executive control room

RC4 adds side-by-side live 3D model review and synchronized cashflow, production, cost variance, risk/opportunity, and forecast range charts for executive review, screenshot capture, and narrated LinkedIn video.

Pro tips

Use Clean mode for screenshots.
Use Field Log before EVM conclusions.
Use formula audit before presenting numbers.
Keep satellite as context unless georeferenced and verified.

Pitfalls

Do not treat schematic piles or utility envelopes as engineered design.
Do not mix assumed quantities with actuals without labeling source.
Do not let basemap imagery imply survey accuracy.
Do not overwrite baseline without a regression checklist.

Daily / weekly maintenance workflow

Frequency	Action	Why it matters
Daily	Update field log quantities, labor hours, equipment hours, material/subcontract costs.	Keeps EVM and forecast meaningful.
Daily	Record notes for delays, inspections, weather, utility conflicts, and design holds.	Creates claim/reconciliation traceability.
Weekly	Export schedule, cashflow, QTO, field log, and JSON snapshot.	Creates versioned backup and review package.
Weekly	Run Geometry QA and formula audit before sharing.	Prevents presenting stale assumptions.
Monthly	Reconcile billing revenue, actual cost, projected cost, retainage, and cash received.	Aligns model with PM forecast and payment reality.

Offline fallback is initializing…

Excavation Pipe Cradle Manhole Catch basin Sheeting / active

Selected fallback element

Click a fallback element to test simplified hit detection.

Runtime reliability checks

v1.4 lessons carried forward

Reliability purpose: this tab proves the app still has a native, dependency-light model sanity layer if Three.js, Chart.js, Leaflet, CDN access, or satellite tiles fail. It is not the official design model.

Best augmentation strategy

Method: keep v2.7/v2.8 as the base, add isolated reliability patches, and use v1.4/v2.3 only as references. Do not merge old files wholesale.

# v2.8 Augmentation Plan

## Base decision
Use v2.7 as the base because it already contains GIS context, guided presentation, offline QA scripting, view styles, and the mature v2-series 5D workbench shell. Use v1.4 and v2.3 as references, not as merge bases.

## Best augmentation methods
1. Additive stabilization layer rather than a full rewrite.
2. Restore missing DOM for any existing scripted feature before adding new features.
3. Add regression/health dashboard inside the app.
4. Default to light model-first mode, while preserving executive/blueprint/inverted styles.
5. Preserve offline fallback: canvas QA must work even when Three.js/Chart.js/Leaflet/CDNs fail.
6. Keep satellite separate from geometry/QTO. It is a context layer only.
7. Create a handoff tab with Claude/Codex prompt, upload manifest, and no-regression checklist.

## v2.8 changes applied
- Added missing Offline QA/Fallback tab page required by the existing v2.7 offline QA script.
- Added Handoff/Regression tab.
- Added startup aliases and compatibility guard for loadViewStyle().
- Changed default style to Light unless a user already saved another style.
- Added one-click Safe Model View.
- Added in-app regression scan.
- Added export buttons for Claude prompt, upload manifest, and handoff README.
- Updated visible version/title to v2.8 Stabilized Handoff.

## v2.9 RC2 changes applied
- Added internal 100%-fit density mode so the app is readable at normal browser zoom without relying on browser 75% zoom.
- Added a close Segment Detail camera mode inspired by the earlier compact/canvas workbench versions.
- Added a Segment button and D keyboard shortcut.
- Kept the changes additive: no QTO, schedule, EVM, cashflow, cost-code, field-log, GIS, or export math was intentionally changed.

## Manual review still required
- Open locally in a browser and check DevTools Console.
- Test with and without internet access.
- Click pipe, cradle, manholes, catch basins, sheeting, and fallback canvas objects.
- Export QTO, cashflow, schedule, JSON snapshot, formula audit, field log, and offline reliability pack.
- Confirm no assumptions are presented as signed/sealed geometry.

Upload manifest

Recommended upload set for Claude/Codex:

UPLOAD:
1. DEP_Sewer_Construction_Intelligence_Workbench_v2_8_STABILIZED_HANDOFF.html
   - Use as the only editable baseline.
2. DEP_Sewer_Construction_Intelligence_Workbench_v2_7_OFFLINE_QA_PRESENTATION_GIS.html
   - Reference only for previous GIS/presentation/offline QA intent.
3. DEP_Sewer_Parametric_3D_Workbench_v1_4_Enhanced_Fixed.html
   - Reference only for offline canvas, hit testing, and low-dependency fallback patterns.
4. DEP_Sewer_Construction_Intelligence_Workbench_v2_3.html
   - Reference only for QTO/export/schedule/cashflow logic.
5. This prompt/manifest file.

DO NOT UPLOAD unless specifically needed:
- Old failed experimental versions that had known undefined functions or broken screen layouts.
- Duplicate renamed copies of the same version.
- Screenshots unless the problem is visual/layout-specific.
- Unrelated apps from other projects.
- Large PDFs/standards unless you are explicitly asking Claude/Codex to update formulas from those sources.

Naming rule:
- Baseline to edit: one file only, named clearly with the highest stable version.
- References: mark filenames with REFERENCE_ONLY if possible.
- Output: increment version number and never overwrite the baseline.

Claude prompt

You are improving a single-file standalone HTML/CSS/JS app: “Artemis Construction Intelligence Workbench — LinkedIn RC2”.

Context files I am providing:
1. Artemis_Construction_Intelligence_Workbench_LinkedIn_RC1.html — current public-safe baseline to edit.
2. DEP_Sewer_Construction_Intelligence_Workbench_v2_7_OFFLINE_QA_PRESENTATION_GIS.html — prior baseline/reference only.
3. DEP_Sewer_Parametric_3D_Workbench_v1_4_Enhanced_Fixed.html — offline canvas/click-testing reference only.
4. DEP_Sewer_Construction_Intelligence_Workbench_v2_3.html — 5D/QTO/export/schedule reference only.

Goal:
Create the next safe iteration without regression. Preserve the working 3D/QTO/cost/schedule/cashflow logic. Improve reliability, geometry review, usability, presentation workflow, and handoff discipline.

Non-negotiable constraints:
- Keep it as one standalone HTML file unless I explicitly ask for a multi-file app.
- Do not remove existing cost-code, QTO, schedule, cashflow, EVM, field-log, formula-audit, satellite/GIS, tutorial, or offline QA features.
- Do not rename IDs/functions unless you also update every caller.
- Never let external libraries, map tiles, or satellite imagery become required for the core app to run.
- Do not treat the schematic model as sealed design, survey control, or official DEP approval geometry.
- Maintain L/M/C/S/E/R suffix logic: Labor, Material, Consumable, Subcontract, Equipment, Revenue/Billing.
- Preserve the alias loadViewStyle(style) -> applySpaceStyle(style) so old prompts/scripts do not break.

First perform static review:
- Identify missing DOM pages for existing tabs.
- Check for duplicate IDs and duplicate function declarations.
- Check every event-binding ID exists.
- Check renderAll/recalcAll does not fail when a tab is hidden or a library is missing.
- Check click/hover selection cannot be stolen by large transparent geometry.
- Check overlay panels cannot block the model permanently.
- Run JS syntax validation before returning the final file.

Best augmentation priorities:
1. Reliability shell: startup health check, visible warnings, offline fallback, syntax/regression checklist.
2. Model-first UX: default light view, one-click safe view, collapsible/relocatable HUD/legend/inspector, large viewport.
3. Selection QA: object priority, parent/child/sibling navigation, clear clicked element data, no transparent picking blockers.
4. Geometry QA: show formulas, assumptions, source/basis, sanity checks, and “not sealed design” warnings.
5. 4D/5D review: keep construction-front sequence, cashflow, billing lag, retainage, EVM, and field actuals tied to selected elements.
6. GIS discipline: satellite/context is optional; add GeoJSON export later, but keep fallback schematic when tile services fail.
7. Handoff discipline: include upload manifest, regression checklist, Claude/Codex instructions, and version notes inside the app.

Implementation request:
- Create a new version named v2.9 only after v2.8 passes regression.
- Add only additive or carefully isolated patches first.
- If refactoring, separate refactor from feature changes.
- Provide a change log and list exactly what was tested.
- Return the complete updated HTML, not a fragment.

Expected output:
- A complete HTML file.
- A short summary: what changed, what was preserved, what tests passed, what still needs manual review.

Codex vs regular chat

Regular chat best for architecture, prompt design, reviewing screenshots, and deciding what to upload.

Codex best for editing the actual HTML, running checks, comparing diffs, and making repeatable no-regression changes across versions.

Model Status

Cash Flow

Cost Variance

Production Trend

Risk / Opportunity

Forecast Range

RC7 Publication Capture Studio

Selected Element

Quantities — Est / Actual / Projected

Cost & Billing — Est / Actual / Projected

Clickable Element Intelligence

Model Hierarchy

Keyboard