Every plan.
Every detail.
Connected.

An organized workspace for owners, public agencies, construction managers, designers and contractors.

• Account and profile

  Manage profile, password, organization identity and branding.

• Project portfolio

  Create and open authorized projects; review active, closeout, archived and permitted trash views.

• Account overview

  Use portfolio summaries and project selection to reach the right job.

• Project control center

  Access project tools, current work, updates and available records from one starting point.

• Task-oriented menu

  Use grouped navigation for home, field work, plans, reviews, schedules, costs and closeout.

• Find a project tool

  Search navigation labels to locate a supported section quickly.

• Quick access

  Open common records through account/project shortcuts.

• Visible authority context

  See customer, project and current authority so actions are taken in the right workspace.

• Organizations and users

  Assign participating organizations, project team members, roles and effective permissions.

• Notifications and activity

  Review notifications, assigned actions and AI activity/audit information.

• Page help and language controls

  Use contextual guidance and available interface language options.

• Field application controls

  Configure licensed project, organization and person-level access; device enrollment and operating-system permissions remain separate.

Scope and availability: Module visibility depends on licensing and effective permissions. Device access follows the applicable client, browser and operating-system requirements.

Keep responsibility, review authority and record history explicit.

• Project identity and settings

  Maintain the job identity, participating parties and supported administrative settings.

• Contract basis

  Record contract details, notice to proceed and the relevant review/payment clock inputs.

• Project team and routing

  Configure responsible organizations and supported review routes for each record type.

• Distinct actions

  Separate creating, submitting, responding, reviewing, verifying and approving according to effective authority.

• Current ball-in-court

  Identify the current responsible party and workflow state.

• Multi-step / parallel review

  Use supported route and approval semantics with accountable transitions.

• Route revisions and history

  Preserve earlier route steps and decisions when a current route is amended.

• Content sealing

  Bind supported certifications and finalized records to their content identity and attribution.

• Linked corrections

  Create eligible correction revisions while preserving original sealed RFI/submittal content.

• Forms and signatures

  Use configured templates and supported signing workflows with required fields and signing authority.

• Audit events

  Retain attributable record and status history across governed workflows.

Scope and availability: Routes differ by record type and project configuration. A content seal records identity and attribution, not the correctness of an engineering judgment.

Bring supported project records into a current, permission-aware investigation workspace.

• Current project-world view

  Combine authorized RFIs, submittals, schedules, drawings, field observations and available energy records.

• Evidence freshness and coverage

  Show the age and coverage of available information rather than implying complete live awareness.

• Selected gap detection

  Identify supported missing answers, references, assignments and review information.

• Investigation drafts

  Prepare source-linked next-step drafts from selected findings.

• Owner settings

  Control eligible monitoring and learning through authorized opt-in settings.

• Bounded scan execution

  Retain scan progress and handle eligible retry, resume, pause and stalled work.

• Outcome feedback

  Record accountable adjudications with source-version context.

• Priority and calibration review

  Evaluate supported candidates against later records before adoption.

• Reusable read-only investigations

  Activate supported tested workflow patterns under owner control.

• Schedule rehearsal

  Explore bounded imported-network scenarios and retain assumptions and calculation evidence.

• Manual energy readings

  Record energy, fuel and demand separately with units, time and source attribution.

Scope and availability: The Living Project workspace and the asset/sensor intake are complementary foundations. They do not currently constitute a fully synchronized operational digital twin.

Additional setup, commercial handoff and exchange functions included in the reviewed platform.

• Project operating profile

  Record supported sector, delivery method, contract duration and site coordinates.

• Sourced contract clocks

  Associate clock settings with the applicable source and delivery-evidence requirements.

• Recoverable project deletion

  Use eligible trash/recovery controls alongside archive and lifecycle permissions.

• Preconstruction clearances

  Track readiness, award/agreement clearances, authorities, organization policies and follow-ups.

• Procurement and long-lead items

  Maintain supported procurement-item tracking and mobilization/NTP handoff information.

• Takeoff calibration and measurements

  Record supported source calibration and measurements before relying on derived quantities.

• Bid-basis capsules

  Retain supported source-basis information with controlled estimate publishing and handoff.

• Schedule acceptance and history

  Record acceptance/rejection, supported mappings, activity data and analysis history for imported versions.

• Billing findings and exports

  Review payment-application findings and prepare supported accountant exports.

• Accounting exchange setup

  Maintain supported mappings, dry runs, approved exchange and reconciliation; an external provider must be configured and supported.

• Portfolio reporting

  Use supported cross-project summaries and export under effective account access.

• Field-client governance

  Apply licensed project, organization and person-level controls to eligible field-client operations.

Scope and availability: Configured agreements and signatures are not an unrestricted legal contract-authoring system. Generalized Workflow Studio, fleet/GPS intelligence and comprehensive offline resilience are not established by these functions.

Deployed on-demand foundation; its evidence compilation is distinct from a fully verified digital twin.

• Cross-register state compilation

  Compile accessible schedule, labor, change, billing, meetings, permits, safety, quality, daily and integration record state.

• Typed evidence presentation

  Distinguish facts about stored records from assertions in those records, unsupported proof and restricted registers.

• Unsealed record citations

  Provide scoped database references with explicit unsealed status and bounded per-register coverage.

• Accepted-schedule gate

  Distinguish submitted schedule versions from the recorded accepted schedule of record.

• Missing-Proof Radar

  Expose absent records and domain evidence that has not yet been verified.

• Authority-aware proof requests

  Prepare reversible proof-request text with the current brief attached only for an authorized preparer; no automatic sending or record insertion.

• Review-bundle export

  Download state, references, refusals, authority and draft/refusal as JSON with a payload SHA-256 fingerprint, not a digital signature.

• Fresh-state controls

  Refresh state, reject stale results and explain restricted access without inferring authority from an administrator title.

Scope and availability: Continuum continuous compilation and integrated sealed-evidence verification are separate unfinished work. The released contract workspace has its own signed journal and portable archive; that does not automatically complete their integration into Continuum.

Recent public-demo and account-reuse development.

• Shared synthetic project story

  Prepare one coherent fictional park/restroom project with linked construction records.

• RFI evidence examples

  Populate ten fictional RFIs with supporting sample PDFs and source relationships.

• Material submittal examples

  Include CMU, concrete, doors, pavers and drinking-fountain submittal examples.

• Prepared transmittal and pay examples

  Provide labeled transmittal covers and a draft pay-application summary.

• Complex change examples

  Populate multiple detailed change orders linked to the synthetic project story.

• Schedule and look-ahead examples

  Populate baseline/update and look-ahead examples for read-only exploration.

• Permits and job-walk examples

  Populate candidate permits and a multi-item field walk with related evidence.

• Procurement and budget examples

  Link fictional procurement items to submittals/activities and populate budget lines.

• Preconstruction checklist examples

  Assign and date the prepared preconstruction checklist in the demonstration.

• Real synthetic IFC processing

  Process the fictional BIM model through TRACE extraction; the recorded demo has geometry for 49 modeled objects.

• Visitor read-only boundary

  Candidate visitor controls deny uploads, mutations, processing, live AI execution and unauthorized account-directory access.

• Registration and access expiry

  Candidate visitor registration, verification, expiration and functional-demo request forms remain under integration acceptance.

• Section completeness audit

  Audit meaningful contents and detail views across 38 project sections; an HTTP success alone does not close the section.

• Training coverage development

  Track section guidance, examples and training-video gaps separately from the sample data.

• Blueprint tenant reuse

  Recorded staging acceptance exports/imports a blueprint into a new tenant with empty destination business records.

• Destination publication and write

  Validate independent destination publication, authorized writes, suspended writes and cross-tenant denials.

• Signed customer setup journey

  Accepted on current isolated staging: expired setup link denied, normal password setup and correct-tenant login passed, and reused setup POST was rejected.

• First-login navigation correction

  The corrected same-origin /app.html navigation passed normal-browser acceptance, including original-password login after attempted setup-link reuse and logout.

• Native parsed demo schedule

  The synthetic project has an accepted-for-training MS Project XML revision with 25 activities, 34 finish-to-start links and 66 working days; the actual risk builder consumes it.

• Published synthetic BIM model

  The real extraction produced 49 geometric products and 52 hierarchy/element records, published inside the synthetic project.

• Indexed demonstration references

  The newest demo additions include seven indexed PDFs totaling 18 pages, four plan sheets and four drawing images.

• Web-service file readability

  The demo owner corrected folder ownership and verified 46 of 46 files readable by the web-service user.

• Prepared internal demo access

  The synthetic project and records exist in a separate live tenant. Public visitor signup/access, full section acceptance and training remain separate work.

Scope and availability: The shared public visitor experience remains in preparation at this checkpoint. Synthetic examples are not customer work, physical inventory or completed approvals.

Current update (September 9, 2026): the shared synthetic project is now published through private, seven-day, read-only visitor sessions. Uploads, edits, processing and live AI execution remain disabled. This supersedes the earlier preparation checkpoint in the source register.

Evidence-grounded assistance for construction administration, investigation and preparation.

• Ask TRACE

  Ask typed or voice questions, including informal wording and follow-ups. Choose quick lookup, an answer with sources or detailed investigation; edit scope-specific suggested questions before sending.

• Product help and training

  Find screen guidance, navigation help and explanations of supported workflows through a separate product-help knowledge base.

• Project-context assistance

  Use authorized project documents and supported structured records as evidence for project questions.

• Structured interpretation

  Separate recorded facts, inferred consequences, assumptions, competing evidence and missing information.

• Risk and schedule reasoning

  Explain supported implications, highlight missing logic, calendars or baselines, and propose a next verification step.

• Cited answers and support checks

  Attach source references to supported findings; identify insufficient evidence rather than invent a project determination.

• Answer, draft, classify, compare and educate

  Supported queued assistance tasks prepare material in an authorized record context, subject to evidence and access controls.

• Professional decision boundaries

  Keep formal engineering, safety, legal, approval and permission-to-build decisions with the authorized person.

• Run history and accountability

  Retain AI activity, run identifiers, source context and supported review/feedback information.

• Request recovery

  Recover eligible long-running requests with the same request key and avoid duplicate model calls for repeated submissions.

• Voice interaction where available

  Use supported voice entry/output subject to browser, device permissions and configured service availability.

Scope and availability: AI availability depends on the enabled module, configured provider and usage allowance. Fluent output is not evidence of correctness.

Source selection is enforced before evidence reaches the reasoning model.

• This project

  Restrict retrieval to the current authorized tenant and project, with matching source and passage identity.

• General knowledge

  Search eligible shared reference material without carrying project context into that search.

• Combined search

  Use the authorized project plus separately identified general references; do not mix in another project.

• Web research boundary

  Project-only and combined project-bearing prompts do not use public web research. Permitted general research is a separate path.

• Source authority

  Distinguish project records, reviewed references, general guidance and assertions; a reference is not automatically a governing requirement.

• Edition and adoption context

  Retain available edition, jurisdiction and applicability metadata so the user can establish the controlling source.

• Permission-aware retrieval

  Apply current access rights to records and evidence, including API and queued worker paths.

• Scope-switch reset

  Clear prior questions, answers, citations and voice state when changing source scope.

• Late-response protection

  Reject stale results after account, tenant, project, source-mode or relevant revision changes.

• Project-private improvement records

  Keep failure curricula scoped and private; do not turn one customer's questions or project documents into another customer's knowledge.

Scope and availability: Shared general references and project-private evidence remain distinct. General references must be evaluated for actual project applicability.

Turn supported files into inspectable evidence while preserving their source identity.

• Digital document ingestion

  Extract supported born-digital documents into searchable passages with source and page context.

• Scanned PDF and image OCR

  Retain extraction method, page identity and available confidence/region metadata for scanned notes and images.

• Page-preserving reference extraction

  Retain native PDF page numbering and layout-oriented text; open the original PDF page to verify tables, symbols and context.

• Immutable source identity

  Use content fingerprints and revision links to identify the exact evidence used.

• Source-linked passage retrieval

  Search relevant passages and supported structured project facts rather than treating all text as equally authoritative.

