← Back to catalogue
Published

Construction Work

vr.wm-blt-007 · wm-blt-007-construction-work

Describe and review one bounded construction undertaking from definition through execution, partial outcomes and retained completion history.

World Models Physical world and living systems PHY.BLT.WRK

Bundle → Layer → Finding → Questions Filled

7 bundles · 14 layers · 14 findings · 42 questions

Work definition Stable undertaking identity and its physical context.

Identity and scope

Preserve the work identifier across revised scope, completion and later defects. Classification and supersession are explicit local decisions.

Identity and scope

Preserve the work identifier across revised scope, completion and later defects. Classification and supersession are explicit local decisions.

  1. Which master identifier and namespace identify this undertaking independently of its permit and asset references? identity
  2. What work kind, deliverables, exclusions and design revisions define the current scope? definition
  3. Which earlier undertaking or scope revision is superseded, split or related, and on whose recorded decision? lifecycle

Site and affected assets

Locate the undertaking and link assets it creates, alters or removes without claiming land rights or collapsing their identities.

Site and affected assets

Locate the undertaking and link assets it creates, alters or removes without claiming land rights or collapsing their identities.

  1. Which sites, parcels, work zones and coordinate references delimit the affected locations? spatial
  2. Which asset references are created, altered, retained or removed by each scope item? relationship
  3. Which access constraints, surveys and uncertainties qualify the declared work area? constraint
Responsibilities and authority Role assignments and applicable external constraints.

Parties and responsibility

Role-specific responsibilities are time bounded and distinct from record ownership or property ownership.

Parties and responsibility

Role-specific responsibilities are time bounded and distinct from record ownership or property ownership.

  1. Which role-based steward controls the work record and which parties perform, design or inspect the work? ownership
  2. What appointment or delegation evidence establishes each role for the relevant scope and interval? authority
  3. Who can view commercial, worker or safety-sensitive information, and which disclosures need a restricted projection? access

Permits and applicable conditions

Record applicability and external decision evidence separately from observed work status. Unknown is not permission, and unauthorized events remain recordable.

Permits and applicable conditions

Record applicability and external decision evidence separately from observed work status. Unknown is not permission, and unauthorized events remain recordable.

  1. Which jurisdiction, contract and work profile determine whether each permit, notification or approval is required? requirement
  2. Which external decisions and conditions apply to which work portions and effective dates? authority
  3. How are expired, suspended, disputed, missing or exceeded authorizations recorded without hiding actual work? exception
Plan and change control Baseline sequence and revision decisions.

Breakdown and scheduling

Represent work portions, task references, dependencies and distinct baseline and forecast times. No universal phase ordering is assumed.

Breakdown and scheduling

Represent work portions, task references, dependencies and distinct baseline and forecast times. No universal phase ordering is assumed.

  1. Which work portions, task masters and dependency relationships form the adopted breakdown? composition
  2. Which baseline, forecast, actual intervals and calendar references apply to each scheduled portion? temporal
  3. What evidence and role can release a recorded hold point, and how is an unresolved dependency shown? process

Scope changes and discontinuity

Record proposed and authorized changes, suspension, restart or cancellation without overwriting prior baselines.

Scope changes and discontinuity

Record proposed and authorized changes, suspension, restart or cancellation without overwriting prior baselines.

  1. Which proposal changes scope, design, time or conditions relative to a named baseline? state
  2. Who decided the change and what external permit, contract or design approvals remain unresolved? decision
  3. Which suspension, restart or cancellation assertion affected which portion and interval? event
Execution observations Physical progress evidence and safety governance context.

Measured and reported progress

Progress is an attributed observation against a baseline and a defined quantity or milestone basis. Forecast, payment and acceptance are distinct.

Measured and reported progress

Progress is an attributed observation against a baseline and a defined quantity or milestone basis. Forecast, payment and acceptance are distinct.

  1. What was observed for each work portion, by whom, when and using which method? provenance
  2. What numerator, denominator, units, baseline and uncertainty support the reported quantity or percentage? measurement
  3. How are conflicting, stale, corrected or unverified reports retained and evaluated? quality

Safety and site constraints

Retain policy-level hazard, plan, inspection and incident references. No generated instructions for dangerous site operations are included.

Safety and site constraints

Retain policy-level hazard, plan, inspection and incident references. No generated instructions for dangerous site operations are included.

  1. Which safety plan revision, accountable roles and hazard assessments apply to the present work scope? security
  2. Which site constraints or inspection findings affect readiness, and what competent review is outstanding? constraint
  3. Which restricted incident or stop-work references explain the current recorded constraints? exception
Materials and environmental interfaces Work-specific material trace and disposition evidence.

