Running full project analysis
Full analysis operates on a selected, authorized project record and produces a source-linked set of findings for human review.
Reference version 1.1 · Updated September 4, 2026
Admit and scope the source record
Validate the source, assign project and tenant identity, record the content hash and document category, and select the processing path before deeper work begins.
Process, retrieve, and analyze
- Create addressable text, rendered-page, single-page PDF, and localized visual artifacts where available.
- Build tenant-scoped text and image representations with document and page provenance.
- Retrieve evidence for each typed project need and run the approved specialist workflows.
- Reconcile material rows, conflicts, quantity support, warnings, and open questions.
Assemble a reviewable output
GAIA Civil assembles the Qualified Opportunity Report with citations, calculation records, uncertainty, report state, ownership, and proposed next action. The report remains inside the review boundary until an authorized person approves the next handoff.
Detail: seven stages and the record each creates
| Stage | Work | Record created |
|---|---|---|
| Scope | Resolve project and document scope; build stable citation context. | Project snapshot, source manifest, coverage, enabled skills |
| Scale & measurement | Assess documented quantities, scale evidence, geometry, and input gaps. | Measurement audits, calculations, assumptions, confidence, questions |
| Evidence collection | Retrieve project, product, and engineering evidence for each need. | Need-linked evidence groups and source citations |
| Engineering analysis | Apply engineering rules, calculations, and enabled domain methods. | Typed engineering analysis and calculated quantities |
| BOM reconciliation | Match product recommendations to authorized needs and evidence. | Candidate products, need IDs, quantities, rationale, confidence |
| Report assembly | Build modular report sections and client-visible methodology. | Qualified Opportunity Report, sources, warnings, appendix |
| Review & follow-up | Select evidence-backed actions, drill-downs, and optional QA supplements. | Actions, open questions, evidence review, final version |
Detail: the technical analysis sequence
| Step | Stage | Work | Record created |
|---|---|---|---|
| 01 | Resolve an authorized project snapshot | Select active, processed project documents and start a new evidence snapshot. Direct attachments must be ingested before they can influence a citation-addressable report. | Authorized document IDs, snapshot identity, processing eligibility, and any rejected attachment or scope condition. |
| 02 | Create a stable evidence order | Retrieve, deduplicate, and select project context before prompts, context PDFs, and final source objects are assembled. | An ordered source ledger and bounded context package whose source positions remain stable through later stages. |
| 03 | Extract typed project needs | Validate project metadata, contacts, need IDs, locations, dimensions, specifications, incumbent material, candidate context, and preliminary quantity fields. | Validated need groups with stable IDs, source locators, populated fields, and explicit missing or invalid inputs. |
| 04 | Assess scale and measurements | Determine whether a quantity is source-based, independently measured, estimated with stated assumptions, conflicted, or needs more input. | Measurement audits containing scale, geometry, formula, named inputs, units, assumptions, cross-checks, conflicts, and status. |
| 05 | Retrieve evidence per need | Fan out targeted project, product, and engineering evidence retrieval for each validated need group. | Need-linked evidence bundles with category, document, page, asset, relevance, and visible no-evidence outcomes. |
| 06 | Run engineering and product analyses | Apply separate specialist roles and only the tenant-enabled civil analysis skills assigned to those roles. | Typed engineering rationale, rules, calculations, candidate products, product evidence, warnings, and reviewer questions. |
| 07 | Verify and reconcile material rows | Normalize references, exclude rows disconnected from authorized needs, and retain product, pursuit, and quantity confidence separately. | Normalized BOM rows linked to authorized need IDs, plus exclusions, reconciliation warnings, and separate confidence fields. |
| 08 | Assemble the core report | Create project, BOM, summary, opportunity, strategy, needs-review, calculation, evidence, and appendix sections from validated artifacts. | A versioned report contract with sections, sources, methodology, warnings, calculations, review states, and coverage metadata. |
| 09 | Prepare selective follow-up | After the required report exists, generate bounded actions, material-gap drill-downs, and optional managed evidence/engineering QA review. | Zero to three evidence-backed actions, targeted gap questions, optional QA findings, and the responsible review path. |
Need help applying this page to an evaluation?Ask a product question