• Citation inspection

  Open available source references and inspect the cited passage or original document.

• Proof collection

  Collect supported answer evidence into proof items for review and communication.

• Proof preview and PDF export

  Preview, print or download supported exhibits, reports and source manifests.

• Safe upload admission

  Apply supported file validation, scanning and ingestion gates before protected evidence becomes usable.

• Reference-pack quality checks

  Validate candidate hashes, page counts, page identity, empty/missing pages, safe paths and provenance metadata.

• Controlled source expansion

  Add eligible references through extraction and quality review; preserve approval states and edition metadata.

Scope and availability: Layout-oriented text does not preserve every visual relationship. OCR alone does not establish dimensions, scale, linework or design intent.

The deployed reference expansion includes eight complete retained federal publications, totaling 524 PDF pages, plus 24 original TRACE workflow guides.

• Electrical engineering

  UFC 3-501-01: electrical engineering reference material with page-linked source access.

• Mechanical / HVAC

  UFC 3-410-01: heating, ventilation and air-conditioning reference material.

• Civil engineering

  UFC 3-201-01: civil engineering reference material.

• Plumbing

  UFC 3-420-01: plumbing systems reference material.

• Cost estimating

  UFS 3-740-05: construction cost-estimating reference material.

• Schedule specifications

  UFGS 01 32 01.00 10: project schedule guide specification.

• Quality control

  UFGS 01 45 00: quality-control guide specification.

• Safety requirements

  UFGS 01 35 26: governmental safety requirements guide specification.

• Existing reference records

  Eligible existing Greenbook and selected OSHA reference records remain subject to their recorded rights, readiness and approval states.

• Workflow knowledge

  Original TRACE guidance explains common processes. Eligible exact guide matches can return cited guidance without a model call; the complete title index appears later in this document.

• Source transparency

  Retained editions, original PDF links and extraction provenance identify what is actually in the deployed pack.

Scope and availability: This is not an all-codes library. Referenced commercial standards are not included by reference. Full OSHA, FHWA and GAO libraries were not added by this expansion; full Greenbook fidelity was not newly certified.

Prepare the next step while keeping issuance, approval and contractual decisions under human control.

• RFI assistance

  Investigate a question using authorized evidence and prepare supported wording or next-step guidance.

• RFI follow-up draft

  Generate an editable follow-up from the current RFI and workflow record; nothing is automatically sent or issued.

• Change-review worksheet

  Prepare a structured review draft tied to the current record, with missing evidence left visible.

• Daily narrative assistance

  Rewrite submitted daily notes into an editable narrative with fact-preservation checks.

• Submittal preparation support

  Use cited assistance to prepare questions and review material alongside the separate accountable submittal workflow.

• Notice and correspondence preparation

  Use supported drafting assistance with authorized context; review the controlling clauses and factual basis before use.

• Living Project investigation drafts

  Prepare source-linked drafts from selected evidence gaps for an authorized reviewer.

• Reusable investigation workflows

  Propose and evaluate bounded read-only investigation patterns from reviewed outcomes before owner activation.

• Formal-action separation

  An AI draft or recommendation does not itself approve a submittal, close an inspection, issue a notice or change the contract.

Scope and availability: A follow-up template is not an autonomous legal analysis. Autonomous bid-protest issuance and a comprehensive automated technical submittal compliance matrix are not delivered claims.

Interpret recorded project conditions and make missing inputs visible.

• Project risk assessment

  Review supported project risk evidence, record context and identified gaps.

• Confidential forward look

  Show cumulative 7-, 14- and 30-day RFI/submittal review due horizons in the authorized confidential assessment.

• Overdue and aging work

  Identify overdue, undated and aged actions without inventing missing deadlines.

• Separate workflow histories

  Keep RFI and submittal completion rates separate, respecting current route cycles and parallel approvals.

• Conditional backlog scenarios

  Estimate remaining review workload only when the required positive completion history exists for each active record type.

• Data sufficiency gates

  Require at least eight positive completions spanning three of four weeks for each active type; return unavailable when the evidence is insufficient.

• Completion quality filters

  Exclude returned, rejected and future completions from the positive completion basis.

• Schedule readiness signals

  Highlight missing or stale accepted schedule evidence.

• Refresh-time operational feeds

  Read current structured workflow and schedule records when the assessment refreshes.

• Scope and privacy controls

  Keep confidential forecasts out of shared/compact views and reject results for a previously selected project or period.

Scope and availability: These are descriptive workload scenarios, not trained delay probabilities, proof of physical progress, legal causation or a guarantee of future performance.

Use selected images and a specific plan page to prepare a traceable visual review.

• Photo and plan inputs

  Submit supported field images and select the relevant PDF plan page for comparison.

• Exact revision and page binding

  Bind the review to the source plan revision and selected page rather than an unspecified drawing set.

• Multimodal interpretation

  Use the configured vision provider to analyze the selected image evidence and plan page together.

• Reviewable observations

  Present supported observations, uncertainty and information requiring field confirmation.

• Evidence-linked persistence

  Retain the source references and review output with the authorized record context.

• Human review notes

  Add accountable review information rather than treating a visual suggestion as an accepted field determination.

• Response validation

  Validate the provider's structured response, required shapes and completion state before admitting a result.

• Protected upload workflow

  Use file and page extraction gates; preserve access boundaries across upload, analysis and replay.

• Stale-view protection

  Prevent a previous project's visual result from replacing the current view.

Scope and availability: Delivered scope is assisted review of selected inputs. Automatic drone-feed monitoring, survey registration, measured alignment deviation, soil-condition diagnosis, automated takeoff from photos and certified installed-work verification are not established.

Improve selected workflows through measured, controlled changes rather than autonomous foundation-model training.

• Scheduled failure capture

  Collect bounded failure signals into private, scoped evaluation curricula.

• Data-minimized curricula

  Use run references rather than publishing raw customer questions into shared learning material.

• Curated vocabulary candidates

  Evaluate fixed retrieval aliases for the original public workflow guides.

• Held-out evaluation

  Compare a candidate on separate labeled cases before activating it.

• Regression protection

  Require preservation of previously passing cases for the eligible vocabulary candidate.

• Experiment identity

  Avoid repeatedly tuning identical experiments against the same holdout; reject stale fingerprint selections.

• Reviewed outcomes

  Record source-versioned human outcomes for selected administrative findings.

• Calibration candidates

  Evaluate selected priority/calibration changes against later, different records before owner activation.

• Reusable skill candidates

  Test bounded investigation patterns before activating supported read-only workflows.

• Opt-in continuous watch

  Process bounded scans, retain progress and recover eligible stalled work with retries, pause and health information.

• Owner control

  Require the applicable authorization for activation, monitoring and return to baseline.

Scope and availability: No autonomous model-weight training or unrestricted self-modifying code is deployed. Continued improvement needs maintained sources, new validated candidates and evaluation; it is not guaranteed every day or year.

Deployed additions verified in the interpretation, schedule-reasoning, research and RFI release records.

• Informal question interpretation

  Handle typos, shorthand, alternate meanings and standard-family hypotheses while retaining the original question.

• Bounded multi-aspect investigation

  Consider sequence, staging/access, crews, equipment, procurement, temporary works, testing holds, permits, handoffs, mitigation and counterevidence when supported.

• General-reference explanation

  Explain a standard as general guidance without requiring project adoption; keep binding project determinations separate.

• No-match research fallback

  Eligible general questions may continue to official public research when related local passages still cannot answer the question.

• Advanced research fallback

  The documented difficult-general-research fallback uses gpt-6-astra after the primary provider cannot release a cited answer; this is an application component, not a TRACE-trained foundation model.

• Citation validation

  Validate citation ranges and Unicode offsets; reject incomplete provider output and unsupported assertions rather than releasing partial text as verified.

• Truthful research history

  Distinguish research actually attempted from a setting merely being enabled; record provider usage and cost.

• Schedule evidence context

  Provide authorized baseline/latest revision, disposition history, methodology, bounded activities/relationships, import assumptions and exact-version comparisons.

• Competing delay explanations

  Examine overlapping delays, mitigation and completion impact; distinguish calendar days from working-time float and request missing CPM evidence.

• Saved Office chart extraction

  Read saved XLSX/PPTX chart series, categories, values, labels, number formats and formula references. Do not evaluate formulas or follow external links.

• Exact RFI conversation binding

  Load subject, question and references from the authorized RFI ID; preserve linked follow-ups only while that project and RFI remain active.

• Public proof tools

  Show proof, collect all eligible references, prevent duplicates and print answer proofs through an in-app preview.

• Direct proof PDF download

  Export supported complete text, tables, technical symbols, citations and eligible original source-page images without depending on the browser print dialog.

• Mixed proof identity

  Reauthorize indexed passages; distinguish archived source evidence from public URL references that have not been archived.

• Request replay protection

  Serialize/replay eligible requests by authenticated user and submission key; reject key reuse for a changed question and avoid duplicate model calls.

Scope and availability: Known limits include intermittent P6 answer-release failures, variable research latency, and saved chart caches that can be stale. These are not guarantees of universal answer accuracy.

Implemented opt-in administrative improvement; activation and usable evidence are prerequisites.

• In-project reviewed outcomes

  Retain explicit source-versioned human adjudications and append-only corrections within the project.

• Chronological source-disjoint evaluation

  Evaluate on later unseen records rather than reusing the same source in training and testing.

• Reviewer diversity gates

  Apply minimum distinct-record and reviewer-diversity/concentration requirements before eligible candidate promotion.

• Baseline and incumbent comparison

  Compare eligible ranking candidates against baseline/current behavior, including per-kind regression and Brier-score checks.

• Bounded learning history

  Refuse candidate promotion from truncated history beyond the supported 2,000-review cap.

• Correction invalidation

  Invalidate dependent learning when source evidence is corrected or access is revoked.

• Owner promotion and rollback

  Keep candidate activation explicit and permit return to the baseline.

• Declarative skill proposals

  Propose read-only investigation patterns from repeated substantiated outcomes; test later reviewed records before owner activation.

• Resumable monitoring

  Use bounded source generations, durable cursors, fenced leases and atomic finding/checkpoint writes.

• Fair scheduling and suspension

  Process due projects with fresh authorization, retry/pause behavior and owner opt-out; do not treat platform support as unattended authority.

• Uncertainty-reduction scenario

  Compare supported paired readiness/duration scenarios and identify the next fact that reduces remaining uncertainty.

Scope and availability: Learning currently covers selected administrative RFI/submittal finding kinds. Metrics are observational and exposure-biased, not foundation-model retraining, physical verification or guaranteed improvement.

Detailed implementation distinctions retained from the AI audit.

• Deterministic clarification

  Offer bounded follow-up choices for broad construction questions without reading private evidence or spending model tokens.

• Structured field-day evidence

  Retrieve authorized daily, job-walk, quality, safety and time-record facts with operational citations.

• Sourced contract clocks

  Include clock settings only with explicit source, day count and working/calendar basis; do not substitute unsourced settings for contract terms.

• Authority, applicability and operativity

  Distinguish retrieval relevance from controlling authority, effective time, jurisdiction, project area/system/phase and amendment effects.

• Qualifying evidence lanes

  Retain exceptions, conditions, alternatives and supersession alongside direct matches; a classifier alone does not establish a legal conflict.

• Optional exact-evidence review

  A separately configured reviewer can assess a draft against its cited passages without browsing, retrieving new evidence, adding citations or executing actions.

• Private shadow curriculum

  Capture corrections, rejections, no-match and escalation signals into a scoped curriculum. This shadow layer does not itself change live answers.

• Measured public-guide retrieval improvement

  A fixed 31-alias candidate improved one small held-out top-topic evaluation from 14/18 to 15/18 while preserving eligible passing cases; this is not general answer accuracy.

• Fingerprint-bound retrieval activation

  Bind eligible activation to pack, dataset, algorithm and registry identities; corrupt or stale state falls back to baseline.

• Route-aware workload counting

  Count any-one review groups once at the earliest due action, all-required groups separately, and exclude inactive future steps.