Material and installed-item trace

Link material batches and installed or removed items to work portions, specifications and review evidence. Resource consumption is distinct from task identity.

Material and installed-item trace

Link material batches and installed or removed items to work portions, specifications and review evidence. Resource consumption is distinct from task identity.

  1. Which material or component identifiers and batches are linked to the affected work portions? identity
  2. Which specification revision and inspection evidence support the recorded use or rejection? validation
  3. Which substitutions, unknown origins or unresolved trace gaps require a disposition? exception

Disposition and environmental evidence

Distinguish planned reuse or recycling from evidenced disposition. Environmental and hazardous-material obligations require an adopted specialist profile.

Disposition and environmental evidence

Distinguish planned reuse or recycling from evidenced disposition. Environmental and hazardous-material obligations require an adopted specialist profile.

  1. Which removed or surplus material streams have recorded quantities, units and classification evidence? classification
  2. What destination, transfer reference and receipt evidence support the claimed disposition? evidence
  3. Which environmental conditions or unknown classifications remain unresolved before a compliance claim? requirement
Inspection and nonconformity Scope-specific quality assessment and correction evidence.

Inspection and test evidence

Examinations refer to a specific scope and requirement revision; results do not automatically accept work.

Inspection and test evidence

Examinations refer to a specific scope and requirement revision; results do not automatically accept work.

  1. Which work portion and requirement revision did each inspection or test examine? definition
  2. Who performed and reviewed it, using which method, conditions and evidence? evidence
  3. What verdict, limitations, outstanding tests and hold-point implications were recorded? validation

Defects and correction

A reported defect may originate outside a formal inspection. Correction assertions require separate verification and may be reopened.

Defects and correction

A reported defect may originate outside a formal inspection. Correction assertions require separate verification and may be reopened.

  1. Which observed nonconformity, location and requirement discrepancy define the defect report? quality
  2. Which responsible role and correction evidence address the reported defect? process
  3. What verification, residual limitation or contrary evidence supports closure or reopening? lifecycle
Outcomes and record continuity Partial or final acceptance and controlled handover.

Acceptance and residual obligations

Allow zero or many scoped outcome records. Contract acceptance, occupancy authorization, commissioning, payment and ownership transfer have separate evidence and masters.

Acceptance and residual obligations

Allow zero or many scoped outcome records. Contract acceptance, occupancy authorization, commissioning, payment and ownership transfer have separate evidence and masters.

  1. Which work portion was accepted, rejected or left pending under which decision and effective date? decision
  2. Which reservations, residual obligations or separately authorized operational uses qualify that outcome? constraint
  3. Which later claim, latent defect or correction changes the recorded assessment without erasing the original decision? temporal

Handover and retained history

A handover packages controlled references to as-built, safety and outcome evidence. Recipient receipt and completeness assessment are separate, and the work retains its identity.

Handover and retained history

A handover packages controlled references to as-built, safety and outcome evidence. Recipient receipt and completeness assessment are separate, and the work retains its identity.

  1. Which asset, operational recipient and required information profile define the handover scope? relationship
  2. Which exact artifact revisions, formats, missing items and recipient acknowledgments constitute the package? interoperability
  3. Which retention, access-transfer and lawful disposal rules govern the completed work history? retention

Classifiers Filled

Family
World Models
Category
Physical world and living systems
Entry kind
entity
Navigation path
NAV.PHY.BLT.WRK
Domain
PHY.BLT.WRK
Industry
Cross-industry
Tags
constructionworkphy.blt.wrk
Also called
U6

What it is Filled

A persistent work entity for construction, alteration, repair or demolition of built assets, carrying scope, site references, responsibilities, plans, observations and outcome evidence. All structures and functions below are proposed local research design informed by cited sources, not prescribed universal schemas or operational engineering instructions.

In scope

  • Work identity, classification and scope revisions
  • Sites, affected assets and external project or task references
  • Profile-specific authority, role and permit assertions
  • Baselines, sequencing, progress, suspension and change evidence
  • Material traceability, environmental disposition and safety governance references
  • Inspection, nonconformity, partial acceptance and handover records

Out of scope

  • Portfolio and contract accounting, wages, invoices and ownership transfer
  • Asset geometry masters, structural calculations, design approval or autonomous site control
  • Issuing permits, certifying occupancy, accepting works or ordering suspension through model functions
  • Detailed hazardous-material, demolition or emergency-response procedures

Why it exists Filled

Describe and review one bounded construction undertaking from definition through execution, partial outcomes and retained completion history.

