# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T20:13:39Z", "synthesisSha256": "794cdd27e3be1a60c0f12a5ebb82cd630365dcd1c721217dd2644e3f82f55e06", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-BLT-007", "registryId": "vr.wm-blt-007", "name": "Construction Work", "version": "0.3.0", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.BLT.WRK" ], "tags": [ "construction", "work", "phy.blt.wrk" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-blt-007-construction-work/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-blt-007", "model": { "registry_id": "vr.wm-blt-007", "model_id": "WM-BLT-007", "name": "Construction Work", "entry_kind": "entity", "purpose": "Describe and review one bounded construction undertaking from definition through execution, partial outcomes and retained completion history.", "scope_statement": "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" ], "boundary_notes": [ { "neighbor": "WM-ACT-005 Project", "distinction": "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.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "WM-ACT-006 Task / Work Item", "distinction": "Tasks are execution units referenced by the work breakdown. A task completion event does not close the undertaking or certify its product.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "WM-BLT-001 Building / Structure and WM-BLT-003 Infrastructure Network", "distinction": "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.", "source_refs": [ "SRC-001", "SRC-008" ] }, { "neighbor": "WM-PLC-002 Land Parcel", "distinction": "Site and affected parcel references locate work; they do not establish title, access rights or property boundaries.", "source_refs": [ "SRC-001", "SRC-006" ] }, { "neighbor": "WM-POL-004 Permit / Authorization", "distinction": "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.", "source_refs": [ "SRC-006" ] }, { "neighbor": "WM-ACT-013 Maintenance", "distinction": "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.", "source_refs": [ "SRC-001", "SRC-003" ] }, { "neighbor": "WM-ACT-019 Incident / Emergency", "distinction": "Incident reports and emergency response remain externally mastered; this record carries restricted references and effects on work status.", "source_refs": [ "SRC-003" ] }, { "neighbor": "Contract, design and inspection masters", "distinction": "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.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] } ] }, "sources": [ { "id": "SRC-001", "title": "IfcTask", "organization": "buildingSMART International", "url": "https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/lexical/IfcTask.htm", "version_or_date": "IFC 4.3.2.0 (IFC4X3_ADD2)", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:11:59Z", "relevance": "Sections 5.3.3.6.1 and attributes: task identity, local status, timing and product relationships. Supports conceptual alignment, not equivalence of the whole undertaking to one task." }, { "id": "SRC-002", "title": "IfcWorkSchedule", "organization": "buildingSMART International", "url": "https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/lexical/IfcWorkSchedule.htm", "version_or_date": "IFC 4.3.2.0 (IFC4X3_ADD2)", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:11:59Z", "relevance": "Sections 5.3.3.11.1 and 5.3.3.11.6: schedules, controlled tasks and resources, project context and calendar placement. Mapping remains proposed." }, { "id": "SRC-003", "title": "Administration - construction safety", "organization": "Health and Safety Executive", "url": "https://www.hse.gov.uk/construction/safetytopics/admin.htm", "version_or_date": "Page displays 2026-01-12; CDM 2015 guidance context", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:11:59Z", "relevance": "Notifications, risk assessments, construction phase plan, health and safety file and inspection reports. Great Britain guidance is a profile example, not universal law or a source of engineering procedures." }, { "id": "SRC-004", "title": "FAR 52.246-12 Inspection of Construction", "organization": "Federal Acquisition Regulatory Council", "url": "https://www.acquisition.gov/far/52.246-12", "version_or_date": "Clause Aug 1996; page FAC 2026-01 effective 2026-03-13", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:11:59Z", "relevance": "Paragraphs (b)-(i): inspection records, quality responsibility, nonconformity and separate acceptance of portions. US federal contract clause example only; actual contract applicability remains unverified." }, { "id": "SRC-005", "title": "FAR 52.236-15 Schedules for Construction Contracts", "organization": "Federal Acquisition Regulatory Council", "url": "https://www.acquisition.gov/far/52.236-15", "version_or_date": "Clause Apr 1984; page FAC 2026-01 effective 2026-03-13", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:11:59Z", "relevance": "Paragraphs (a)-(c): scheduled sequence and dates, actual progress and supplemental schedules. No universal deadline or payment rule imported." }, { "id": "SRC-006", "title": "FAR 52.236-7 Permits and Responsibilities", "organization": "Federal Acquisition Regulatory Council", "url": "https://www.acquisition.gov/far/52.236-7", "version_or_date": "Clause Nov 1991; page FAC 2026-01 effective 2026-03-13", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:11:59Z", "relevance": "Necessary permits, applicable rules and responsibility for work and materials. Jurisdiction and contract must determine the adopting profile." }, { "id": "SRC-007", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "Recommendation 2013-04-30", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:11:59Z", "relevance": "Entity, Activity and Agent relationships support record attribution and derivation. Provenance does not certify truth, legal authority or engineering adequacy." }, { "id": "SRC-008", "title": "Sustainable Management of Construction and Demolition Materials", "organization": "United States Environmental Protection Agency", "url": "https://www.epa.gov/smm/sustainable-management-construction-and-demolition-materials", "version_or_date": "Page updated 2026-03-18", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:11:59Z", "relevance": "Construction, renovation and demolition material streams, reuse and recycling, and destination checks. Supports a material-disposition evidence dimension, not a compliance certificate or hazardous-material procedure." } ], "structure": { "bundles": [ { "id": "bundle-definition", "name": "Work definition", "description": "Stable undertaking identity and its physical context.", "rationale": "Prevent merging a work record with a contract, site or asset.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-008" ], "layers": [ { "id": "layer-identity", "name": "Identity and scope", "description": "Preserve the work identifier across revised scope, completion and later defects. Classification and supersession are explicit local decisions.", "source_refs": [ "SRC-001", "SRC-007" ], "findings": [ { "id": "finding-identity", "name": "Identity and scope", "description": "Preserve the work identifier across revised scope, completion and later defects. Classification and supersession are explicit local decisions.", "source_refs": [ "SRC-001", "SRC-007" ], "questions": [ { "id": "identity-q1", "text": "Which master identifier and namespace identify this undertaking independently of its permit and asset references?", "kind": "identity", "answer_data": [ "identity-master" ] }, { "id": "identity-q2", "text": "What work kind, deliverables, exclusions and design revisions define the current scope?", "kind": "definition", "answer_data": [ "identity-scope" ] }, { "id": "identity-q3", "text": "Which earlier undertaking or scope revision is superseded, split or related, and on whose recorded decision?", "kind": "lifecycle", "answer_data": [ "identity-lineage" ] } ], "data_elements": [ { "id": "identity-master", "name": "Work master identity", "description": "Opaque work identifier with issuing namespace; permit numbers are aliases, not a mandatory key.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "identity-scope", "name": "Scope baseline", "description": "Work kind, description, deliverables, exclusions, design references, revision and adoption profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "identity-lineage", "name": "Revision and undertaking lineage", "description": "Predecessor revision, related work identifiers, split or supersession rationale, decision issuer and effective time.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] } ], "artifacts": [ { "id": "identity-artifact", "name": "Scope baseline record", "description": "Versioned evidence for identity and scope. Retain issuer, scope, source reference, revision and access classification; an attachment alone is not verification.", "media_or_form": [ "application/json", "application/pdf" ], "serial": true, "identity_strategy": "Use the authoritative master-system identifier and issuer namespace first; separate logical record identity from immutable revision and content digest. Use a local opaque identifier only when no master identifier exists.", "source_refs": [ "SRC-001", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-site", "name": "Site and affected assets", "description": "Locate the undertaking and link assets it creates, alters or removes without claiming land rights or collapsing their identities.", "source_refs": [ "SRC-001", "SRC-006", "SRC-008" ], "findings": [ { "id": "finding-site", "name": "Site and affected assets", "description": "Locate the undertaking and link assets it creates, alters or removes without claiming land rights or collapsing their identities.", "source_refs": [ "SRC-001", "SRC-006", "SRC-008" ], "questions": [ { "id": "site-q1", "text": "Which sites, parcels, work zones and coordinate references delimit the affected locations?", "kind": "spatial", "answer_data": [ "site-locations" ] }, { "id": "site-q2", "text": "Which asset references are created, altered, retained or removed by each scope item?", "kind": "relationship", "answer_data": [ "site-assets" ] }, { "id": "site-q3", "text": "Which access constraints, surveys and uncertainties qualify the declared work area?", "kind": "constraint", "answer_data": [ "site-conditions" ] } ], "data_elements": [ { "id": "site-locations", "name": "Location references", "description": "Site and parcel identifiers, work-zone geometry reference, coordinate system, revision and confidence; no cadastral authority inferred.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-001", "SRC-006", "SRC-008" ] }, { "id": "site-assets", "name": "Affected asset links", "description": "Target identifier, target revision, relationship kind and scope item; planned targets may remain unresolved.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006", "SRC-008" ] }, { "id": "site-conditions", "name": "Site context evidence", "description": "Survey provenance, site access basis, existing-condition limitations, observation time and unresolved discrepancies.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-006", "SRC-008" ] } ], "artifacts": [ { "id": "site-artifact", "name": "Site and asset reference register", "description": "Versioned evidence for site and affected assets. Retain issuer, scope, source reference, revision and access classification; an attachment alone is not verification.", "media_or_form": [ "application/json", "application/pdf" ], "serial": true, "identity_strategy": "Use the authoritative master-system identifier and issuer namespace first; separate logical record identity from immutable revision and content digest. Use a local opaque identifier only when no master identifier exists.", "source_refs": [ "SRC-001", "SRC-006", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-governance", "name": "Responsibilities and authority", "description": "Role assignments and applicable external constraints.", "rationale": "Separate recording authority from permission to carry out physical work.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ], "layers": [ { "id": "layer-roles", "name": "Parties and responsibility", "description": "Role-specific responsibilities are time bounded and distinct from record ownership or property ownership.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ], "findings": [ { "id": "finding-roles", "name": "Parties and responsibility", "description": "Role-specific responsibilities are time bounded and distinct from record ownership or property ownership.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ], "questions": [ { "id": "roles-q1", "text": "Which role-based steward controls the work record and which parties perform, design or inspect the work?", "kind": "ownership", "answer_data": [ "roles-assignments" ] }, { "id": "roles-q2", "text": "What appointment or delegation evidence establishes each role for the relevant scope and interval?", "kind": "authority", "answer_data": [ "roles-mandates" ] }, { "id": "roles-q3", "text": "Who can view commercial, worker or safety-sensitive information, and which disclosures need a restricted projection?", "kind": "access", "answer_data": [ "roles-disclosure" ] } ], "data_elements": [ { "id": "roles-assignments", "name": "Role assignments", "description": "Record steward, client, contractor, designer and reviewer role references with scope and effective interval; no named company is prescribed as owner.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] }, { "id": "roles-mandates", "name": "Mandate evidence", "description": "Appointment issuer, scope, reference, expiry and verification state. Assignment alone does not establish competence.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] }, { "id": "roles-disclosure", "name": "Disclosure profile", "description": "Purpose, recipient role, permitted fields, redaction basis and audit obligations; default access denied.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "roles-artifact", "name": "Responsibility and access matrix", "description": "Versioned evidence for parties and responsibility. Retain issuer, scope, source reference, revision and access classification; an attachment alone is not verification.", "media_or_form": [ "application/json", "application/pdf" ], "serial": true, "identity_strategy": "Use the authoritative master-system identifier and issuer namespace first; separate logical record identity from immutable revision and content digest. Use a local opaque identifier only when no master identifier exists.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-authority", "name": "Permits and applicable conditions", "description": "Record applicability and external decision evidence separately from observed work status. Unknown is not permission, and unauthorized events remain recordable.", "source_refs": [ "SRC-006", "SRC-003" ], "findings": [ { "id": "finding-authority", "name": "Permits and applicable conditions", "description": "Record applicability and external decision evidence separately from observed work status. Unknown is not permission, and unauthorized events remain recordable.", "source_refs": [ "SRC-006", "SRC-003" ], "questions": [ { "id": "authority-q1", "text": "Which jurisdiction, contract and work profile determine whether each permit, notification or approval is required?", "kind": "requirement", "answer_data": [ "authority-applicability" ] }, { "id": "authority-q2", "text": "Which external decisions and conditions apply to which work portions and effective dates?", "kind": "authority", "answer_data": [ "authority-decisions" ] }, { "id": "authority-q3", "text": "How are expired, suspended, disputed, missing or exceeded authorizations recorded without hiding actual work?", "kind": "exception", "answer_data": [ "authority-exceptions" ] } ], "data_elements": [ { "id": "authority-applicability", "name": "Authority applicability assessment", "description": "Rule and jurisdiction references, assessor, assessed time, work scope and required, not-required or unknown state with reasons.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-006", "SRC-003" ] }, { "id": "authority-decisions", "name": "Authority decision links", "description": "Issuer, decision identifier and revision, authorized scope, effective interval, conditions, verification state and revocation links.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-003" ] }, { "id": "authority-exceptions", "name": "Authority exceptions", "description": "Observed noncompliance, disputed applicability, unresolved checks and escalation references; recording never authorizes continuation.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-003" ] } ], "artifacts": [ { "id": "authority-artifact", "name": "Authorization evidence register", "description": "Versioned evidence for permits and applicable conditions. Retain issuer, scope, source reference, revision and access classification; an attachment alone is not verification.", "media_or_form": [ "application/json", "application/pdf" ], "serial": true, "identity_strategy": "Use the authoritative master-system identifier and issuer namespace first; separate logical record identity from immutable revision and content digest. Use a local opaque identifier only when no master identifier exists.", "source_refs": [ "SRC-006", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-planning", "name": "Plan and change control", "description": "Baseline sequence and revision decisions.", "rationale": "Keep forecasts, observations and authority to change separate.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007" ], "layers": [ { "id": "layer-schedule", "name": "Breakdown and scheduling", "description": "Represent work portions, task references, dependencies and distinct baseline and forecast times. No universal phase ordering is assumed.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ], "findings": [ { "id": "finding-schedule", "name": "Breakdown and scheduling", "description": "Represent work portions, task references, dependencies and distinct baseline and forecast times. No universal phase ordering is assumed.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ], "questions": [ { "id": "schedule-q1", "text": "Which work portions, task masters and dependency relationships form the adopted breakdown?", "kind": "composition", "answer_data": [ "schedule-breakdown" ] }, { "id": "schedule-q2", "text": "Which baseline, forecast, actual intervals and calendar references apply to each scheduled portion?", "kind": "temporal", "answer_data": [ "schedule-times" ] }, { "id": "schedule-q3", "text": "What evidence and role can release a recorded hold point, and how is an unresolved dependency shown?", "kind": "process", "answer_data": [ "schedule-gates" ] } ], "data_elements": [ { "id": "schedule-breakdown", "name": "Work breakdown references", "description": "Stable portion and task identifiers, parent scope and dependency type; prevent cycles and double counting in the adopted profile.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "schedule-times", "name": "Schedule versions", "description": "Baseline and forecast identifiers, task links, start and finish, duration basis, timezone and calendar reference; actual times belong to observations.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "schedule-gates", "name": "Hold point register", "description": "Prerequisite evidence, responsible reviewer, release record and unresolved state; local data changes do not release site operations.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] } ], "artifacts": [ { "id": "schedule-artifact", "name": "Schedule baseline and hold register", "description": "Versioned evidence for breakdown and scheduling. Retain issuer, scope, source reference, revision and access classification; an attachment alone is not verification.", "media_or_form": [ "application/json", "application/pdf" ], "serial": true, "identity_strategy": "Use the authoritative master-system identifier and issuer namespace first; separate logical record identity from immutable revision and content digest. Use a local opaque identifier only when no master identifier exists.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-changes", "name": "Scope changes and discontinuity", "description": "Record proposed and authorized changes, suspension, restart or cancellation without overwriting prior baselines.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ], "findings": [ { "id": "finding-changes", "name": "Scope changes and discontinuity", "description": "Record proposed and authorized changes, suspension, restart or cancellation without overwriting prior baselines.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ], "questions": [ { "id": "changes-q1", "text": "Which proposal changes scope, design, time or conditions relative to a named baseline?", "kind": "state", "answer_data": [ "changes-proposal" ] }, { "id": "changes-q2", "text": "Who decided the change and what external permit, contract or design approvals remain unresolved?", "kind": "decision", "answer_data": [ "changes-decision" ] }, { "id": "changes-q3", "text": "Which suspension, restart or cancellation assertion affected which portion and interval?", "kind": "event", "answer_data": [ "changes-interruptions" ] } ], "data_elements": [ { "id": "changes-proposal", "name": "Change proposal", "description": "Proposal ID, old baseline, requested delta, impacts and supporting evidence; proposal is not approval.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "changes-decision", "name": "Change disposition", "description": "Disposition, decision role, effective time, external authority references, resultant baseline and unresolved approvals.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "changes-interruptions", "name": "Interruption history", "description": "Affected portion, asserted state, observation and effective times, reason, issuer, source and resume prerequisite references.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "changes-artifact", "name": "Change and interruption log", "description": "Versioned evidence for scope changes and discontinuity. Retain issuer, scope, source reference, revision and access classification; an attachment alone is not verification.", "media_or_form": [ "application/json", "application/pdf" ], "serial": true, "identity_strategy": "Use the authoritative master-system identifier and issuer namespace first; separate logical record identity from immutable revision and content digest. Use a local opaque identifier only when no master identifier exists.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-execution", "name": "Execution observations", "description": "Physical progress evidence and safety governance context.", "rationale": "Avoid treating a schedule, photograph or percentage as certified completion.", "source_refs": [ "SRC-003", "SRC-005", "SRC-007" ], "layers": [ { "id": "layer-progress", "name": "Measured and reported progress", "description": "Progress is an attributed observation against a baseline and a defined quantity or milestone basis. Forecast, payment and acceptance are distinct.", "source_refs": [ "SRC-005", "SRC-001", "SRC-007" ], "findings": [ { "id": "finding-progress", "name": "Measured and reported progress", "description": "Progress is an attributed observation against a baseline and a defined quantity or milestone basis. Forecast, payment and acceptance are distinct.", "source_refs": [ "SRC-005", "SRC-001", "SRC-007" ], "questions": [ { "id": "progress-q1", "text": "What was observed for each work portion, by whom, when and using which method?", "kind": "provenance", "answer_data": [ "progress-observation" ] }, { "id": "progress-q2", "text": "What numerator, denominator, units, baseline and uncertainty support the reported quantity or percentage?", "kind": "measurement", "answer_data": [ "progress-quantity" ] }, { "id": "progress-q3", "text": "How are conflicting, stale, corrected or unverified reports retained and evaluated?", "kind": "quality", "answer_data": [ "progress-assessment" ] } ], "data_elements": [ { "id": "progress-observation", "name": "Progress observation", "description": "Observer, work portion, observation time, recorded time, evidence links and method; images are supporting evidence only.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-001", "SRC-007" ] }, { "id": "progress-quantity", "name": "Progress measurement basis", "description": "Numerator, denominator, units, baseline, tolerance or uncertainty, measurement conditions and aggregation weights; unknown values stay unknown.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-001", "SRC-007" ] }, { "id": "progress-assessment", "name": "Observation assessment", "description": "Review status, reviewer, discrepancy, correction link and explanation; revisions may reduce progress and do not trigger payment.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-001", "SRC-007" ] } ], "artifacts": [ { "id": "progress-artifact", "name": "Progress evidence statement", "description": "Versioned evidence for measured and reported progress. Retain issuer, scope, source reference, revision and access classification; an attachment alone is not verification.", "media_or_form": [ "application/json", "application/pdf" ], "serial": true, "identity_strategy": "Use the authoritative master-system identifier and issuer namespace first; separate logical record identity from immutable revision and content digest. Use a local opaque identifier only when no master identifier exists.", "source_refs": [ "SRC-005", "SRC-001", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-safety", "name": "Safety and site constraints", "description": "Retain policy-level hazard, plan, inspection and incident references. No generated instructions for dangerous site operations are included.", "source_refs": [ "SRC-003", "SRC-007" ], "findings": [ { "id": "finding-safety", "name": "Safety and site constraints", "description": "Retain policy-level hazard, plan, inspection and incident references. No generated instructions for dangerous site operations are included.", "source_refs": [ "SRC-003", "SRC-007" ], "questions": [ { "id": "safety-q1", "text": "Which safety plan revision, accountable roles and hazard assessments apply to the present work scope?", "kind": "security", "answer_data": [ "safety-plan" ] }, { "id": "safety-q2", "text": "Which site constraints or inspection findings affect readiness, and what competent review is outstanding?", "kind": "constraint", "answer_data": [ "safety-readiness" ] }, { "id": "safety-q3", "text": "Which restricted incident or stop-work references explain the current recorded constraints?", "kind": "exception", "answer_data": [ "safety-incidents" ] } ], "data_elements": [ { "id": "safety-plan", "name": "Safety governance references", "description": "Plan identifier and revision, scope, accountable role, review date and hazard assessment links; absent evidence is explicitly unresolved.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-007" ] }, { "id": "safety-readiness", "name": "Readiness assertions", "description": "Inspection reference, scope, condition, competent reviewer, observation time and expiry or reassessment trigger; no automated safety clearance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-007" ] }, { "id": "safety-incidents", "name": "Incident and safety restriction links", "description": "External incident or order identifiers, access class and recorded work effects; operational response remains with authorized personnel.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-007" ] } ], "artifacts": [ { "id": "safety-artifact", "name": "Safety governance evidence index", "description": "Versioned evidence for safety and site constraints. Retain issuer, scope, source reference, revision and access classification; an attachment alone is not verification.", "media_or_form": [ "application/json", "application/pdf" ], "serial": true, "identity_strategy": "Use the authoritative master-system identifier and issuer namespace first; separate logical record identity from immutable revision and content digest. Use a local opaque identifier only when no master identifier exists.", "source_refs": [ "SRC-003", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-materials", "name": "Materials and environmental interfaces", "description": "Work-specific material trace and disposition evidence.", "rationale": "Connect installation and waste evidence without taking over material, inventory or environmental masters.", "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ], "layers": [ { "id": "layer-materials", "name": "Material and installed-item trace", "description": "Link material batches and installed or removed items to work portions, specifications and review evidence. Resource consumption is distinct from task identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "findings": [ { "id": "finding-materials", "name": "Material and installed-item trace", "description": "Link material batches and installed or removed items to work portions, specifications and review evidence. Resource consumption is distinct from task identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "questions": [ { "id": "materials-q1", "text": "Which material or component identifiers and batches are linked to the affected work portions?", "kind": "identity", "answer_data": [ "materials-items" ] }, { "id": "materials-q2", "text": "Which specification revision and inspection evidence support the recorded use or rejection?", "kind": "validation", "answer_data": [ "materials-conformity" ] }, { "id": "materials-q3", "text": "Which substitutions, unknown origins or unresolved trace gaps require a disposition?", "kind": "exception", "answer_data": [ "materials-substitutions" ] } ], "data_elements": [ { "id": "materials-items", "name": "Material and component links", "description": "External item or batch master, work portion, installed or removed relation, quantity and units with observation basis.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "materials-conformity", "name": "Material evidence links", "description": "Specification revision, submittal and inspection references, acceptance scope and reviewer; receipt does not establish fitness.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "materials-substitutions", "name": "Substitution and trace exceptions", "description": "Proposed replacement, original reference, authority evidence, status and unresolved origin or inspection gaps.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "materials-artifact", "name": "Material trace register", "description": "Versioned evidence for material and installed-item trace. Retain issuer, scope, source reference, revision and access classification; an attachment alone is not verification.", "media_or_form": [ "application/json", "application/pdf" ], "serial": true, "identity_strategy": "Use the authoritative master-system identifier and issuer namespace first; separate logical record identity from immutable revision and content digest. Use a local opaque identifier only when no master identifier exists.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-environment", "name": "Disposition and environmental evidence", "description": "Distinguish planned reuse or recycling from evidenced disposition. Environmental and hazardous-material obligations require an adopted specialist profile.", "source_refs": [ "SRC-008", "SRC-006" ], "findings": [ { "id": "finding-environment", "name": "Disposition and environmental evidence", "description": "Distinguish planned reuse or recycling from evidenced disposition. Environmental and hazardous-material obligations require an adopted specialist profile.", "source_refs": [ "SRC-008", "SRC-006" ], "questions": [ { "id": "environment-q1", "text": "Which removed or surplus material streams have recorded quantities, units and classification evidence?", "kind": "classification", "answer_data": [ "environment-streams" ] }, { "id": "environment-q2", "text": "What destination, transfer reference and receipt evidence support the claimed disposition?", "kind": "evidence", "answer_data": [ "environment-transfers" ] }, { "id": "environment-q3", "text": "Which environmental conditions or unknown classifications remain unresolved before a compliance claim?", "kind": "requirement", "answer_data": [ "environment-conditions" ] } ], "data_elements": [ { "id": "environment-streams", "name": "Material stream observations", "description": "Stream ID, work portion, classification system and version, quantity, units, method and uncertainty; no hazardous handling instructions.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008", "SRC-006" ] }, { "id": "environment-transfers", "name": "Disposition evidence", "description": "Reuse, recycling, disposal or unknown destination assertion, transfer reference, recipient and receipt state; avoid double counting.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008", "SRC-006" ] }, { "id": "environment-conditions", "name": "Environmental review conditions", "description": "Applicable profile references, reviewer, conditions, expiry and unresolved classification or destination evidence; no generic compliance certification.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008", "SRC-006" ] } ], "artifacts": [ { "id": "environment-artifact", "name": "Material disposition record", "description": "Versioned evidence for disposition and environmental evidence. Retain issuer, scope, source reference, revision and access classification; an attachment alone is not verification.", "media_or_form": [ "application/json", "application/pdf" ], "serial": true, "identity_strategy": "Use the authoritative master-system identifier and issuer namespace first; separate logical record identity from immutable revision and content digest. Use a local opaque identifier only when no master identifier exists.", "source_refs": [ "SRC-008", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-assurance", "name": "Inspection and nonconformity", "description": "Scope-specific quality assessment and correction evidence.", "rationale": "Keep examination results, remedial actions and acceptance decisions distinct.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ], "layers": [ { "id": "layer-inspection", "name": "Inspection and test evidence", "description": "Examinations refer to a specific scope and requirement revision; results do not automatically accept work.", "source_refs": [ "SRC-004", "SRC-003" ], "findings": [ { "id": "finding-inspection", "name": "Inspection and test evidence", "description": "Examinations refer to a specific scope and requirement revision; results do not automatically accept work.", "source_refs": [ "SRC-004", "SRC-003" ], "questions": [ { "id": "inspection-q1", "text": "Which work portion and requirement revision did each inspection or test examine?", "kind": "definition", "answer_data": [ "inspection-scope" ] }, { "id": "inspection-q2", "text": "Who performed and reviewed it, using which method, conditions and evidence?", "kind": "evidence", "answer_data": [ "inspection-evidence" ] }, { "id": "inspection-q3", "text": "What verdict, limitations, outstanding tests and hold-point implications were recorded?", "kind": "validation", "answer_data": [ "inspection-verdict" ] } ], "data_elements": [ { "id": "inspection-scope", "name": "Examination scope", "description": "Inspection or test master reference, work portion, sampled population, requirement ID and revision.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-003" ] }, { "id": "inspection-evidence", "name": "Examination evidence", "description": "Examiner and competence reference, method, conditions, observation time, report and provenance links.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-003" ] }, { "id": "inspection-verdict", "name": "Scoped verdict", "description": "Pass, fail, inconclusive or not-examined state, limitations, reviewer and pending follow-up; no inference beyond examined scope.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-003" ] } ], "artifacts": [ { "id": "inspection-artifact", "name": "Inspection evidence register", "description": "Versioned evidence for inspection and test evidence. Retain issuer, scope, source reference, revision and access classification; an attachment alone is not verification.", "media_or_form": [ "application/json", "application/pdf" ], "serial": true, "identity_strategy": "Use the authoritative master-system identifier and issuer namespace first; separate logical record identity from immutable revision and content digest. Use a local opaque identifier only when no master identifier exists.", "source_refs": [ "SRC-004", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-defects", "name": "Defects and correction", "description": "A reported defect may originate outside a formal inspection. Correction assertions require separate verification and may be reopened.", "source_refs": [ "SRC-004", "SRC-007" ], "findings": [ { "id": "finding-defects", "name": "Defects and correction", "description": "A reported defect may originate outside a formal inspection. Correction assertions require separate verification and may be reopened.", "source_refs": [ "SRC-004", "SRC-007" ], "questions": [ { "id": "defects-q1", "text": "Which observed nonconformity, location and requirement discrepancy define the defect report?", "kind": "quality", "answer_data": [ "defects-report" ] }, { "id": "defects-q2", "text": "Which responsible role and correction evidence address the reported defect?", "kind": "process", "answer_data": [ "defects-correction" ] }, { "id": "defects-q3", "text": "What verification, residual limitation or contrary evidence supports closure or reopening?", "kind": "lifecycle", "answer_data": [ "defects-verification" ] } ], "data_elements": [ { "id": "defects-report", "name": "Nonconformity report", "description": "Defect identifier, work portion, asset location, reporter, source, detection time, requirement reference and assessed consequence; inspection link optional.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-007" ] }, { "id": "defects-correction", "name": "Correction history", "description": "Assigned role, planned and reported action reference, evidence, time and disposition; no engineering repair procedure generated.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-007" ] }, { "id": "defects-verification", "name": "Closure and reopening review", "description": "Reviewer, examined scope, outcome, residual risk, waiver authority reference and reopening evidence; correction is not automatic closure.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-007" ] } ], "artifacts": [ { "id": "defects-artifact", "name": "Defect and correction history", "description": "Versioned evidence for defects and correction. Retain issuer, scope, source reference, revision and access classification; an attachment alone is not verification.", "media_or_form": [ "application/json", "application/pdf" ], "serial": true, "identity_strategy": "Use the authoritative master-system identifier and issuer namespace first; separate logical record identity from immutable revision and content digest. Use a local opaque identifier only when no master identifier exists.", "source_refs": [ "SRC-004", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-completion", "name": "Outcomes and record continuity", "description": "Partial or final acceptance and controlled handover.", "rationale": "Preserve work history while linking distinct asset and operational records.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ], "layers": [ { "id": "layer-acceptance", "name": "Acceptance and residual obligations", "description": "Allow zero or many scoped outcome records. Contract acceptance, occupancy authorization, commissioning, payment and ownership transfer have separate evidence and masters.", "source_refs": [ "SRC-004", "SRC-006" ], "findings": [ { "id": "finding-acceptance", "name": "Acceptance and residual obligations", "description": "Allow zero or many scoped outcome records. Contract acceptance, occupancy authorization, commissioning, payment and ownership transfer have separate evidence and masters.", "source_refs": [ "SRC-004", "SRC-006" ], "questions": [ { "id": "acceptance-q1", "text": "Which work portion was accepted, rejected or left pending under which decision and effective date?", "kind": "decision", "answer_data": [ "acceptance-outcomes" ] }, { "id": "acceptance-q2", "text": "Which reservations, residual obligations or separately authorized operational uses qualify that outcome?", "kind": "constraint", "answer_data": [ "acceptance-reservations" ] }, { "id": "acceptance-q3", "text": "Which later claim, latent defect or correction changes the recorded assessment without erasing the original decision?", "kind": "temporal", "answer_data": [ "acceptance-later" ] } ], "data_elements": [ { "id": "acceptance-outcomes", "name": "Scoped acceptance decisions", "description": "Decision master, issuer role, work scope, outcome, effective time, contract basis and evidence verification; partial and repeated decisions supported.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "acceptance-reservations", "name": "Residual obligations", "description": "Outstanding items, responsibility, dates, separate operational authorization references and unresolved matters; dates derive from the adopted profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "acceptance-later", "name": "Subsequent outcome evidence", "description": "Later defect or dispute reference, original decision link, asserted impact, issuer and observation time; local record cannot rescind legal effects.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "acceptance-artifact", "name": "Acceptance and reservation register", "description": "Versioned evidence for acceptance and residual obligations. Retain issuer, scope, source reference, revision and access classification; an attachment alone is not verification.", "media_or_form": [ "application/json", "application/pdf" ], "serial": true, "identity_strategy": "Use the authoritative master-system identifier and issuer namespace first; separate logical record identity from immutable revision and content digest. Use a local opaque identifier only when no master identifier exists.", "source_refs": [ "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-handover", "name": "Handover and retained history", "description": "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.", "source_refs": [ "SRC-003", "SRC-007", "SRC-001" ], "findings": [ { "id": "finding-handover", "name": "Handover and retained history", "description": "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.", "source_refs": [ "SRC-003", "SRC-007", "SRC-001" ], "questions": [ { "id": "handover-q1", "text": "Which asset, operational recipient and required information profile define the handover scope?", "kind": "relationship", "answer_data": [ "handover-recipient" ] }, { "id": "handover-q2", "text": "Which exact artifact revisions, formats, missing items and recipient acknowledgments constitute the package?", "kind": "interoperability", "answer_data": [ "handover-package" ] }, { "id": "handover-q3", "text": "Which retention, access-transfer and lawful disposal rules govern the completed work history?", "kind": "retention", "answer_data": [ "handover-retention" ] } ], "data_elements": [ { "id": "handover-recipient", "name": "Handover recipient and scope", "description": "Asset references, recipient role and namespace, information requirements and handover portion; receipt is not asset commissioning.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-007", "SRC-001" ] }, { "id": "handover-package", "name": "Handover manifest", "description": "Artifact IDs, revisions, digests, formats, restricted-link handling, missing items, dispatch and receipt records; completeness separately reviewed.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-007", "SRC-001" ] }, { "id": "handover-retention", "name": "Work history retention profile", "description": "Record classes, applicable retention basis, review trigger, holds, authorized deletion and minimal tombstone policy; no perpetual personal-data retention assumed.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-007", "SRC-001" ] } ], "artifacts": [ { "id": "handover-artifact", "name": "Handover manifest and retention decision", "description": "Versioned evidence for handover and retained history. Retain issuer, scope, source reference, revision and access classification; an attachment alone is not verification.", "media_or_form": [ "application/json", "application/pdf" ], "serial": true, "identity_strategy": "Use the authoritative master-system identifier and issuer namespace first; separate logical record identity from immutable revision and content digest. Use a local opaque identifier only when no master identifier exists.", "source_refs": [ "SRC-003", "SRC-007", "SRC-001" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "function-register-work", "name": "Register work identity", "description": "Proposed, unimplemented local operation. Create a proposed local undertaking record with scope and separately mastered context.", "inputs": [ "Namespace and work identifier", "Scope and steward role", "Site or unresolved location references" ], "outputs": [ "Scoped draft identity", "Duplicate or unresolved-identity report" ], "preconditions": [ "Record steward authorized for this namespace", "Identity collision check completed" ], "effects": [ "Creates local draft only; does not authorize construction" ], "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "function-revise-baseline", "name": "Record baseline revision", "description": "Proposed, unimplemented local operation. Preserve a previous baseline and record a new decision-backed revision.", "inputs": [ "Expected current revision", "Proposed delta", "Decision and external approval references" ], "outputs": [ "New baseline revision or refusal", "Unresolved approval list" ], "preconditions": [ "Authorized recorder and current revision match", "Decision scope and evidence reviewed" ], "effects": [ "Appends revision and lineage; does not amend contracts or permits" ], "source_refs": [ "SRC-002", "SRC-005", "SRC-007" ] }, { "id": "function-record-progress", "name": "Record progress evidence", "description": "Proposed, unimplemented local operation. Capture an observation and assess its measurement basis without certifying completion.", "inputs": [ "Work portion and baseline", "Observation, quantity and method", "Evidence and observer" ], "outputs": [ "Attributed observation or refusal", "Missing-basis and contradiction flags" ], "preconditions": [ "Recorder has scope access", "Units, denominator and observation time supplied or explicitly unknown" ], "effects": [ "Appends observation and review state; does not trigger payment or release a hold point" ], "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "function-link-assurance", "name": "Link inspection or correction review", "description": "Proposed, unimplemented local operation. Attach scoped evidence and record a qualified review state.", "inputs": [ "Inspection or defect reference", "Requirement revision", "Reviewer and verdict evidence" ], "outputs": [ "Scoped assessment or refusal", "Remaining defect and examination gaps" ], "preconditions": [ "Reviewer authorized for record scope", "Evidence source and revision resolvable or explicitly unresolved" ], "effects": [ "Adds local assessment; no engineering certification, site instruction or automatic acceptance" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "function-record-outcome", "name": "Record an external outcome", "description": "Proposed, unimplemented local operation. Record a partial acceptance, suspension or other externally issued decision as evidence.", "inputs": [ "Decision issuer and identifier", "Scope and effective time", "Reservations and current record revision" ], "outputs": [ "Attributed decision record or refusal", "Conflicting authority report" ], "preconditions": [ "Authorized recorder", "Decision evidence and issuer scope checked; unverified claims labeled" ], "effects": [ "Preserves assertion history; does not issue, revoke or execute the external decision" ], "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "function-prepare-handover", "name": "Prepare restricted handover projection", "description": "Proposed, unimplemented local operation. Build a local review package of permitted artifact revisions and outstanding items.", "inputs": [ "Recipient role and purpose", "Artifact revision manifest", "Handover and disclosure profiles" ], "outputs": [ "Local manifest or refusal", "Missing and restricted item report" ], "preconditions": [ "Recipient-specific access evaluated", "No unresolved access expansion", "Current manifest revision known" ], "effects": [ "Creates local projection only; no transmission, rights transfer or asset commissioning" ], "source_refs": [ "SRC-003", "SRC-007" ] } ], "composition": [ { "target": "WM-ACT-005", "relation": "REFERENCE", "purpose": "Optional project governance master; no inherited project completeness claim.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "WM-ACT-006", "relation": "REFERENCE", "purpose": "Execution task references and breakdown mappings; binding revision must be chosen by adopter.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "WM-BLT-001", "relation": "REFERENCE", "purpose": "Building or structure produced, altered or removed; independently mastered identity.", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "target": "WM-BLT-003", "relation": "REFERENCE", "purpose": "Infrastructure network affected by the undertaking; no automatic operational state mutation.", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "target": "WM-PLC-002", "relation": "REFERENCE", "purpose": "Site parcels by authoritative external reference without asserting title or access rights.", "required": false, "source_refs": [ "SRC-006" ] }, { "target": "WM-POL-004", "relation": "REFERENCE", "purpose": "Optional permits and authorization decisions; absence must be qualified, not interpreted as permission.", "required": false, "source_refs": [ "SRC-006" ] }, { "target": "WM-ORG-001", "relation": "REFERENCE", "purpose": "Role-assigned organizations remain external masters with local appointment evidence.", "required": false, "source_refs": [ "SRC-003", "SRC-006" ] }, { "target": "WM-ACT-013", "relation": "REFERENCE", "purpose": "Maintenance context that may commission a construction undertaking; avoid duplicate work identity.", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "target": "WM-ACT-019", "relation": "REFERENCE", "purpose": "Restricted incident references and work-status effects; response stays external.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "IFC 4.3.2.0 IfcTask and IfcWorkSchedule", "relation": "ALIGN", "purpose": "Conceptual mapping of work portions, schedules and product links only; no IFC conformity or whole-root equivalence claimed.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "PROV-O 2013-04-30", "relation": "ALIGN", "purpose": "Conceptual evidence attribution and derivation mapping; not a trust or authority proof.", "required": false, "source_refs": [ "SRC-007" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Name a role-based work record steward, delegated scope and contact mechanism; no prescribed company owner.", "Declare jurisdiction, work classification, schema version and required external reference bindings.", "Provide artifact storage, interfaces, authorized processes, disclosure and retention profiles.", "Preserve the independent-review, source/version, profile and executable-conformance holds." ], "namespace_guidance": "Use a steward-controlled namespace with immutable work and portion identifiers. Keep permit, project, task, asset, artifact and revision namespaces distinct; aliases never establish identity by themselves.", "registry_links": [ "vr.wm-blt-007", "WM-ACT-005", "WM-ACT-006", "WM-POL-004", "WM-BLT-001", "WM-BLT-003" ] }, "canon_and_patch": { "canonicalization_rules": [ "Research distribution remains noncanonical and reviewable-draft under the single-provider waiver.", "Canonical local serialization preserves stable IDs, units, source revisions and unknown values; no normalization may turn an assertion into a verified fact." ], "patch_rules": [ "Require expected revision, actor, reason and source for every patch; record effective and observation times separately.", "Append corrections and supersession links; refuse silent changes to accepted decisions or baseline history." ], "compatibility_rules": [ "Version schema, status vocabulary and adopter profile independently; migration must state any lossy projection.", "Pin IFC mapping, task bindings and authority profiles before executable use; wildcard legacy imports are not admitted." ] }, "artifact_rules": { "identity_priority": [ "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" ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and an explicit UTC offset. Distinguish observed, recorded, issued and effective times; preserve date-only precision without invented instants.", "serial_naming_rule": "Serial artifacts use stable work ID, artifact role and immutable revision token; timestamps are metadata and never the sole identity.", "integrity_rule": "Store media type, digest algorithm and digest with source and revision; verify bytes on retrieval and retain a discrepancy record. A hash establishes byte equality only, not truth or authority." }, "policies": [ "All data structures, lifecycle states and functions are proposed research design; an adopter must supply executable schemas and review authority.", "Record unauthorized, unsafe or disputed observations honestly while flagging the exception; never suppress facts to satisfy a readiness rule.", "Safety-critical decisions and hazardous operations remain with qualified personnel under applicable policies; no operational instructions or actuation are provided.", "No universal permit, notification, inspection, acceptance, occupancy or retention rule is inferred from the example jurisdictions.", "Minimize worker and commercial data; public views require an approved field-level projection and lawful purpose.", "Source provenance is not an endorsement of a claim; separate reported, reviewed, disputed and unknown states." ], "crud": { "read": [ "Resolve scope, recipient role and purpose before retrieving any artifact; redact sensitive metadata as well as content." ], "create": [ "Require authorized steward, unique namespace identity and explicit work scope; allow draft and unknown authority states." ], "update": [ "Require optimistic concurrency and evidence-backed revision; preserve contradictory observations and their disposition." ], "delete": [ "Retire work records through a referenced decision and retention review; check legal and contractual holds.", "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." ] }, "roles": [ { "name": "Work record steward", "responsibilities": [ "Own namespace and record continuity; maintain scope and adopter profiles." ] }, { "name": "Authorized recorder", "responsibilities": [ "Record evidence with source, time and uncertainty; cannot issue external approvals." ] }, { "name": "Construction coordinator", "responsibilities": [ "Maintain plan and responsibility references; escalate unresolved authority or safety constraints." ] }, { "name": "Qualified reviewer", "responsibilities": [ "Review only within appointed competence and scope; distinguish review from acceptance authority." ] }, { "name": "Acceptance decision custodian", "responsibilities": [ "Link issuer decisions and reservations without creating legal effects." ] }, { "name": "Information custodian", "responsibilities": [ "Apply access, handover, integrity and lawful retention controls." ] } ], "access": { "default_rule": "Deny by default; grant purpose-limited role access to the minimum work scope, fields and artifact revisions.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Approved public projection may disclose work scope and status while suppressing personal, commercial and sensitive site details.", "Emergency access requires the applicable authorized policy, minimum scope and subsequent audit; no universal access bypass is defined." ], "audit_requirements": [ "Record actor, role, purpose, policy revision, accessed scope and outcome for reads and writes.", "Log redactions, exports, denied requests, evidence changes and retention dispositions without duplicating sensitive payloads." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL", "Review state", "Publication holds" ], "read_order": [ "AGENTS.md and owner Dimension policy", "spec.yaml scope, holds and source references", "Pinned neighbor schemas and local adoption profile", "Current work revision and authorized evidence" ] } }, "coverage": { "claim": "Source-grounded proposed structure for one persistent construction undertaking, reconciled with legacy U6 and checked in a separate local no-tools self-audit. Selected Great Britain guidance, US federal contract clauses and exchange vocabularies inform the design; independent review, source/version verification, adoption profiles and executable conformance remain holds. Noncanonical reviewable draft only.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Persistent undertaking identity and scope lineage distinct from task, permit and asset." }, { "dimension": "lifecycle", "status": "covered", "notes": "Planned, observed, suspended, partial outcome and retained history assertions; transitions require a local profile." }, { "dimension": "relationships", "status": "covered", "notes": "Optional referenced masters and conceptual alignments, without forced instantiation of neighbors." }, { "dimension": "temporal", "status": "covered", "notes": "Baseline, forecast, observed, recorded and effective times remain separate." }, { "dimension": "provenance", "status": "covered", "notes": "Attributed source revisions, evidence links and correction chains; no truth certification." }, { "dimension": "ownership", "status": "covered", "notes": "Role-based record stewardship differs from property ownership, appointments and legal authority." }, { "dimension": "validation", "status": "covered", "notes": "Source-grounded research schema validation; runtime instance validation remains incomplete." }, { "dimension": "access", "status": "covered", "notes": "Least disclosure and restricted safety, worker and commercial artifacts." }, { "dimension": "interoperability", "status": "gap", "notes": "Conceptual IFC and PROV-O links only; no round-trip fixtures or executable mappings." }, { "dimension": "direct properties", "status": "covered", "notes": "Work kind, scoped sites, dates and state; quantities belong to observations and linked assets, not intrinsic dimensions of an abstract undertaking." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Scope and evidence distinguish undertaking from asset; recognition by photograph alone cannot establish identity or completion." }, { "dimension": "capabilities and actions", "status": "covered", "notes": "Six proposed local functions with preconditions and effects; physical and legal actions remain external." }, { "dimension": "materials and environment", "status": "covered", "notes": "Trace, disposition and evidence gaps; no environmental compliance claim." }, { "dimension": "regional coverage", "status": "gap", "notes": "Selected Great Britain guidance and US federal contract examples; global, local and sector profiles unverified." } ], "known_omissions": [ "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." ], "conflicts": [], "regional_assumptions": [ "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." ], "adversarial_checks": [ "Can unauthorized commencement be recorded without authorizing continuation? Yes: observation and authority status remain separate.", "Can a demolished asset or partially accepted portion coexist with a retained work record? Yes: identifiers and scoped outcome records remain distinct.", "Can a progress revision decrease and a corrected defect reopen? Yes: provenance and correction history preserve disagreement.", "Does a missing permit mean not required? No: applicability, pending, unknown and violation are separate assertions.", "Does artifact receipt prove handover completeness or permit occupancy? No: acknowledgment, review and external operational authorization remain separate." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "entity", "status": "accepted", "rationale": "A work keeps a stable identity across plans, observations and scoped outcomes. Its temporary execution does not make its record a single event or turn it into the physical product. External project, task, permit and asset masters preserve separate authority. The registry standalone-mm value is a catalogue class, not a research subject-kind enum." }, "decisions": [ { "concept": "Undertaking identity and project boundary", "disposition": "accepted", "rationale": "One persistent construction work entity owns scoped execution evidence; optional project context does not duplicate portfolio or contract governance." }, { "concept": "Legacy product graduation", "disposition": "rejected", "rationale": "Assets remain separately identified before and after work acceptance, including alteration and demolition. No acceptance function changes the class or operating state of an asset." }, { "concept": "Site and maintenance classification", "disposition": "qualified", "rationale": "Location references do not establish rights. Maintenance may commission construction work, and permit presence alone cannot determine the boundary; the adopting profile must explain classification." }, { "concept": "Roles and applicable authority", "disposition": "accepted with profile dependency", "rationale": "Record ownership, competence and external decision authority remain distinct. Missing or disputed authorizations do not prevent truthful observation records or authorize continuation." }, { "concept": "Optional composition references", "disposition": "accepted as candidates", "rationale": "No registry relationship rows were found. All eleven links are optional references or conceptual alignments, with operational binding and profile requirements explicitly deferred." }, { "concept": "Plans and change decisions", "disposition": "separated", "rationale": "Baseline, forecast and actual observations retain different meanings. Local revision recording does not amend a contract, grant a permit or release a site hold point." }, { "concept": "Progress evidence and physical properties", "disposition": "qualified", "rationale": "Quantities require a baseline and measurement basis and may decrease after correction. They describe observations or linked assets, not intrinsic physical dimensions of the abstract undertaking." }, { "concept": "Safety and hazardous activities", "disposition": "bounded", "rationale": "The draft records policy, competent-review and incident references only. It supplies no dangerous operational procedures and no automated safety or site-control authority." }, { "concept": "Materials and environmental claims", "disposition": "accepted as proposed evidence design", "rationale": "Material trace and disposition fields are local design choices, not universal requirements derived from guidance. Receipt, classification and destination uncertainty remain reviewable." }, { "concept": "Inspection and defect lifecycle", "disposition": "accepted", "rationale": "Inspection verdicts apply to scoped requirements. Defect origin need not be a formal inspection, and correction assertions remain separate from verified closure or reopening." }, { "concept": "Partial acceptance and handover", "disposition": "accepted with qualifications", "rationale": "Zero or many outcome records replace the legacy single acceptance rule. Acceptance, occupancy, commissioning, payment, ownership and package receipt remain separate assertions." }, { "concept": "Local function effects", "disposition": "accepted as unimplemented proposals", "rationale": "All six functions record or prepare local evidence with authority and scope checks. They do not transmit packages, operate equipment or issue or revoke externally effective decisions." }, { "concept": "Identity, privacy and retention service rules", "disposition": "accepted with adoption dependency", "rationale": "Master identity, revision and digest are distinct. Retention review and lawful payload disposal qualify historical continuity and prevent automatic perpetual retention of personal data." }, { "concept": "Source and legacy conformance claims", "disposition": "limited and held", "rationale": "Eight primary pages support selected conceptual distinctions. Browser readings do not establish current law or measured direct HTTP success. Unread ISO clauses and legacy wildcard imports cannot support conformance." }, { "concept": "Executable schemas and independent review", "disposition": "deferred", "rationale": "Candidate nested objects and mappings are incomplete for runtime validation. The separate frozen phase is a Codex self-audit; neither external provider agreement nor independent review exists." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts; the separate local Codex no-tools self-audit is not an independent second-provider review.", "Source and version verification remains incomplete. Eight admitted pages were readable through the research browser, but direct HTTP requests were not attempted under the owner-reported sandbox block. Zero HTTP 200 responses were measured; direct status, durable version pins, licensing and independent claim verification remain open. The coordinator checker is prepared.", "Jurisdiction, contract incorporation and deviations, permit and occupancy regimes, safety and environmental obligations, competence, privacy and retention require qualified adoption-profile review. Great Britain and US examples are not universal rules, and no local jurisdiction compliance is certified.", "Nested instance schemas, state transitions, cross-record integrity, pinned neighbor bindings, IFC and PROV-O mappings, executable conformance and adversarial fixtures remain incomplete. Functions are proposed local operations only; no runtime, engineering or legal certification is claimed.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "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." ] }, "statistics": { "sources": 8, "bundles": 7, "layers": 14, "findings": 14, "questions": 42, "artifacts": 14, "functions": 6 } }