• Recovery semantics gate

  The resource-recovery planner supports bounded unstarted fixed-duration DAGs with FS/nonnegative lag and ASAP/SNET releases plus explicit calendars. Unsupported SS/FF/SF, actual progress, splitting, overtime and inferred productivity are refused.

• Narrative fact preservation

  Rewrite supplied daily notes in English or Spanish while preserving facts, numbers, negations and uncertainty; do not add unsupported blame or causation.

• Provider-team distinction

  Gemini, Grok and Claude consultations helped development reviews; they are not established as a three-provider vote on every customer answer.

Scope and availability: Reference extraction is automated rather than named human fidelity review. Attempted but blocked GAO, OSHA 3886 and USACE CQM source downloads were not ingested. UFS is a nonmandatory reference and UFGS documents are templates requiring tailoring/adoption.

Integrated customer-panel viewing and review controls; original source files remain preserved.

• Internal document viewer

  Open supported authorized PDF/image documents inside TRACE, navigate available pages and download the original.

• Internal CAD workspace

  Choose a current-project DWG and exact version, then open the converted drawing inside BIM without requiring an external CAD application for the supported review functions.

• Internal 2D controller

  Select entities, search source handles, pan, zoom, fit, switch layers, restore converted visibility, add notes, draw polylines and measure approximate XY distances.

• Internal XYZ controller

  Orbit, pan, zoom and fit source XYZ line/point geometry; apply explicit Z-range, zero-Z and vertical-display controls. The 2D layer switches do not automatically filter this XYZ view.

• Internal solid-surface controller

  Select one actual POINT layer, build the shaded surface, inspect low/high colors, toggle points/wireframe and apply maximum-edge and display-scale controls.

• Internal IFC controller

  Use object tree/search, picking, selected-object fit, isolation/show-all, top/front orthographic views, isometric perspective, X/Y/Z section cuts, wireframe and reset.

• Source/geometry distinction

  IFC-derived GLB is served as a checked derivative; this does not establish arbitrary public GLB/glTF upload support or automatic mapping of every mesh to an IFC element.

• Coordinate/reference controller

  Select actual points or separate block anchors, inspect original XYZ, export/print chosen rows and label a selected actual point as an unverified reference marker.

• Version and integrity controller

  Bind viewing, annotations, evidence links and geometry to source/version fingerprints; reject stale or mismatched outputs.

• Review and publication controller

  Apply current source cleanliness, status, license and actor permissions; IFC publication and provisional CAD review remain distinct workflows.

• Conversion controller

  Dispatch bounded native extraction, use private identity-bound caches, report supported/omitted geometry and recheck access after processing.

• Print/export controller

  Prepare supported drawing, elevation, surface, coordinate and document-page outputs with applicable source identity, units and display settings.

• Format boundaries

  DWG and IFC/IFCZIP have production review paths. PDF/images use document/markup paths. The richer direct DXF/3DFACE successor has accepted isolated staging integration; native RVT/DGN/SKP and arbitrary format conversion still require separate work.

• Editing boundaries

  TRACE review annotations do not rewrite the DWG/IFC design. IFC dimensioning, capped section solids, survey-certified benchmarks and approved final grading are not supplied merely by viewing.

Scope and availability: This is TRACE's internal review viewer/controller, not a full AutoCAD/Civil 3D/Revit authoring replacement. Section cuts are uncapped; camera ground/shadows are display aids, and geometry completeness remains source-dependent.

Implemented release with 155 passing tests: 112 PHP tests (384 assertions), 37 voice tests and six browser fixture tests; TypeScript typecheck also passed.

• Telephone interruption fix

  The response queue now waits while the caller speaks, coalesces overlapping turns and supports caller interruption. The user reported the real-call test passed as natural and responsive.

• Source-specific research

  Explicit official-source requests bypass the original workflow-guide shortcut; literal exclusions of project records are respected while private identifier protections remain in place.

• Live official-citation acceptance

  The tested RFI question returned official public-web citations to USACE CQM guidance and Caltrans Source Inspection Guidelines, with no project records used.

• Immediate support and troubleshooting

  Get help now provides four current workflow guides, typed product guidance, clear source labels, retained inputs/errors and a human-ticket handoff path.

• Current product guidance

  Web and telephone guidance covers My Apps/App Factory, Undo/Redo, loading, support, training and billing boundaries.

• Private improvement cycle

  Completed a private cycle containing seven failure signals, two scoped curricula and two new versions. No model weights, live answer behavior or promotion changed; no autonomous training.

• Billing readiness checks

  A read-only, secret-free check identifies missing merchant credentials, webhook configuration and plan setup. Live paid launch remains blocked pending configuration and financial acceptance.

• Support interaction isolation

  Support guidance no longer triggers a legacy acceptance toast; topic selection does not approve or seal a project record.

Scope and availability: The real-call result is one user-reported acceptance, not two independently identified calls or a statistical audio benchmark. Live research is a tested example, not universal accuracy. Human handoff is a ticket path, not a continuous staffing promise. No live charge, refund or subscription was attempted.

Retained 24-guide pack; these are original workflow explanations, not adopted contract requirements.

• Getting started with TRACE

  Original TRACE guidance available to eligible workflow retrieval.

• Asking TRACE a useful question

  Original TRACE guidance available to eligible workflow retrieval.

• Writing and tracking a request for information (RFI)

  Original TRACE guidance available to eligible workflow retrieval.

• Preparing a submittal for review

  Original TRACE guidance available to eligible workflow retrieval.

• Finding the right drawing and revision

  Original TRACE guidance available to eligible workflow retrieval.

• Organizing project files and document records

  Original TRACE guidance available to eligible workflow retrieval.

• Writing a useful daily report

  Original TRACE guidance available to eligible workflow retrieval.

• Taking and labeling useful site photos

  Original TRACE guidance available to eligible workflow retrieval.

• Preparing and recording an inspection

  Original TRACE guidance available to eligible workflow retrieval.

• Recording and escalating a safety concern

  Original TRACE guidance available to eligible workflow retrieval.

• Reviewing time entries and field days

  Original TRACE guidance available to eligible workflow retrieval.

• Turning meetings into clear action items

  Original TRACE guidance available to eligible workflow retrieval.

• Building a practical lookahead plan

  Original TRACE guidance available to eligible workflow retrieval.

• Tracking materials and long-lead items

  Original TRACE guidance available to eligible workflow retrieval.

• Keeping change requests and approvals distinct

  Original TRACE guidance available to eligible workflow retrieval.

• Reading a project budget carefully

  Original TRACE guidance available to eligible workflow retrieval.

• Preparing a payment application record

  Original TRACE guidance available to eligible workflow retrieval.

• Organizing permit and authority correspondence

  Original TRACE guidance available to eligible workflow retrieval.

• Planning closeout and turnover information

  Original TRACE guidance available to eligible workflow retrieval.

• Managing punch lists and remaining work

  Original TRACE guidance available to eligible workflow retrieval.

• Using a transmittal to explain what was sent

  Original TRACE guidance available to eligible workflow retrieval.

• Coordinating models and markups

  Original TRACE guidance available to eligible workflow retrieval.

• Using forecasts alongside field observations

  Original TRACE guidance available to eligible workflow retrieval.

• Understanding citations, uncertainty, and corrections

  Original TRACE guidance available to eligible workflow retrieval.

Scope and availability:

Eight retained publications totaling 524 PDF pages. Editions below describe the retained pack, not a claim of current editions.

• UFC 3-501-01 Electrical Engineering

  27 November 2024; 96 PDF pages; https://legacy.wbdg.org/FFC/DOD/UFC/ufc_3_501_01_2024.pdf

• UFC 3-410-01 Heating, Ventilating, and Air Conditioning Systems

  28 July 2025; Change 1, 23 January 2026; 63 PDF pages; https://legacy.wbdg.org/FFC/DOD/UFC/ufc_3_410_01_2025_c1.pdf

• UFC 3-201-01 Civil Engineering

  20 December 2022; Change 1, 1 June 2026; 68 PDF pages; https://legacy.wbdg.org/FFC/DOD/UFC/ufc_3_201_01_2022_c1.pdf

• UFC 3-420-01 Plumbing Systems

  1 April 2021; 72 PDF pages; https://legacy.wbdg.org/FFC/DOD/UFC/ufc_3_420_01_2021.pdf

• UFS 3-740-05 Construction Cost Estimating

  2 February 2026; 112 PDF pages; https://legacy.wbdg.org/FFC/DOD/UFC/ufs_3_740_05_2026.pdf

• UFGS 01 32 01.00 10 Project Schedule

  August 2026; 24 PDF pages; https://legacy.wbdg.org/FFC/DOD/UFGS/UFGS%2001%2032%2001.00%2010.pdf

• UFGS 01 45 00 Quality Control

  August 2023, Change 4 August 2026; 51 PDF pages; https://legacy.wbdg.org/FFC/DOD/UFGS/UFGS%2001%2045%2000.pdf

• UFGS 01 35 26 Governmental Safety Requirements

  May 2024, Change 2 August 2026; 38 PDF pages; https://legacy.wbdg.org/FFC/DOD/UFGS/UFGS%2001%2035%2026.pdf

Scope and availability:

Released advisory assessment controls added after the previous catalog.

• Answer-unit review

  Split complete answer paragraphs and printable findings into server-created, hashed review units.

• Complete finding review

  Include finding titles and applicability text in review rather than examining only selected snippets.

• Independent structured review

  Return one review result per unit with source references, claim kind, assertion polarity and prerequisite states.

• Review coverage validation

  Reject omitted, duplicate or unknown units and evidence references outside the supplied source set.

• Three-state prerequisites

  Represent each condition as supported, contradicted or unknown; unknown does not become satisfied.

• Conjunctive condition checking

  Require all stated prerequisites to be supported before releasing a positive assertion that they are met.

• Qualified uncertainty

  Allow an honest statement that acceptance or applicability is unproven without treating it as a positive claim.

• Material qualification retention

  Require each material summary or finding to retain its relevant conditions; another paragraph cannot silently repair an omission.

• Whole-answer completeness

  Block truncated answers and materially unanswered requests through explicit completeness review.

• Authority-promotion prevention

  Avoid converting a reported execution or relevant document into verified incorporation, approval or controlling authority.

• Missing-adoption distinction

  Do not infer that terms are legally nonbinding merely because their adoption evidence is absent.

• Source-conditioned notice language

  A narrow guard checks identified suspension statements for supported notice and undisputed-invoice qualifications.

• Complete reviewer evidence

  Supply passage text, source hashes, passage hashes and page locators to the reviewer.

• Review audit records

  Retain unit hashes, prerequisite outcomes, evidence references, expected counts and reviewer details.

• Adversarial regression capture

  Turn observed truncation, omitted conditions, false authority promotion and incorrect refusal into regression cases.

• Independent reference-answer consultation

  Claude, Gemini and Grok reviewed anonymized supplied sources and corrected reference wording; their acceptance applies to that wording, not certification of TRACE software.

• Advisory assessment acceptance

  The recorded final suite passed 19 adversarial reviewer cases and a complete live assessment; software checks covered 91 tests and 305 assertions.

• Human verification step

  Name the missing or governing records and the authorized person's next verification action before consequential decisions.

Scope and availability: Semantic interpretation remains model judgment. This is evidence-backed advisory assistance, not guaranteed legal correctness or an autonomous construction manager.

Organize files, drawings and daily records around their project context.

• Project document workspace

  Upload, organize and retrieve authorized project files with source identity and extraction status.

• Plan sets and sheets

  Register plan sets and sheet records, including supported proposals from uploaded documents.

• Human-attested registration

  Review proposed sheets and bulk-register supported records with attribution.

• Immutable plan revisions

  Retain prior sheet versions and formal review context.

• Internal document markup

  Select a supported PDF/image page, annotate it and use the authorized sharing workflow while preserving original bytes.

• Plan revision comparison

  Compare extracted statements and metadata between authorized revisions of the same sheet.

• Photo and media records

  Store project images and attachments with content provenance.

• Daily reports

  Capture field work, labor/equipment context and supporting media in the daily record.