Distinguishing features Derived, awaiting review

  • Unlike WM-ACT-005 Project: Project governance, finance and portfolio identity remain external. This root is a persistent construction undertaking with its own execution scope; a small undertaking need not have a separately instantiated project record.
  • Unlike WM-ACT-006 Task / Work Item: Tasks are execution units referenced by the work breakdown. A task completion event does not close the undertaking or certify its product.
  • Unlike WM-BLT-001 Building / Structure and WM-BLT-003 Infrastructure Network: Produced, altered or removed assets retain separate identities before and after acceptance. A demolition undertaking may produce no new asset. Work history does not change class into the product.
  • Unlike WM-PLC-002 Land Parcel: Site and affected parcel references locate work; they do not establish title, access rights or property boundaries.
  • Unlike WM-POL-004 Permit / Authorization: Permit decisions and their authoritative terms are referenced. An undertaking can lack a permit because none is required, an application is pending, or unauthorized work occurred; these states must remain distinguishable.
  • Unlike WM-ACT-013 Maintenance: Maintenance management can commission a bounded construction undertaking. Permit presence alone does not distinguish maintenance from construction; record the adopted classification and link both masters without duplicating work.
  • Unlike WM-ACT-019 Incident / Emergency: Incident reports and emergency response remain externally mastered; this record carries restricted references and effects on work status.
  • Unlike Contract, design and inspection masters: Contracts, approved designs, formal tests and legal decisions are referenced with revisions and issuer scope. This model stores work-specific assertions and trace links, not replacement legal or engineering masters.

Note: Derived from boundary notes against neighbouring models.

What robots and AI may and may not do Derived, awaiting review

Must not

  • Record unauthorized, unsafe or disputed observations honestly while flagging the exception; never suppress facts to satisfy a readiness rule.
  • Deny by default; grant purpose-limited role access to the minimum work scope, fields and artifact revisions.

May

  • Register work identity: Proposed, unimplemented local operation. Create a proposed local undertaking record with scope and separately mastered context.
  • Record baseline revision: Proposed, unimplemented local operation. Preserve a previous baseline and record a new decision-backed revision.
  • Record progress evidence: Proposed, unimplemented local operation. Capture an observation and assess its measurement basis without certifying completion.
  • Link inspection or correction review: Proposed, unimplemented local operation. Attach scoped evidence and record a qualified review state.
  • Record an external outcome: Proposed, unimplemented local operation. Record a partial acceptance, suspension or other externally issued decision as evidence.
  • Prepare restricted handover projection: Proposed, unimplemented local operation. Build a local review package of permitted artifact revisions and outstanding items.

Note: Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.

Moral aspects Derived, awaiting review

  • Delete eligible payloads only under authorized retention and privacy policy, retaining only lawful minimal tombstones and non-sensitive referential metadata; history does not justify indefinite personal-data storage.

Note: Sentences mentioning harm, privacy, consent or similar, collected from the specification.

Owners Filled

Steward

Name a role-based work record steward, delegated scope and contact mechanism; no prescribed company owner.

Roles

Work record steward
Own namespace and record continuity; maintain scope and adopter profiles.
Authorized recorder
Record evidence with source, time and uncertainty; cannot issue external approvals.
Construction coordinator
Maintain plan and responsibility references; escalate unresolved authority or safety constraints.
Qualified reviewer
Review only within appointed competence and scope; distinguish review from acceptance authority.
Acceptance decision custodian
Link issuer decisions and reservations without creating legal effects.
Information custodian
Apply access, handover, integrity and lawful retention controls.

Links to other meta-models Filled

references

  • WM-ACT-005 - Optional project governance master; no inherited project completeness claim.
  • WM-ACT-006 - Execution task references and breakdown mappings; binding revision must be chosen by adopter.
  • WM-BLT-001 - Building or structure produced, altered or removed; independently mastered identity.
  • WM-BLT-003 - Infrastructure network affected by the undertaking; no automatic operational state mutation.
  • WM-PLC-002 - Site parcels by authoritative external reference without asserting title or access rights.
  • WM-POL-004 - Optional permits and authorization decisions; absence must be qualified, not interpreted as permission.
  • WM-ORG-001 - Role-assigned organizations remain external masters with local appointment evidence.
  • WM-ACT-013 - Maintenance context that may commission a construction undertaking; avoid duplicate work identity.
  • WM-ACT-019 - Restricted incident references and work-status effects; response stays external.

aligned

  • IFC 4.3.2.0 IfcTask and IfcWorkSchedule - Conceptual mapping of work portions, schedules and product links only; no IFC conformity or whole-root equivalence claimed.
  • PROV-O 2013-04-30 - Conceptual evidence attribution and derivation mapping; not a trust or authority proof.

