PRODUCT / HONEST CAPABILITY STATUS

Working foundations.
A bigger direction.

The complete preconstruction platform is the destination. The desktop source audit identifies narrower, human-operated foundations. Code presence is not the same as production validation.

01 / SOURCES

Keep the revision attached to the review.

Local desktop code includes PDF-page viewing, embedded text extraction/search and explicit cited-passage capture for registered source revisions.

Audit boundary: not comprehensive OCR, automatic drawing interpretation or complete plan takeoff. Native runtime acceptance was not established by the cited source audit.

LOCAL PDF REVIEWREVISION REFERENCEEXPLICIT EVIDENCE
02 / SCOPE

Document missing coverage without inventing scope.

Manual review surfaces can record scope gaps and distinguish documented technical scope from a subcontractor bid coverage gap.

Audit boundary: no verified fully automatic completeness review or autonomous scope creation.

MANUAL GAP REVIEWSCOPE CONTEXTHUMAN FOLLOW-UP
03 / PACKAGES

Prepare trade packages and RFP drafts.

Audited desktop code includes scope-linked bid-package preparation, spreadsheet-readable bid forms and a user-controlled draft handoff to a mail application.

Audit boundary: no autonomous invitation sending or evidence that a subcontractor received the request.

PACKAGE DRAFTBID FORMPERSON SENDS
04 / COMMERCIAL

Level the bid without changing what the bidder said.

Bounded lump-sum bid leveling code supports human-selected internal allowances and package adjustments, with the stated amount kept distinct from internal commercial treatment.

Audit boundary: general unit-price leveling, award decisions and a complete automatic estimate are not verified operating capabilities.

BIDDER-STATED AMOUNTHUMAN-DIRECTED PLUGREVIEWABLE BASIS
05 / REASONING

Leave a trail for the next reviewer.

Source and evidence review, human treatments and decision-history surfaces are represented in the audited desktop code. The intent is that decisions travel with their reason.

Audit boundary: full approval authority, policy promotion and production workflow acceptance require separate verification.

HUMAN DECISIONREVIEW CONTEXTNO AI APPROVAL
CAPABILITIES NOT YET VERIFIED AS RELEASED

What this website will not pretend.

Fully automated drawing interpretation or scope discovery; general quantity takeoff; comprehensive proposal ingestion and estimating; owner-proposal generation; active cross-project Company Mode and company-learning; automated data shedding (Coming soon, not available now); autonomous procurement or approvals; and fully automated AI execution are not being marketed as finished production features.

The boundary is deliberate: a doctrine requirement, partial implementation, passing unit test and observed release are different things.

THE ROAD AHEAD

Built in stages.
Transparent about each one.

See how the bounded product foundations fit into the complete planned preconstruction chain and where company-level knowledge is intended to enter.

PRODUCT DIRECTION

Owner proposal continuity

Connect approved scope and pricing decisions to audience-appropriate owner presentations.

PRODUCT DIRECTION

Cross-project knowledge

Use authorized historical context to inform new projects while preserving relevance and supersession.

IN DEVELOPMENT

Company governance

Company-specific practices require trustworthy authorization before authoritative policy transitions can be enabled.