• Signed daily records

  Use supported signature/seal workflows and append corrections rather than overwriting finalized content.

• Weather intelligence

  Use project-coordinate forecasts, the current weather bar, ten-day outlook and source-linked weather notices.

• Daily Project Success Brief

  Produce a deterministic cited position statement from supported sealed records and contract clocks, including freshness and explicit unknowns.

Scope and availability: Text comparison does not compare all pixels or geometry. Forecasts are external observations, not proof that work was weather-delayed.

Additional document, knowledge and field-record tools included in the platform inventory.

• TRACE Atlas source administration

  Upload eligible reference sources, track ingestion and manage source versions under the applicable authority.

• Source review queues

  Review extraction/readiness and verification status before eligible material is used as grounded evidence.

• Source relationships

  Maintain supported relationships between references and preserve provenance context.

• Access classifications

  Apply supported document/source classifications in addition to tenant and project permissions.

• Quarantine handling

  Keep unsafe or unready uploads out of the usable evidence path and expose supported status information.

• Resumable media uploads

  Use supported large-file upload handling for project media.

• Media organization

  Maintain descriptions, location metadata, collections, evidence links and previews.

• Media archive and restore

  Archive and restore eligible media under current authority.

• Field-day archive

  Retain supported daily field records and printable daily outputs.

• TRACE Sign

  Prepare, send or void supported signature envelopes; delivery and provider availability are configuration dependent.

Scope and availability: Source verification status does not establish universal technical correctness. Access to the source administration tools is role dependent.

Deployed document-page editing improvements.

• Undo and redo

  Restore up to 100 supported annotation changes, including grouped clear operations.

• History branching

  Invalidate redo after a new edit; retain native text-input undo behavior.

• Page and source isolation

  Reset markup history on project/source-version/page changes, cancellation and successful send.

Scope and availability:

Delivered RFI, document and tracker refinements from reviewed release records.

• Record-specific Ask TRACE

  Bind the exact authorized RFI identity, subject, question and references to the conversation and retain that context only while the matching project/RFI stays active.

• Historical response separation

  Display superseded responses as history while directing current action to the active correction.

• Named seal attribution

  Resolve recorded actors to names and timestamps instead of showing only internal identifiers.

• Correct document parties

  Use the recorded issuing/originating and receiving organizations in the corresponding preview.

• Separate RFI and submittal printing

  Use record-specific Preview / print RFI and Preview / print submittal controls and headings.

• Shared issued-document register

  Retain explicit issued status and distinguish issued documents from generated previews.

• Authorized original attachment viewing

  Retrieve the submitted original under current account/project permission, with page navigation and download where supported.

• Unsigned original preservation

  Preserve the unchanged unsigned original while the supported review workflow creates separate signed copies for individual reviewers.

• Final required-approver seal

  Keep intermediate signed review copies separate from the final seal after the last required approval.

• Member template previews

  Permit eligible project members to preview templates while requiring template-management authority for edits.

• Revision-preserving template edits

  Create a new template revision without invalidating earlier assignments or signatures.

• Resumable submittal attachments

  Use bounded upload chunks and finalized attachment identity to avoid duplicate or partial attachments; the recorded implementation uses 8 MB chunks.

• Governing-document conflict controls

  Record unrecorded, confirmed or conflicting precedence with citations, ordered categories and conflict notes; do not silently choose between conflicting provisions.

• Printable download fallback

  Provide a self-contained printable document when an embedded host blocks the standard print window.

• Tracker validation guidance

  Give actionable feedback for empty generation prompts, tracker names, missing fields, empty labels and empty choice lists.

• Responsive tracker keyboard access

  The deployed studio includes tested responsive layouts, keyboard access and reduced initial clutter on small screens.

• Demo weather role coverage

  The live demo location/weather correction provides current conditions and a 10-day forecast to the four configured demo roles.

Scope and availability: Viewing, previewing and printing do not issue, seal or approve records.

Inspect real IFC-derived geometry and its relationship to the uploaded source.

• IFC and IFCZIP admission

  Upload supported models to an authorized project container with an immutable version and source fingerprint.

• Queued extraction

  Extract supported IFC identity, hierarchy, objects and properties through the conversion worker.

• Searchable model manifest

  Find extracted elements and inspect properties with authorized project/version context.

• Human publication gate

  Review, publish or reject model versions; viewing rights depend on authority and publication state.

• Derived GLB geometry

  Convert supported IFC geometry to a self-contained browser-viewable model.

• Opening integrity

  Exclude Boolean cutter solids from displayed meshes while retaining actual host opening subtraction.

• Conversion coverage

  Show represented, converted, excluded-feature and missing-geometry counts, with an explicit completeness result.

• Coordinate metadata

  Report available units and axis basis; display centering does not rewrite source coordinates.

• Source-to-geometry verification

  Check original source bytes, derived geometry bytes, lengths and fingerprints against the version binding.

• Serving-time authorization

  Recheck actor, project, version and status before serving verified geometry.

• BCF coordination exchange

  Import supported BCF 2.1 issues into the staging register and export authorized issues.

Scope and availability: Native Revit ingestion, cross-model federation and automatic BIM-to-asset linkage are not established. Bounded single-IFC coordination candidates were subsequently deployed and are listed below.

A construction-related example is automatically available from every project BIM panel.

• Smooth orbit, pan and zoom

  Inspect the model using interactive camera controls and short animated view transitions.

• Element tree and search

  Find and select individual rendered objects; display authorized names when available.

• Selection and fit

  Highlight an object and frame the selected geometry.

• Isolation and show-all

  Focus on selected geometry, then restore the complete model.

• Section cuts

  Move a cut along X, Y or Z to look inside the model.

• Orthographic views

  Switch to top or front inspection views, or return to an isometric perspective.

• Wireframe and reset

  Inspect mesh structure and restore the default view.

• Rendering quality

  Use antialiasing, controlled pixel density, balanced lighting and ground shadows for a clear model display.

• Resource cleanup

  Abort obsolete loads and dispose viewer resources when the active scope changes.

• Source details panel

  Inspect conversion metadata and fingerprints; unavailable details remain explicitly unavailable.

• Related synthetic example

  Explore a three-storey public-works building with structure, glazing, doors, utility pipes and six opening voids; it creates no project records.

Scope and availability: Section cuts are uncapped visual slices. The synthetic example is IFC-derived, not a reconstruction from photographs or a survey-certified model.

Deployed customer-panel capabilities added after the earlier public inventory.

• Automatic CAD availability

  Clean authorized uploaded DWGs appear in the current project BIM CAD workspace.

• Direct Open CAD

  Open the selected drawing revision from Documents; keep original download and version history available.

• Review-pending viewing

  Provisional review status no longer alone blocks the CAD viewer; viewing does not approve the source, bypass quarantine or widen access.

• Native bounded conversion

  Convert supported DWG geometry through an isolated native worker; preserve original source bytes and report unsupported entities and missing references.

• 2D drawing controls

  Pan, zoom, fit, show/hide layers, restore converted visibility and find/select supported entities.

• CAD annotations

  Create notes, polylines and approximate XY distance annotations bound to the exact version and source fingerprint.

• Append-only markup history

  Retain saved drawing annotation history without overwriting the original drawing.

• XYZ elevation view

  Inspect actual source line/point coordinates in 3D with orbit, pan and fit controls.

• Elevation display filters

  Choose a Z range, optional zero-Z exclusion and explicitly labeled 1x, 2x, 5x or 10x vertical display scale.

• Solid terrain preview

  Build a shaded height-colored triangulated surface from one selected native POINT layer.

• Low/high color legend

  Show source-elevation ranges with blue lows and gold highs; optional wireframe and source-point overlays.

• Surface quality controls

  Report zero-Z exclusions, merged duplicates, conflicting-coordinate exclusions and triangle counts; refuse unusable or collinear input.

• Gap filtering

  Optionally exclude triangles exceeding a selected edge length. Separate point layers are never automatically pooled.

• Survey point distinction

  Keep actual native POINT coordinates separate from block-insertion anchors; neither is automatically official survey control.

• Point selection and filtering

  Filter coordinate candidates by layer/block, select rows and retain exact XYZ rather than substituting attribute labels.

• Selected-point CSV

  Export selected coordinate rows with units, source/version and unverified status; escape spreadsheet-formula strings.

• Reference marker

  Mark a selected actual POINT with a visible reference label and XYZ; label remains unverified and does not establish an official benchmark.

• Drawing and surface printing

  Print current 2D, XYZ or solid-surface views and selected coordinate tables with source identity and applied display settings.

• Context cleanup

  Abort obsolete loads and dispose graphics resources on tenant/project/source changes; recheck access and source integrity.

Scope and availability: Solid terrain is interpolated point coverage, not certified final grade. The reviewed grading file has separate point patches and missing references; approved proposed-surface identity, boundaries, breaklines, CRS and datum remain unverified.

Deployed after the original 3D release.

• Element evidence links

  Associate an exact IFC element/revision with an authorized RFI, submittal or schedule activity and record the reason.

• Revocable association history

  Preserve link revocation history and recheck access to both model and target record.

• Revision metadata comparison

  Show added, removed and changed extracted identities/properties between two versions of the same model.

• Potentially affected links

  Show explicit associations potentially affected by metadata changes while leaving each link bound to its original revision.

• Intersection candidates

  Run bounded native geometric intersection checks between selected classes within one exact IFC revision.

• Clearance candidates

  Measure supported separation against the selected tolerance and return candidate pairs for human review.

• Opening-aware geometry

  Respect host opening subtraction and exclude Boolean cutter objects from the displayed products.

• Coverage-qualified results

  Report missing geometry and check coverage; incomplete zero-hit results cannot establish a no-conflict conclusion.

Scope and availability: No cross-model federation, RVT authoring, geometric revision comparison, 4D simulation or automatic issue/approval creation is claimed.

A separate newer DXF path now has coherent isolated staging and browser acceptance.

• Direct POINT extraction

  Retain explicit source points with exact source identity and original decimal provenance.

• Direct LINE extraction

  Retain source line endpoints rather than inferring design lines from rendered pixels.

• Direct 3DFACE extraction

  Preserve explicit face vertex order and hidden-edge information where supported.

• Unit provenance

  Carry declared units without silently assigning survey datum or coordinate reference authority.

• Unknown-reference retention

  Expose missing or unsupported references instead of silently fabricating geometry.

• Resource-limited parser

  Constrain parsing by entity/vertex/output size, memory, CPU and wall-time limits.

• Network-disabled parser isolation

  Run the bounded parser with restricted filesystem/network permissions in the tested worker path.

• Authenticated local socket bridge

  Restrict the application-to-parser interface to its authorized local caller.

• Lifetime ownership lock

  Bind listener ownership and recovery to its recorded process/socket identity.

• Recorded listener recovery

  The accepted disposable integration tested listener termination, recovery and subsequent parsing.

• Incomplete-ownership refusal

  Do not recover an unproven socket/listener identity or crash before durable ownership metadata.

• Application Documents integration

  The later isolated staging release passed real Documents upload and CAD review.

• Primitive viewer and printing

  Staging browser acceptance covered one POINT, LINE and 3DFACE, source limits and TRACE-branded print output.

• Parser release backup linkage

  Bind the accepted staging CAD revision to its encrypted backup/transfer receipts.

Scope and availability: This successor does not replace the released DWG path in production. It does not establish arbitrary Civil 3D semantics, external-reference expansion, certified survey control or final-grade interpretation.

Newer verified additions received from the demonstration development owner after the main catalog refresh.

• Native synthetic DWG admission

  A native DWG is admitted in the separate synthetic project, with 651 terrain POINT coordinates matching the authored CSV, one explicitly unverified reference point and 656 rendered entities.

• DWG layer visibility correction

  An installed narrow LibreDWG exporter patch preserves layer visibility instead of negating all layer colors and hiding otherwise visible drawing layers.

• Visible and hidden layer regression

  Both visible-layer and deliberately hidden-layer fixtures passed, together with the real production sandboxed preview under the web-service user.

