Precon Estimator Workspace Workflow

Summary

The estimator workspace is where Precon composes the opportunity story: documents, chronology, solicitation truth, sizing, RFI candidates, planning state, notes, readiness, and action panels. It is the broadest child workflow because it is where source evidence becomes usable preconstruction context.

The concept page Precon Estimator Workspace orients the primitive. This thread explains how the workspace ties together the other child workflows.

Reader Question

How does Precon present a coherent estimator workspace without making the UI own document, sizing, planning, or RFI truth?

Surface Or Workflow

Operators use the pursuit workspace, workspace brief, chronology panel, workplan panel, RFI panel, action panels, artifact panels, and document sections. Engineers enter through workspace read models, chronology builders, timeline registries, planning services, document explorer services, and workspace API routes.

Lifecycle

The workspace starts from the opportunity root. It loads current opportunity state, solicitation context, document artifacts, planning assignments, sizing precedence, chronology events, RFI state, and readiness. It then presents that state in tabs and panels that reflect operator questions rather than database tables.

Actions flow back through explicit API routes and services. Workspace notes, planning changes, RFI edits, document review, and bid decisions should leave audit evidence or service-owned state changes.

Child Threads

Implementation Boundaries

Workspace UI lives under app/web/app/precon/opportunities/workspace; API routes under app/api/precon/opportunities/workspace_routes.py; services under services/precon/opportunities/workspace; shared contracts under libs/precon/opportunities/workspace. Planning and document context come from their own services rather than from workspace-local SQL.

Tradeoffs

The workspace deliberately composes many services. That makes the page more complex, but it protects the ownership boundaries that let sizing, RFI, documents, and planning evolve independently.

Visual

The current visual is a graph neighborhood. The intended visual is a workspace composition map showing opportunity root, documents, chronology, sizing, RFI, planning, actions, and audit events.

Source Evidence

  • docs/engineering/concepts/precon-estimator-workspace.md
  • app/web/app/precon/opportunities/workspace
  • app/api/precon/opportunities/workspace_routes.py
  • services/precon/opportunities/workspace
  • libs/precon/opportunities/workspace
  • services/precon/planning
  • services/precon/opportunities/document_explorer
  • tests/precon/test_opportunity_workspace_chronology_timeline.py