neighbor

  • WM-ACT-005 Project - Project governance, finance and portfolio identity remain external. This root is a persistent construction undertaking with its own execution scope; a small undertaking need not have a separately instantiated project record.
  • WM-ACT-006 Task / Work Item - Tasks are execution units referenced by the work breakdown. A task completion event does not close the undertaking or certify its product.
  • WM-BLT-001 Building / Structure and WM-BLT-003 Infrastructure Network - Produced, altered or removed assets retain separate identities before and after acceptance. A demolition undertaking may produce no new asset. Work history does not change class into the product.
  • WM-PLC-002 Land Parcel - Site and affected parcel references locate work; they do not establish title, access rights or property boundaries.
  • WM-POL-004 Permit / Authorization - Permit decisions and their authoritative terms are referenced. An undertaking can lack a permit because none is required, an application is pending, or unauthorized work occurred; these states must remain distinguishable.
  • WM-ACT-013 Maintenance - Maintenance management can commission a bounded construction undertaking. Permit presence alone does not distinguish maintenance from construction; record the adopted classification and link both masters without duplicating work.
  • WM-ACT-019 Incident / Emergency - Incident reports and emergency response remain externally mastered; this record carries restricted references and effects on work status.
  • Contract, design and inspection masters - Contracts, approved designs, formal tests and legal decisions are referenced with revisions and issuer scope. This model stores work-specific assertions and trace links, not replacement legal or engineering masters.

What else AI and robots need to interact with it Incomplete

Identity and identifiers required Filled

  • Authoritative master-system identifier with issuer namespace
  • Stable local opaque identifier when no master identity exists
  • Revision identifier and content digest for the represented bytes, not a replacement for record identity

Direct properties required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Recognition required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Capabilities and actions required Filled

  • Register work identity: Proposed, unimplemented local operation. Create a proposed local undertaking record with scope and separately mastered context.
  • Record baseline revision: Proposed, unimplemented local operation. Preserve a previous baseline and record a new decision-backed revision.
  • Record progress evidence: Proposed, unimplemented local operation. Capture an observation and assess its measurement basis without certifying completion.
  • Link inspection or correction review: Proposed, unimplemented local operation. Attach scoped evidence and record a qualified review state.
  • Record an external outcome: Proposed, unimplemented local operation. Record a partial acceptance, suspension or other externally issued decision as evidence.
  • Prepare restricted handover projection: Proposed, unimplemented local operation. Build a local review package of permitted artifact revisions and outstanding items.

Hazards and failure modes required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Standards and interfaces required Derived, awaiting review

  • PROV-O: The PROV Ontology

Context of use required Filled

  • Great Britain HSE guidance and US federal FAR clauses are scoped examples, not globally applicable obligations.
  • No Cyprus or other local jurisdiction profile is asserted.
  • IFC and PROV-O supply conceptual exchange vocabulary, not construction safety or legal compliance certification.

Sources Filled

  1. IfcTask - buildingSMART International
  2. IfcWorkSchedule - buildingSMART International
  3. Administration - construction safety - Health and Safety Executive
  4. FAR 52.246-12 Inspection of Construction - Federal Acquisition Regulatory Council
  5. FAR 52.236-15 Schedules for Construction Contracts - Federal Acquisition Regulatory Council
  6. FAR 52.236-7 Permits and Responsibilities - Federal Acquisition Regulatory Council
  7. PROV-O: The PROV Ontology - World Wide Web Consortium
  8. Sustainable Management of Construction and Demolition Materials - United States Environmental Protection Agency

Open questions

  • Have the coordinator run check_sources.py outside the sandbox and separately verify source versions, substantive support, licensing and applicable local rules.
  • Develop executable adopter schemas and fixtures for unauthorized starts, partial acceptance, demolition without a new asset, scope changes, disputed progress, defects and restricted handover.
  • Restore an independent external review before any canonical or publishable-draft promotion; pin actual neighbor and exchange bindings before runtime use.
  • Independent external review is absent; Claude and Grok skipped under the owner waiver.
  • Direct HTTP checks unattempted under the owner-reported sandbox restriction; browser readings are not measured HTTP status or independent verification.
  • Current applicable law, contract deviations, permit and occupancy regimes, translations and licensing require qualified adopter review.
  • Nested candidate data schemas, precise state-transition rules, pinned neighbor bindings and executable mappings are incomplete.
  • Detailed project finance, design calculations, material and inventory masters, safety procedures and asset operation are delegated.
  • ISO 19650 clauses were not read or admitted; legacy wildcard import and conformity claims are rejected.

Machine files

Provenance

world-models research · reviewable-draft

Built from: models/wm-blt-007-construction-work/spec.yaml