• Native BIM control acceptance

  Scoped local viewer acceptance verified 49 mesh loads, IFC tree selection, isolation, fit, top projection, wireframe, section cut, search and source checksum.

• Linked preaward demonstration estimate

  The synthetic project includes a draft preaward profile and a ten-item estimate, with all ten items linked to plan versions.

• Unsigned TRACE Sign demonstration

  A synthetic draft envelope contains two fictional recipients, unsigned fields and a two-page PDF; it is not an executed customer agreement.

• Expanded file integrity acceptance

  Ninety media/document-version file readability, hash and size checks passed for the synthetic demonstration content.

Scope and availability: The converter patch is installed. Synthetic geometry and records do not establish survey authority or real contract approval. Public visitor signup/access remains separate.

Current update (September 9, 2026): public visitor registration and verified read-only access are now live as a separate delivery layer. Synthetic geometry and records still do not establish survey authority or real contract approval.

Manage the formal exchange of questions, responses and review packages.

• RFI register

  Track questions, subject, responsible parties, references and current review status.

• RFI supporting context

  Associate specification sections, plan references, related submittals and governed attachments.

• RFI response workflow

  Record the authorized response, route it through configured review and retain sealed history.

• Submittal register

  Organize packages by specification section, assigned parties and review clocks.

• Submittal review

  Capture dispositions, review stamps, certifications and accountable finalization.

• Unsigned and sealed artifacts

  Preserve supported original/unsigned material alongside the accountable review record.

• Branded record documents

  Produce supported RFI, submittal, change-order and payment-application covers from the record and account branding.

• Issued transmittal register

  Maintain append-only issued-document history and source associations.

• Meeting management

  Prepare agendas, record minutes and action items, and finalize supported meeting records.

• Communication preparation

  Preview or print supported records and prepare communication through the configured workflow.

Scope and availability: Draft generation and document export are separate from sending, issuing or approving a record.

Connect structured observations to a protected project record.

• Project asset registry

  Register an asset with an immutable sensor channel, metric and unit.

• Manual observation entry

  Enter attributable readings with measurement time and declared units.

• Authenticated observation API

  Accept authorized client readings with project and tenant checks.

• Data-quality validation

  Validate decimal precision, time bounds, metric and unit identity; reject conflicting or mismatched observations.

• Duplicate protection

  Use UUID idempotency and sensor/timestamp deduplication to prevent replayed readings from multiplying records.

• Channel credentials

  Issue, rotate and revoke scoped sensor credentials with bounded expiry and one-time raw-token display.

• Credential revalidation

  Check issuer rights, license and project lifecycle at intake; credentials cannot silently switch channels.

• MQTT 5 / TLS bridge

  Delivered gateway software supports durable buffering, fixed-identity retries, QoS 1 acknowledgment and verified TLS.

• Energy TRACE

  Keep attributable manual energy, fuel and power-demand readings with units, time and source references.

• City of Los Angeles permit lookup

  Look up an exact issued-permit number in the supported official dataset and display source/status/check dates separately.

• No automatic permit mutation

  A lookup does not itself update a project's issued status or establish legal applicability.

Scope and availability: Gateway deployment and actual hardware onboarding are required. No production hardware calibration, anomaly control, general municipal feed, live CSLB/DIR connection or full operational digital twin is claimed.

Record findings and route accountable follow-up through the project.

• Inspections

  Capture supported inspection records and evidence.

• Observations and deficiencies

  Describe issues, assign responsibility and track follow-up.

• Punch items

  Maintain completion items and evidence-backed closure under the applicable authority.

• Job walks

  Record field walks, observations, due dates, responsible parties and accountable finalization.

• Formal closure rules

  Require the supported human determination; a party claim or AI recommendation cannot close an item on its own.

• Safety observations

  Capture unsafe-condition reports and corrective actions.

• Incidents and near misses

  Maintain incident/near-miss records and human recordability determinations.

• Toolbox talks and training

  Record supported safety talks, training and participation evidence.

• Permit screening

  Use country/jurisdiction-aware candidate screening with editable federal, state/province and local entries.

• Applicability determinations

  Record a project-specific basis for permit applicability.

• Issuance evidence

  Require supported clean evidence for issued status and preserve determination history.

Scope and availability: These workflows support accountable administration; they do not independently certify site safety, statutory compliance or permit applicability.

Browser evidence capture has a separate identity and review chain from native draft synchronization.

• Browser device-key enrollment

  Enroll a project-scoped capture key through authenticated controls before offline use.

• Pinned server receipt key

  Verify returned receipts against the previously pinned signing identity.

• Original-byte manifest

  Bind original files and observation metadata to a signed capture manifest.

• Offline queue persistence

  Keep signed originals on the enrolled browser while disconnected, including tested browser restart scenarios.

• Capture sequence tracking

  Maintain device-chain counters and avoid treating an older capture as new.

• Reconnect receipt verification

  Clear eligible pending items only after validating the server receipt.

• Dropped-response recovery

  Retry an uncertain capture with the same identity after a committed response is lost; avoid duplicate evidence.

• Encrypted queue export

  Export a protected recovery backup using a user-held passphrase.

• Revoked-device refusal

  Recheck device authority when reconnecting and retain refused originals for controlled recovery.

• Recovery operator attribution

  Distinguish the original signer from the person recovering the backup.

• Recovered-evidence quarantine

  Keep recovered originals unreviewed until the authorized inspection and review path completes.

• Scanner prerequisite

  Require the configured scan/inspection result before recovered evidence can be accepted.

• Independent reviewer separation

  Prevent original submitters and recovery operators from self-accepting the recovered evidence.

• Original inspection and download

  Allow an authorized reviewer to inspect exact recovered bytes before recording a review.

• Revocation preservation

  Recovery does not silently reactivate the revoked device.

• Offline shell delivery

  Serve the cacheable capture shell and JavaScript modules with the required routing and MIME behavior.

Scope and availability: Physical iOS/Android acceptance and comprehensive offline drawings, RFIs, schedules and approvals are separate. A disconnected device learns revocation only after contact; local expiry remains important.

Combine deterministic schedule analysis with bounded alternatives for authorized review.

• Supported schedule imports

  Read CSV, XLSX, MS Project XML and Primavera P6 XER exports through supported parsers.

• Immutable schedule versions

  Retain source identity, import assumptions and authorized version comparisons.

• CPM and logic analysis

  Inspect supported critical-path calculations, relationships, gaps and version deltas.

• Rolling look-ahead

  Prepare three-week look-ahead drafts with constraints, accountable transitions and export.

• Living Project rehearsal

  Compare up to four user-supplied network alternatives for duration, release and dependency changes.

• Recovery scenario generation

  Generate four fixed-priority heuristic proposals for eligible complete, unstarted networks of 1-200 activities and up to 1,000 supported relationships.

• Work-calendar handling

  Evaluate supported work periods, closures and dependencies in the recovery planner.

• Resource feasibility

  Respect declared labor/equipment capacities and material-release constraints in supported recovery cases.

• Declared cost comparison

  Show direct work costs based on the supplied rates and inputs, rather than inferred project margin.

• Unsupported-input refusal

  Inspect original source semantics; refuse unsupported logic, ambiguous defaults, actual-progress recovery and unrepresentable constraints.

• Reviewable output

  Show assumptions, finish effects and relevant calculation evidence without modifying the imported schedule.

Scope and availability: Legacy rehearsal uses abstract elapsed minutes; recovery is a separate constrained planner. Neither guarantees a global optimum, constructability, Monte Carlo probabilities or automatic write-back to P6/MS Project.

Exportable review material and controlled improvement.

• Registered archive coverage

  Include an explicit registry of supported project record families and flag coverage gaps.

• Newer schema preservation

  Retain newer change-order fields and associated asset, sensor, visual-review, BIM-link and CAD-markup records.

• Polymorphic target checks

  Verify that supported polymorphic evidence targets are represented rather than silently omitted.

• Credential exclusion

  Exclude stored credential hashes and secrets from portable evidence packages.

• Original file reconciliation

  Check selected file identities, bytes and hashes against the archive manifest.

• Signed coverage manifest

  Release a complete marker only after record registry, file and coverage checks pass.

• Independent archive verification

  Provide verifier resources for checking signatures and package consistency separately from the interactive portal.

• External reference distinction

  Identify an external URL as a reference rather than implying its remote content is included in the archive.

• Relationship-lag calendars

  Use the appropriate relationship and working-time basis in supported schedule rehearsal.

• Progress methodology declaration

  Retain the selected progress/remaining-duration assumptions in the scenario packet.

• Reviewable scenario signature

  Bind the signed rehearsal to its exact source, assumptions and result.

• Full schedule packet printing

  Preserve complete row content across multiple printed pages in the tested packet path.

• Reviewed outcome examples

  Build procedure candidates from expressly reviewed outcomes and their required evidence types.

• Procedure evaluation

  Evaluate a proposed procedure against held-out examples and current source requirements.

• Explicit procedure promotion

  Require authorized activation of a candidate rather than automatically changing live behavior.

• Procedure retirement

  Retain history while stopping future use of a retired version.

• Record-specific checklists

  Prepare unsent review steps for a selected authorized source record.

Scope and availability: A portable evidence archive is not a complete infrastructure backup. Procedure learning does not train foundation-model weights.

Connect billing, cost and change records to their supporting evidence and authority.

• Schedule of values

  Structure progress billing and maintain supported line allocations.

• Payment applications

  Prepare progress applications with supporting records and review/payment clocks.

• Certification controls

  Use supported content-bound, two-person certification and structural validation.

• Compliance withholdings

  Track supported withholding amounts separately from the operation of the payment clock.

• Change orders

  Keep approval and contract incorporation as distinct actions.

• Contract growth

  Associate approved changes with SOV allocation while preserving the original contract value.

• Cost codes and budgets

  Maintain budget, commitments, actual cost, forecast and variance records with attributable revisions.

• Timesheets

  Record crew and equipment hours by cost code with supported approval.

• Trade partners and subcontracts

  Maintain project partners and subcontract records.

• Credential windows

  Evaluate entered license, registration, bond and insurance effective/expiry dates against the recorded work date.

• Releases and waivers

  Manage configured release records and claimant exposure.

• Stop payment notices

  Track notice-related withholding separately from release exposure.

Scope and availability: Legal and financial determinations require the controlling project terms and authorized review. Recorded credential windows are not a live licensing-board verification.

The tested package was deployed September 8, 2026 Pacific time. Existing workflow behavior and grants were preserved.

• Transactional evidence decisions

  Connect supported formal record actions to explicit evidence acceptance, current source and authority checks, transaction locking and retry identity.

• Contract provenance journal

  Maintain append-only, project-bound events, source relationships, configured evidence policy, cryptographic signatures and independent review.

• Signed offline capture

  Enroll/revoke capture devices; sign local originals, pin receipt keys, retain offline queues, encrypt recovery backups, synchronize and quarantine recovered evidence for independent review.

• Extended schedule semantics

  Use working-day and relationship-lag calendars, progress methodology, remaining durations and source-linked scenario packets.

• Reviewed procedure lifecycle

  Record reviewed outcomes, evaluate candidate procedures, explicitly activate/retire versions and prepare unsent record-specific checklists.

• Portable project evidence archive

  Export registered project records and eligible original files with credential exclusions, byte checks, signed coverage manifest and an independent verifier.

Scope and availability: Workspace is enabled. Mandatory new evidence gating on existing workflows is off; explicit evidence acceptances remain enforced. This release does not supply automatically approved jurisdiction rules or activate merchant billing.

Detailed components of the released contract workspace.

• Evidence source adapters

  Import authorized facts from RFIs, submittals, changes, payments, schedules, quantities, quality, meetings, labor, safety, procurement and reviewed passages.

• Accountable organization selection

  Bind imported evidence to a configured project organization rather than accepting an invented party.

• Evidence relationship graph

  Record supports, requires, contradicts, measures, implements, responds-to and derived-from relationships.

• Audited source correction

  Retain the previous revision and correction reason rather than overwriting evidence history.

• Evidence withdrawal controls

  Record withdrawal or control events while preserving historical references.

• Live source freshness

  Recheck current source identity before proposals, relationships and accepted decisions.

• Current actor refresh

  Refresh user and grant state without discarding the device-bound token context.

• Decision intent binding

  Bind a proposed acceptance to its target, command content and source state.

• Concurrent decision protection

  Serialize relevant decisions and source corrections with scoped locks and transaction checks.

• Same-request receipt replay

  Return the prior result for an identical accepted request and reject reuse with changed content.

• Stale browser action protection

  Detect changed account, project, form content or decision options during asynchronous lookups.

• Existing approval continuity

  Keep ordinary approval behavior intact while mandatory evidence enforcement is disabled.

• Explicit acceptance enforcement

  Validate an expressly supplied contract acceptance even in continuity mode.

• Five extended terminal paths

  Support evidence acceptance at bid award, takeoff acceptance, accounting exchange approval, lien confirmation and stop-notice resolution.

• Signed journal chain

  Bind ordered project events to previous hashes and a server signing identity.

• Project calendar policy

  Configure timezone, working weekdays, exceptions and dated nonworking days.

• Jurisdiction pack preview

  Preview versioned rule changes against source-linked project evidence before publication.

• Jurisdiction version pinning

  Retain the exact reviewed pack, effective dates and publication history; do not silently inherit a changed rule set.

• Evidence-aware permission display

  Show available controls from current capabilities while keeping restricted source facts out of the projection.

• Immutable migration behavior

  Add journal/review structures while preserving existing records; destructive history rollback is refused.

Scope and availability: The deployed workspace does not automatically approve a source, issue a notice, send payment, adopt a legal rule or grant new access.

Support configured public-works and project-specific labor evidence workflows.

• Compliance profile

  Configure the applicable project requirements and supported California public-works / PLA / CWA settings.

• Requirement register

  Track required submissions and project-specific evidence.

• Sealed submissions

  Receive attributable subcontractor compliance submissions.

• DIR receipt evidence

  Record supported registration/receipt information for review.

• Prevailing-wage review

  Compare reported classifications against supplied, cited rate determinations; flag unknown or missing classifications.

• Apprenticeship notices

  Track DAS 140/142-related evidence and supported requests.

• Apprenticeship ratios

  Review configured ratio information against submitted records.

• Training funds

  Track supporting contribution evidence.

• Assent and dispatch

  Maintain agreement/dispatch-related records where required by the configured profile.

• Local and targeted hiring

  Track supported project workforce and hiring commitments.

• Exception findings

  Use deterministic checks to identify gaps and document human resolution.

Scope and availability: No universal live wage-rate feed, autonomous trade classification or blanket legal-compliance guarantee is included. Time cards and certified-payroll review remain distinct processes.

Prepare procurement and contractor estimates while preserving controlled access.

• Preconstruction readiness

  Maintain supported readiness records and qualification information.

• Procurement profiles

  Configure public or private operating workflows for the project.

• Solicitations

  Prepare and manage supported solicitation records.

• Addenda

  Track procurement amendments and associated documents.

• Bidder access

  Use supported bidder invitation and controlled bid-room workflows.

• Controlled bid receipt

  Receive and retain bid submissions through the configured process.

• Human award

  Keep award decisions with authorized people.

• Source-bound takeoff

  Associate supported quantity work with the source evidence used.

• Deterministic estimating

  Build supported estimates with cost-code and cost-basis information.

• Quotes and leveling

  Maintain supported internal quote and comparison information under contractor access controls.

• Estimate handoff

  Move an authorized estimate through the supported controlled handoff process.

• Contractor-private commercial data

  Do not expose internal estimates, quotes, budgets or leveling merely because an owner also uses TRACE.

Scope and availability: Procurement profiles are configurable workflows, not determinations that a bid, classification, protest or award is legally compliant.

Create supported custom trackers and manage attributable stock movements.

• Natural-language app definition

  Describe a supported form or tracker and generate a reviewable constrained definition.

• Typed fields

  Configure supported field types, validation and references.

• Workflow states

  Define supported simple states and transitions.

• Dashboard charts

  Add supported charts over application records.

• Draft and revision review

  Inspect and edit the generated definition before publication.

• Publication controls

  Use app-specific builder and publisher authority to release a supported revision.

• My Apps runtime

  Open published applications and create or manage authorized records through the installed web runtime.

• App-specific access

  Separate viewer, editor, builder and publisher grants.

• Bounded recovery

  Restore an eligible prior valid published definition when required.

• Inventory ledger

  Record receipts, transfers, issues and reversals with fixed-precision quantities and attribution.

• Movement history and reconciliation

  Inspect stock movements and supported reconciliation records.

• App-to-inventory references

  Link supported custom records to inventory items without automatically posting a stock movement.

Scope and availability: App Factory generates constrained definitions, not arbitrary executable programs. It does not automatically purchase material, post ERP transactions or connect external systems.

Additional lifecycle functions behind the custom-application and stock-ledger workspaces.

• App templates and catalogue

  Start from supported catalogue definitions or reusable templates.

• Saved app drafts

  Retain editable drafts before publishing a valid application definition.

• Blueprint import and export

  Exchange supported application definitions through validated blueprint workflows.

• Definition migration preview

  Inspect supported schema/definition changes before applying an eligible migration.

• Migration application

  Apply supported changes through the controlled application lifecycle.

• Record operations

  Create, update and delete eligible custom-app records under app-specific permissions.

• Search and pagination

  Find records in supported custom trackers without loading the entire record set at once.

• Linked tracker references

  Relate supported records across authorized custom applications.

• Summaries and dashboards

  Use supported record summaries, charts and dashboard layouts.

• Manifests and health controls

  Inspect app definition/runtime state and use supported recovery-draft or repair operations.

• Inventory setup

  Maintain item/location registers and opening-stock preview/application.

• Stock balances

  Review balances and attributable movement history across authorized locations.

Scope and availability: These are validated application-data workflows. They do not establish arbitrary code execution, generalized ERP automation or fleet telemetry.

Deployed web tooling with provider generation subject to current pricing, usage and service readiness.

• Guided tracker creation

  Describe, review, save draft and publish through a four-step process.

• Searchable tracker library

  Find trackers using library search and draft/published filters.

• Stable field editing

  Add, remove and reorder typed fields without silently replacing stable field keys.

• Interactive practice mode

  Preview a generated design and submit practice entries without creating business records.

• Multiline records

  Preserve paragraphs and Unicode through preview, creation, editing and reload.

• Contextual entry deletion

  Confirm deletion of the named selected entry with Keep entry as the safe default; this is not whole-tracker deletion.

• Automatic training tracker

  Supported new-account paths receive one account-local SAMPLE inspection tracker with 15 fields, four transitions, a chart and a fictional record; existing accounts are not universally backfilled.

• Idempotent sample provisioning

  Avoid duplicate samples and preserve user edits, deletions and revoked grants; eligible later members receive sample-specific access.

• Known-definition recovery

  Recover eligible valid published definitions and repair derived indexes without inventing replacement business records.

• Generation availability disclosure

  Earlier production generation passed, but later pricing/reconciled-usage gates blocked a tested request. Generation is implemented and conditional, not guaranteed available to every account.

Scope and availability: Client access follows the applicable browser and device requirements. Whole-tracker deletion and unrestricted executable generation remain separate from these supported tracker controls.

Preserve the operating record and configure external exchange deliberately.

• Closeout checklist

  Assemble evidence-backed turnover requirements and track completion.

• Human closure acknowledgment

  Record accountable closure rather than inferring acceptance from an export.

• Agency package builder

  Create supported record snapshots with a sealed manifest and content fingerprints.

• Project archive

  Retain supported read-only archived records for authorized access.

• Customer API

  Use supported scoped API operations with current authorization and read/write restrictions.

• Integration configuration

  Maintain supported provider setup, mapping and connection-health information; unavailable adapters remain unavailable.

• Source and record export

  Export supported records, manifests, proof reports and exchange formats.

• Tenant/project separation

  Enforce server-side scope and effective permissions across governed endpoints.

• Attributable history

  Retain supported audit events, sealed content identity and linked corrections.

• Platform administration

  Manage supported account/module licensing, grants, AI usage and operational settings.

• Support and onboarding

  Use product help and supported support workflows; configure email, retention, backup and external connections for the deployment.

Scope and availability: Named integration catalog entries are not proof of active adapters. SSO/MFA/SCIM, enterprise certifications, failover and restore guarantees require separately verified delivery terms.

Separate billing technology from the construction capability inventory.

• Subscription onboarding controls

  Corrected provisioning checks distinguish subscription activation from verified completed payment and enforce plan mismatch guards.

• Atomic account provisioning

  Implemented receipt/account/encrypted-mail enqueue and retry controls are documented.

• Sandbox checkout development

  Sandbox OAuth, catalog and checkout creation are recorded; end-to-end buyer approval, webhook activation, delivery and live launch acceptance remain incomplete.

Scope and availability: Paid self-service launch is not accepted merely because sandbox objects or subscription routes exist. Quote-based public pricing and actual provider readiness remain relevant.

Browser access, released native-server contracts and continuing installed-client development are distinct delivery paths.

• Desktop access

  Windows and Mac can use supported browser workflows. A Windows application with a separate protected native draft workspace and isolated online portal window is undergoing installed acceptance.

• Mobile access

  iOS and Android have native-client development, shared interface and bridge work. Signed distribution and physical-device acceptance must be confirmed for the applicable release; supported browser access remains separate.

• Device permissions

  Microphone, camera, file selection, downloads and notifications follow the device/browser permission settings.

• Graphics and connectivity

  Interactive CAD/BIM requires compatible graphics support; provider-backed and connected workflows require the relevant network/service connection.

Scope and availability: Device project enumeration and signed draft synchronization APIs are released. This does not establish App Store/Play distribution, complete native parity or offline formal approvals.

Updated by the September 9 AI/operations release: interruption handling corrected and a user-reported real-call acceptance passed.

• Telephone conversation gateway

  Configured telephony gateway connects caller audio with a realtime AI conversation service.

• Public product knowledge

  Provide TRACE product/help knowledge through the configured voice service; this does not establish unrestricted project-document access over telephone.

• Turn and response controls

  Manage conversation-turn behavior and response-length settings to reduce interrupted or unfinished speech.

• Privacy-safe timing diagnostics

  Collect timing/completion telemetry for audio-gap diagnosis without recording audio or transcript text in that diagnostic.

• Versioned gateway deployment

  The current operations/help gateway passed 37 voice tests and TypeScript checks. Its audio/queue code matches the real-call-tested version.

Scope and availability: The earlier interruption issue is superseded by the documented fix and user-reported natural, responsive real-call result. Device, network and conversation conditions still affect call quality.

Development history remains visible. Later production receipts supersede earlier candidate-only descriptions.

• Universal approval evidence gates

  Released for the supported bid-award, takeoff, accounting-exchange, lien-release and stop-notice paths. Explicit submitted acceptances are validated; mandatory gating of existing workflows remains disabled.

• Expanded contract and procedure controls

  Released customer device recovery/revocation, reviewed-procedure activation/drafting/retirement and jurisdiction-pack validation. Project policy and legal-rule content still require authorized configuration.

• Approved jurisdiction packs

  Validation machinery does not supply approved legal rule content; authoritative pack review remains outstanding.

• Richer direct-face DXF path

  Direct POINT/LINE/3DFACE extraction, restricted parsing, listener recovery, Documents opening and printing passed isolated staging acceptance. This successor is distinct from the production DWG viewer.

• Broader regional recovery

  Current isolated authentication, encrypted capture/restore, scoped regional-independence and backup recurrence evidence exists; full current-region production promotion/routing/write survival/failback remains unaccepted.

• Native Revit and federation

  Licensed native translation, multi-model federation and cross-source coordinate reconciliation remain advanced integration work.

• 4D and 5D intelligence

  Model-linked schedule playback, cost exposure, trade/zone capacity and richer package/procurement readiness remain roadmap scope beyond bounded delivered tools.

• Calibrated predictive models

  Trained, prospectively validated delay/cost probabilities require suitable outcome data and validation; workload scenarios are not those probabilities.

• Autonomous reality capture

  Continuous drone feeds, photo-to-3D reconstruction, calibrated field-to-plan deviation measurements and certified visual takeoff remain unestablished.

• Full operational digital twin

  Automatic asset/BIM identity mapping, sensor-based physical-state simulation and municipal lifecycle synchronization remain incomplete.

• General regulator synchronization

  Live CSLB/DIR/wage and broad jurisdiction feeds remain separate from the limited delivered permit adapter.

• Unrestricted self-learning and repair

  Autonomous model-weight training, arbitrary executable self-modification and universal automatic infrastructure repair are not delivered capabilities.

Scope and availability: Some staging/candidate areas continue to change. Only a scoped acceptance/deployment receipt can promote their availability status.

Detailed platform-specific work remains visible without confusing source code, tests and public distribution.

• Restricted native login contract

  Issue enrollment/sync credentials through dedicated client routes rather than a generic unrestricted API bridge.

• Device-bound token authority

  Tie synchronization authority to the selected enrolled device and current owner.

• Native project directory

  Return only projects individually authorized for the current tenant, user, device, organization, membership and client surface.

• Minimal project identity envelope

  Return schema version, tenant/user/device identity and minimal project ID, name, number and lifecycle fields.

• Bounded directory pagination

  Scan a bounded page and continue by cursor, including empty visible pages with more candidates remaining.

• Private directory responses

  Use no-store responses and a request-rate limit for the installed-client project selector.

• Full-envelope native replay check

  Compare canonical payload, signature, proof version, record identity, operation type, version, logical clock, counter and normalized wall-clock before replaying a receipt.

• Altered retry rejection

  Return conflict for an operation UUID reused with changed content instead of presenting an earlier accepted receipt.

• Monotonic batch high-water mark

  A refused lower counter cannot lower the threshold for subsequent items in the same batch.

• Stable refused receipts

  An exact retry of a refused operation retains its prior disposition; it does not become accepted.

• Protected native draft storage

  Windows durable counters and OS-protected draft queues are in active implementation and acceptance.

• Isolated online portal window

  Windows development embeds the existing online portal in a sandboxed window with normal web login and CSRF, separate from privileged native storage.

• Online workflow reuse

  RFI, submittal, timecard and approval workflows use their existing portal authority instead of bypassing it through device tokens.

• Controlled child views

  Desktop development covers document popups, same-origin blob previews, printing and user-visible downloads without exposing a privileged bridge.

• Identity-change cleanup

  Desktop acceptance checks account cancellation, logout and separate browser-session cleanup.

• Cached snapshot limitation

  A snapshot checksum is not a detached server-signed grant. Cached permissions support bounded offline UX, not fresh server authority.

• Reconnect authorization

  Server checks current device, membership, project, organization, field policy and signatures before accepting drafts.

• Consequential command refusal

  Formal offline commands remain refused; a draft receipt does not approve, issue or pay a record.

• Cross-platform material workflow

  Windows/iOS/Android candidate work includes draft, submit, return, approve, order and receive stages with named approvers.

• Authorized approver picker

  Candidate material workflow resolves eligible people by project authority instead of relying on a typed internal identifier.

• Voice-to-material draft protection

  Candidate validation prevents voice-created line items from injecting approval fields.

• Shared mobile bridge and UI

  Android and iOS source integration and shared generated interface assets are being reconciled and tested.

• Android build verification

  The development task records a successful native compile; broader tests and signed distribution remain separate.

• Installed reviewer acceptance

  Synthetic desktop login/read/CSRF/logout checks passed; installed reviewer, offline queue and full release acceptance remain open at this checkpoint.

• Protected original-operation queue

  New native source work preserves the original signed operation in a protected queue rather than regenerating it on every retry.

• Deterministic enrolled Ed25519 signing

  Native source work signs the enrolled-device envelope deterministically; focused tests verify the signing contract.

• Immutable signed-envelope readback

  Native queue components read back the retained envelope and detect changed stored content.

• Validated immutable native receipts

  Native source components validate and retain immutable receipt results for the submitted operation.

• Exact native upload transport

  New orchestration targets the dedicated operations contract with account/device identity checks; current orchestration tests use mocked transport.

• Native integration boundary

  The new queue/orchestration is not yet integrated into the main/renderer release or accepted against the live server; no newer signed executable acceptance is recorded.

Scope and availability: Server project-directory and replay fixes are released. The Windows and mobile application components listed as development require their own signed-build, installed and physical-device acceptance.

Named recovery mechanisms exist; later staging registrations do not imply blanket production activation.

• Structured database diagnosis

  Classify transaction conflicts, contention, timeouts, interruptions, access failures, constraints, schema/query errors and cancellation using driver codes.

• Sanitized diagnostics

  Avoid exposing SQL text, bindings, credentials or customer payloads in recovery guidance.

• Allowlisted read recovery

  Retry only explicitly supported factory and inventory reads, rather than arbitrary application calls.

• Three-attempt retry budget

  Bound eligible transient read recovery to at most three attempts.

• SQLite contention handling

  Recognize BUSY/LOCKED failures within the eligible retry policy.

• PostgreSQL contention handling

  Recognize selected lock-unavailable and transient read failures without retrying permanent errors.

• Per-attempt authorization refresh

  Recheck user, tenant, administrator and reference authority before retrying and returning data.

• Pinned initiating identity

  Prevent a retry from following a later account or tenant switch into another scope.

• Circuit cooldown

  After exhausted transient work, retain a bounded cooldown rather than retry indefinitely.

• Private retry guidance

  Return private 503 responses with a retry indication and a fixed reason code for eligible failures.

• Uncertain-write reporting

  Report an unconfirmed write outcome without claiming either success or loss.

• No blind write replay

  Reconcile uncertain mutations by their durable receipt/idempotency identity instead of automatically repeating them.

• Statement deadlines

  Apply transaction-local PostgreSQL statement deadlines to supported reads.

• Lock deadlines

  Apply transaction-local lock deadlines while preserving stricter deployment limits.

• Caller transaction protection

  Do not interfere with caller-owned transactions or leak timeout settings beyond commit/rollback.

• Telemetry isolation

  A telemetry failure must not transform a completed operation into a replayable failure.

• Batch fault isolation

  One failing application does not prevent another eligible application's inspection or recovery.

• Truthful batch exit status

  Report failed, degraded and deferred work rather than labeling a partly failed sweep successful.

• Cancellation respect

  Do not retry explicit cancellation or permanent permission/schema failures.

Scope and availability: Self-healing means bounded handling of named failures. It is not an error-free guarantee, arbitrary query rewriting, unrestricted code repair or zero-downtime certification.

Controlled repair preserves business records and publication authority.

• Scheduled application health sweep

  Inspect a bounded set of app definitions and runtime state with overlap and lease guards.

• Known-good definition restoration

  Restore an eligible prior valid published definition while preserving recorded business data.

• Row-locked definition repair

  Own one scoped transaction during repair and retain tenant ownership.

• Derived-index health checks

  Detect eligible missing or inconsistent derived indexes separately from original records.

• Bounded index repair

  Repair supported derived indexes within configured scan/repair budgets.

• Ordinary timer index acceptance

  Saved staging evidence includes timer-driven repair; configuration alone is not counted as that scenario test.

• Stale generation recovery

  Inspect eligible abandoned generation work through a separately enabled recovery schedule.

• Invalid-schema correction attempt

  For eligible completed invalid provider output, make at most one guarded correction request.

• Correction authorization guard

  Refresh builder permissions, app version, references and catalog before a second provider attempt.

• Separate correction accounting

  Reserve quota and settle usage separately for each attempt, linking the correction to the original.

• Shared provider deadline

  Use only the remaining original deadline; do not start a correction when insufficient time remains.

• No automatic publication from repair

  A corrected schema remains subject to validation, review and explicit publication.

• Unsupported integration refusal

  Do not retry unsupported external integrations, unavailable references or unknown connection outcomes as automatic schema fixes.

• Incremental app generation

  Retain constrained definition/version semantics when generating an eligible application change.

• Lease-aware progress

  Check ownership before doing sweep work or advancing its cursor.

• Admission-contention recovery

  Later staging evidence records bounded admission contention retry; this does not prove recovery of every API or worker failure.

Scope and availability: Core factory tooling has an earlier production release. Newer repair switches and exact acceptance belong to their recorded staging revisions; generation correction is independently gated.

Durable admission and recovery workflows protect source identity.

• Upload admission transitions

  Track accepted upload intent separately from its final target receipt.

• Private upload recovery snapshots

  Retain bounded private source snapshots for eligible finalization recovery.

• Quarantine recovery

  Inspect eligible quarantined upload work without treating unsafe content as clean.

• Real scanner integration tests

  Recorded isolated recovery acceptance includes actual scanner execution and refusal paths.

• Queued finalization recovery

  Recover eligible interrupted upload finalization through a scoped handler and durable identity.

• Atomic target receipt linkage

  Link a finalized target to the corresponding upload operation rather than inventing a second result.

• Permission-aware queued reprocessing

  Revalidate source ownership and current processing authority before delayed work.

• Knowledge extraction recovery

  Maintain named recovery handling for eligible extraction intents and source/version identities.

• Page-batch preservation

  Acceptance criteria protect already committed page/passage hashes during recovery.

• Ordinary extraction timer gap

  Current registration is evidenced; the latest owned interrupted-admission timer scenario remains a separate unfinished acceptance.

• BIM admission outbox

  Record initial BIM-source admission with tenant/project/version/hash/storage identity and original uploader.

• Fenced delivery claim

  Use a time-bounded delivery claim before inserting the admitted extraction job.

• Transactional queue insertion

  For supported database queues, insert the job and sent receipt in the same transaction.

• Transport-specific refusal

  Unsupported queue transports remain pending; no nontransactional fallback is presented as equivalent.

• Delivery attempt budget

  Bound admission attempts, cooldown, lifetime and sweep size.

• Duplicate-admission protection

  Repeated admission cannot reset the original work budget.

• Extraction/publication distinction

  Delivery of an extraction job does not mean extraction, human review or model publication succeeded.

• Private snapshot cleanup

  Bound deletion and scanning of eligible expired recovery snapshots.

• Scheduler overlap guards

  Prevent overlapping eligible health, generation, index, quarantine, extraction, finalization and cleanup runs.

• Separate manual retry

  Keep explicit manual BIM retry separate from initial admission-delivery recovery.

• Partial PDF recovery acceptance

  A newer isolated real-Laravel test preserves committed page 1 and completes page 2 after a deliberately injected fault. The deployed ordinary-timer continuation remains a distinct acceptance.

Scope and availability: Later staging has enabled recovery registrations. Handler tests, timer observations and full workflow recovery are different evidence levels; not every promised failure has an accepted timer scenario.

Infrastructure developments are listed individually with their current acceptance limits.

• Immutable release identity

  Bind prepared runtime files and configuration to reviewed release manifests.

• Baseline drift refusal

  Stop a deployment when current production files differ from the approved baseline.

• Shared deployment lock

  Serialize cooperating releases instead of overwriting simultaneous work.

• Pre-release backups

  Preserve affected runtime files, configuration and database snapshots before accepted releases.

• Private database backup verification

  Validate retained backup archive structure with the matching database tool version.

• Source-hash parity

  Compare deployed bytes with reviewed/tested candidate hashes.

• Controlled service reload

  Reload application services and gracefully restart queue workers after the release switch.

• Known-state rollback

  Restore backed-up runtime/configuration while preserving newly recorded evidence and signing identity.

• Immutable activation receipts

  Record exact staging release, configuration and runtime-acceptance identities.

• Interrupted publication recovery

  Candidate supervisor work records durable intent and permits recovery only from recognized partial publication states.

• Unknown-state refusal

  Refuse another exchange or blind rollback when release ownership or pending-state identity is uncertain.

• Service startup checks

  Verify web, worker and scheduler service behavior before opening the accepted staging endpoint.

• Boot-persistence checks

  Inspect startup enablement and bounded retry requirements after reboot; full current regional acceptance remains separate.

• Encrypted checkpoint capture

  Create encrypted snapshots with independently verified ciphertext identity.

• Cross-host retained copies

  Verify matching retained encrypted bytes and receipts on two hosts for accepted staging captures.

• Interrupted transfer reconciliation

  Resume transfer of the exact existing ciphertext without silently recapturing a new snapshot under the old identity.

• Scheduled backup recurrence

  A later ordinary staging timer capture completed unattended with matching two-host evidence.

• Plaintext cleanup verification

  Check removal of owned temporary plaintext and work artifacts after retained capture.

• Revision hold for backup changes

  Pause eligible backup work during a staged revision until its own acceptance completes.

• Restoration rehearsal

  Recorded isolated restores reconcile selected database rows and file objects; coverage gaps remain explicit.

• Region promotion preparation

  Prepare/fence source and destination runtime identities before a proposed failover.

• HTTPS and DNS acceptance

  Require runtime, private HTTPS, routing and post-route checks rather than treating promotion alone as successful failover.

• Post-route write survival

  Regional acceptance requires scoped writes/files to survive the routed runtime and later reconciliation.

• Failback verification

  Returning to the original region requires its own acceptance and permission/state reconciliation.

• Restored-document authorization

  A remaining specific test must verify an existing restored document's actual authorized download, version/hash and denied-access behavior.

• Provider security dependency tracking

  Retain unresolved provider storage/security questions as dependencies rather than claiming external certification.

Scope and availability: Production release safeguards are in use. The broader regional program is isolated staging work; complete automatic regional failover, continuous backup guarantees and universal self-repair are not established.

All previously discussed advanced concepts remain visible; a concept is not a shipped feature.

• Design-package readiness

  Propose versioned deliverable/prerequisite views by discipline or zone, without treating incomplete evidence as permission to build.

• Confirmed change impact map

  Extend confirmed model/record links into review impact across requirements, activities and cost allocations.

• Procurement exposure map

  Relate declared lead times and required-on-site dates to selected package/installation assumptions.

• Model federation

  Combine models only after explicit units, coordinate and reference alignment acceptance.

• 4D schedule playback

  Propose model state playback bound to explicitly mapped schedule versions and activity dates.

• 5D cost exposure

  Propose allocated cost links with protection against counting the same cost line repeatedly.

• Licensed Revit translation

  Evaluate authorized RVT translation separately from native Revit authoring or automation.

• Information Delivery Specification checks

  Evaluate machine-readable model information requirements against a supported model/toolchain.

• Model-to-BCF action drafts

  Prepare traceable issue/RFI drafts from accepted coordination findings for human adoption.

• Prospective risk outcomes

  Capture what was known at forecast time and prevent later outcomes or revisions leaking into training features.

• Calibrated risk probabilities

  Require chronological holdout comparison, calibration and uncertainty before advertising delay/cost probabilities.

• Trade and zone capacity

  Model declared resource demand, access and temporary-work occupancy for supported scenarios.

• Weather-sensitive work exposure

  Use dated forecasts and explicitly approved thresholds for advisory activity exposure.

• Design-build interface responsibility

  Record named organizations, delegated design and scope boundaries with source-backed authority.

• Commissioning and turnover map

  Propose versioned associations among equipment, tests, O&M requirements and asset records.

• Evidence Readiness Map

  Prototype a 3D view of missing release evidence and prerequisites rather than inferred physical defects.

• Decision Replay

  Reconstruct the evidence available when a decision was recorded while keeping later information separate.

• Minimum-Unblock Plan

  Propose a bounded set of documented review/procurement steps that clears declared prerequisites, with conditional effects.

• Continuous field-to-plan capture

  Future calibrated image/drone pipelines need source registration, physical scale, temporal alignment and validation.

• Municipal living asset twin

  Future live simulation and municipal handover require real asset identity, sensor connections and maintenance data contracts.

• Broad regulator synchronization

  Future CSLB, wage and permit feeds need authorized providers, current jurisdictions and source validation beyond the limited existing adapter.

• Autonomous code repair boundary

  Arbitrary generated code, automatic hotfix deployment and foundation-model self-training are not implemented by bounded recovery.

Scope and availability: These are engineering directions and product concepts, not patent novelty, competitor superiority or an error-free guarantee.

How to describe the system accurately while retaining every reliability development.

• Self-healing claim

  TRACE contains bounded, permission-aware recovery mechanisms for named failures; each requires its recorded configuration and acceptance.

• Error-free claim boundary

  No finite test suite establishes an error-free system. Public wording should name verified safeguards and observed results.

• No test-count inflation

  Overlapping suites, inherited tests and different frozen releases are not added into a universal coverage percentage.

• Source-scoped answer quality

  An accepted cited answer or adversarial fixture is evidence for that case, not universal answer accuracy.

• No inevitable intelligence growth

  Scheduled failure capture and reviewed evaluation enable improvement work; next year is not automatically smarter without validated changes.

• Fail-closed consequential actions

  Missing authority, evidence, stale sources, unsupported inputs or uncertain outcomes result in refusal or review rather than invented success.

• Production versus staging distinction

  A registered timer, built binary, private prototype or successful isolated test is not a production release receipt.

• Real versus synthetic distinction

  Demonstration records, generated fixtures and prepared stock movements remain labeled as synthetic.

• Configuration dependency disclosure

  Provider accounts, merchant credentials, legal rule adoption and per-user grants control availability.

• Independent decision authority

  Human engineering, legal, safety, payment and project approvals remain attributable to authorized people.

Scope and availability: This inventory documents capabilities and developments; it is not an independent certification or a new full-system test.

Choose the modules your team needs. Availability, project permissions and licensed scope apply.

• TRACE help & training

  TRACE answering questions about TRACE Management System itself: how to use each screen, what a capability does, and the basics of public-works administration. Reads the TRACE product knowledge base only - never your project evidence - and cannot draft contract documents.

  Available · Included account tool
• Account & profile

  Profile, password, company logo, sign-in security.

  Available · Included account tool
• Projects

  Create and open the projects inside your own account.

  Available · Included account tool
• TRACE project assistance

  TRACE - Traceable Record-Anchored Cited Evidence. Cited answers grounded in THIS project's own authorised records, plus drafting and preparation help for RFIs, submittals and notices. TRACE cites or refuses; it never decides, and every formal action still requires an accountable human.

  Available · License required
• Submittals

  Submittal register, spec-section routing, review clocks and stamping.

  Available · License required
• RFIs

  RFI register, ball-in-court clocks and sealed responses.

  Available · License required
• Daily reports

  Field daily reports with sealed signatures; corrections append.

  Available · License required
• Daily Project Success Brief

  A daily position statement assembled deterministically from this project's own sealed records and contract clocks. Every line carries its citations, its epistemic type, its freshness and a derived confidence, and anything the system cannot know is printed as an explicit refusal. No language model writes any part of it.

  Available · License required
• Branded RFI & submittal documents

  Issue-ready RFI and submittal transmittals composed from the record itself and branded to YOUR account and your counterparty - never to TRACE Management System. Parties, precedence of contract instruments, contract clock and sealed attachment hashes are derived, not typed.

  Available · License required
• Schedule intelligence

  Immutable schedule versions, deterministic CPM checks and an authorisation-filtered delta ledger.

  Available · License required
• Project documents

  Ingest born-digital files, scanned PDFs and direct drawing/receipt images as tenant-scoped evidence. OCR text, page identity, extraction method and confidence remain attached to every retrievable passage; low-quality visual evidence requires human confirmation.

  Available · License required
• Photos & media

  Media upload with SHA-256 provenance sealing.

  Available · License required
• Weather intelligence

  Live forecast bound to project coordinates, with cited weather notices.

  Available · License required
• TRACE Field applications

  Commercial product ceiling for TRACE Field on mobile and approved field devices. Platform sales controls the product licence; the City then narrows the enabled project features, each organization, and each person. Device operating-system permissions and Meta preview enrollment remain separate gates.

  Available · License required
• Look-ahead schedule

  Three-week rolling look-ahead drafts, constraint tracking, accountable transitions, and project export.

  Available · License required
• Inspections & punch

  Inspection, observation, deficiency and punch capture. Closure requires an accountable formal determination - a party claim or an AI recommendation cannot close an item - and every status change appends a hash-chained event.

  Available · License required
• Permits & agency approvals

  Country- and jurisdiction-aware permit screening with editable federal, state/province and local candidates. Applicability requires an accountable project-specific basis; issued status requires clean evidence, and every determination remains in a hash-chained history.

  Available · License required
• Change orders

  Change orders with approval and incorporation kept as two separate acts, allocation to the schedule of values, and a contract-growth bridge that never touches the original contract value.

  Available · License required
• Preconstruction & procurement

  Governed preconstruction readiness, qualification, solicitation, addenda, controlled bid receipt and human award workflows. Public and private procurement profiles are configurable operating postures, not legal-compliance determinations.

  Available · License required
• Estimating & takeoff

  Contractor-facing source-bound takeoff, deterministic estimating, cost-code basis and controlled estimate handoff. Internal estimates, quotes, budgets and leveling details are not exposed to an owner merely because the owner uses TRACE.

  Available · License required
• Payment applications

  Progress billing on a schedule of values, with server-authoritative refusal of structurally improper requests, two-person certification bound to a content hash, and compliance withholdings that reduce the amount without stopping the payment clock.

  Available · License required
• Releases & stop notices

  Waivers and releases under Civil Code ss. 8132-8138 and public-works stop payment notices under ss. 9300-9364. Reported as two totals that are never netted against each other: a release reduces exposure to a claimant, a notice freezes money still owed to the contractor.

  Available · License required
• Trade partners & credentials

  Project trade partners and subcontracts with attributable licence, DIR, bond and insurance windows evaluated for the day the work occurred.

  Available · License required
• Labor compliance

  Configurable California public-works and project-specific PLA/CWA requirements; sealed subcontractor submissions; DIR receipt, prevailing-wage, DAS 140/142, apprenticeship-ratio, training-fund, assent, dispatch, local/targeted-hire and workforce tracking; deterministic exception review with human resolution.

  Available · License required
• Meetings

  Project meetings with agenda, content-hashed minutes, action items, and accountable finalization.

  Available · License required
• Transmittals

  Append-only issued-document register for branded RFI, submittal, change-order, and pay-application cover transmittals.

  Available · License required
• Job walk

  Project-scoped field walks, content-hashed observations, responsible parties, due dates, evidence-backed closure, and accountable finalization.

  Available · License required
• Plans coordination

  Native API-backed plan sets, project-document sheet proposals, human-attested bulk registration, safe preview, immutable revisions, formal review, internal markups, and OCR of scanned notes, legends and sheet references with page/region provenance. Project-specific precedence is a separate named human determination. TRACE may read cited extracted evidence; geometry, scale, dimensions, linework and design intent require supported visual analysis or human confirmation and are never inferred from OCR alone.

  Available · License required
• BIM coordination

  Governed IFC ingestion with immutable source hashing, isolated object/property extraction, a human publication gate, an internal reviewed-geometry viewer, searchable model objects, explicit revision-bound evidence links to authorized RFIs/submittals/schedule activities, extracted-property revision comparison, bounded single-model IFC intersection and clearance candidates, and BCF 2.1 issue exchange. Native Revit ingestion, model federation, geometric revision comparison, design certification, and permission-to-build decisions are not claimed.

  Available · License required
• Safety & observations

  Observations, incidents, near misses, toolbox talks, training and corrective actions with human recordability determinations and hash-chained transitions.

  Available · License required
• Budget & costs

  Project cost-code register for budget, commitments, actual cost, forecast and variance with attributable, hash-chained revisions.

  Available · License required
• Timesheets

  Crew and equipment hours by cost code.

  Available · License required
• Closeout

  Evidence-backed turnover checklist, human closure acknowledgment, and read-only project archive.

  Available · License required
• Send to City

  Agency package builder using governed record snapshots, a sealed manifest and SHA-256 fingerprints. Export never falsely claims agency submission, receipt, or acceptance.

  Available · License required

Package inclusion is confirmed in your quote. Connected services and device permissions may require separate setup.