System and method for establishing persistent cross-application object-state identity in non-parametric renovation design files through native metadata write-back and governance-consequence mutation routing

HK20137562APending Publication Date: 2026-09-11UNDERGROUND CLASSICS LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
HK22026124817
Authority / Receiving Office
HK · HK
Patent Type
Applications
Current Assignee / Owner
Filing Date
2026-06-15
Publication Date
2026-09-11

Smart Images

  • Figure 00000026_0000
    Figure 00000026_0000
  • Figure 00000027_0000
    Figure 00000027_0000
  • Figure 00000028_0000
    Figure 00000028_0000
Patent Text Reader

Abstract

A computer-implemented system and method establish persistent cross-application object-state identity for renovation design elements extracted from non-parametric computer-aided design (CAD) files by writing a machine-derived persistent object-state identifier directly into the native data structures of the originating design file as native application metadata — extended entity data (XDATA) in AutoCAD DWG and DXF files, or entity attribute dictionary records in SketchUp SKP files. This write-back operation modifies the machine-readable state of the originating file so that any subsequent parsing session, in any software environment, can retrieve the persistent object-state identifier directly from the file without re-executing the identity derivation computation. During the identity encoding and validation phase, the system derives a professional-authority dependency map from a built-environment configuration register for each renovation object candidate record and stores it as a pre-computed stable attribute of the governed object-state record, encoding the professional authority roles causally impacted when that record is mutated. A Governance Supervisor Engine reads the pre-stored professional-authority dependency map to route mutation proposals through Observation, Advisory, or Governed propagation pathways based on the governance tier of the highest-impact professional authority role identified — without live traversal of a canonical authority register. The persistent object-state identifier functions as a mandatory binding key across cost, procurement, scheduling, and compliance downstream destination registers. An identity retirement event mechanism preserves prior identifiers as immutable historical records and stamps a fresh authority map onto the replacement record.
Need to check novelty before this filing date? Find Prior Art

Description

1 SYSTEM AND METHOD FOR ESTABLISHING PERSISTENT CROSS- APPLICATION OBJECT-STATE IDENTITY IN NON-PARAMETRIC RENOVATION DESIGN FILES THROUGH NATIVE METADATA WRITE- BACK AND GOVERNANCE-CONSEQUENCE MUTATION ROUTING TECHNICAL FIELD OF THE INVENTION This invention relates to computer-aided architectural design data processing systems for the renovation and built-environment sector, specifically to a system and method for establishing and maintaining persistent cross-application object- state identity in non-parametric renovation design files through native metadata write-back, and for enforcing governance-consequence-based mutation routing to downstream project destination registers. BACKGROUND OF THE INVENTION The present invention provides a specific technical improvement to the operation of non-parametric CAD data processing systems: it extends the information-carrying capacity of non-parametric design files — formats such as AutoCAD DWG, DXF, and SketchUp SKP that do not natively support persistent cross-application object identity — by writing a machine-derived persistent object-state identifier directly into the native data structures of the originating file, and governs the downstream propagation of mutations to that identity-bearing state based on the professional authority roles causally impacted by the proposed mutation. The present invention addresses this technical limitation directly by deriving a machine-stable composite identity vector from entity geometry, layer classification, annotation context, and spatial containment data, writing the resulting persistent object-state identifier into the originating file as native application metadata (XDATA in DWG / DXF; entity attribute dictionary in SKP), and enforcing governance- consequence-based downstream mutation routing through a Governance Supervisor Engine that evaluates a professional-authority dependency map associated with each identity-bearing object-state record. Standard renovation drafting relies heavily on non-parametric CAD files containing two-dimensional vector entity records. These formats — AutoCAD DWG, DXF, and SketchUp SKP among others — do not natively provide persistent, cross- application object identity. Each entity has a transient handle assigned by the authoring application that may change between file sessions. When the same file is re-opened or re-exported, or consumed by a downstream application such as a cost-estimation system, there is no native mechanism for resolving whether a given entity corresponds to a physical component previously recorded in an external register. When renovation design information is read by a downstream application — for example, a cost estimation system or a field verification tool — the downstream application has no reliable mechanism to determine whether the entity records it reads in the current session correspond to the same physical components whose records were processed in a prior session. This produces silent identity reassignment: a wall costed in one session is re-derived as a different record in the next, breaking the continuity of cost, procurement, and inspection records. HK 20137562 A 2 Furthermore, no prior-art system derives a machine-generated governance- consequence vector from the professional-authority dependency map of an identity- bearing object-state record and uses that vector to enforce variable state-mutation propagation pathways based on which professional authority roles are causally impacted. Existing systems either route all mutations through a single pathway, or rely on manual human classification of component criticality, introducing human error and making routing non-deterministic. A further technical deficiency in the prior art arises at operational phase transition boundaries — specifically, the boundary between the design phase and the construction-award or procurement phase. Object identity graphs assembled during the design phase are typically discarded at handover boundaries, requiring construction-phase systems to reconstruct object identity from unstructured document exports. The present invention eliminates this deficiency by writing the persistent object-state identifier into the native file structure, enabling phase- transition-resilient identity continuity. SUMMARY OF THE INVENTION The present invention provides a non-conventional computational pipeline that resolves the identity-persistence limitations of non-parametric renovation design file formats through: (a) binary-level extraction of vector entity records, layer table records, block definition references, and annotation text from the native file payload; (b) derivation of a composite identity vector from spatial containment, object-class normalisation, source-entity cryptographic fingerprint, and version- stable instance discriminator components; (c) write-back of the resulting persistent object-state identifier as native application metadata directly into the originating design file; and (d) injection of the persistent object-state identifier as a mandatory binding key across all downstream data structures. The platform provides a non-conventional computational pipeline comprising: an entity-parsing engine (upstream extraction and candidate record generation); an identity encoding module (composite identity vector derivation, native-file write- back, mandatory binding key injection); a validation interface (confidence vector computation, viewport-localised correction, extraction-weight learning); a governance supervisor engine (governance-consequence vector derivation, three- pathway mutation routing); and a relationship engine (pseudo-parametric dependency tracking). These components act together to produce a governed, identity-persistent object record set from an otherwise identity-fragile non- parametric design file. The write-back limitation is retained in independent Claims 1 and 7 to provide the concrete, machine-state-modifying technical anchor that resists abstract-idea challenges. Claims 8 through 19 address the downstream mutation enforcement system based on governance-consequence routing, and Claims 20 through 24 address extended system capabilities. HK 20137562 A 3 2BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a block diagram illustrating the overall system architecture showing the Family A upstream extraction and identity binding pipeline and the Family B downstream governance-consequence mutation routing enforcement system. FIG. 2 is a flowchart of the entity-parsing engine, illustrating parsing of vector entity records, layer table records, and annotation text records to generate renovation object candidate records. FIG. 3 is a block diagram of the identity encoding module, showing the composite identity vector formula and the native application metadata write-back operation into the originating non-parametric design file. FIG. 4 is a diagram of the viewport-localised validation interface, showing the validation packet generation, confidence vector computation, and operating-mode switching between Bootstrap-Seeded and Cold Encounter modes. FIG. 5 is a flowchart of the Governance Supervisor Engine, showing governance- consequence vector derivation from the professional-authority dependency map, and routing through the Observation, Advisory, and Governed propagation pathways. FIG. 6 is a diagram of the identity retirement event mechanism, illustrating retire- record creation, superseded-by linkage generation, and flagging of downstream destination register payloads. FIG. 7 is a data flow diagram showing the persistent object-state identifier functioning as a mandatory binding key across heterogeneous downstream destination registers comprising cost, procurement, scheduling, and field- verification systems. FIG. 8 is a data flow diagram illustrating the alternative identity persistence embodiments described in Section 3.8, showing the sidecar metadata file, external governed object-state store, plugin-managed local cache, and project-level identity registry options. DETAILED DESCRIPTION OF THE INVENTION As used in this specification and the appended claims, the following terms have the meanings set out below: "composite identity vector" means a machine-computed vector derived from a calculated spatial containment path, a normalised object-class token, a source- entity cryptographic fingerprint derived from vector entity records, and a version- stable instance discriminator, from which the persistent object-state identifier is deterministically derived, wherein uniqueness of the persistent object-state identifier is determined from the composite identity vector as a whole HK 20137562 A 4 "downstream destination register" means any database, register, software module, external application interface, or project data store that receives, stores, displays, verifies, or acts upon object-state records, persistent object-state identifiers, or state-mutation payloads originating from the governed object-state store "entity-parsing engine" means a computer processing component configured to extract vector entity records, layer table records, block definition records, annotation text records, and coordinate data from a non-parametric renovation design file payload and transform them into renovation object candidate records without requiring or producing native parametric object relationships within the originating authoring application "governed object-state record" means a machine-readable record stored in the governed object-state store and associated with a persistent object-state identifier, the record containing at least source-entity reference data, object classification data, spatial containment data, validation status data, version state hash data, a populated mandatory justification string, and a pre-computed professional-authority dependency map entry derived from the built-environment configuration register during the identity encoding and validation phase at identity-creation time and stored as a pre-computed stable attribute of the record "governance-consequence vector" means a machine-generated data structure derived by the Governance Supervisor Engine from a professional-authority dependency map associated with a persistent object-state identifier, encoding, for each proposed state-mutation payload, the set of professional authority roles causally impacted by the proposed mutation and their respective governance tier (observation, advisory, or governed) "Governance Supervisor Engine" means the computer processing component configured to intercept proposed state-mutation payloads targeting governed object-state records, evaluate a professional-authority dependency map to derive a machine-generated governance-consequence vector, and route each proposed mutation through the Observation, Advisory, or Governed propagation pathway based on the governance tier of the highest-impact professional authority role identified "native application metadata" means a machine-readable data field or record that is: (a) inserted into or appended to the native data structure of the originating non- parametric renovation design file using a mechanism supported by the file format specification; (b) stored as part of the file's binary or text-encoded content when the file is saved; and (c) retrievable by any compliant parser of the same file format without requiring access to an external data store — including, but not limited to, extended entity data (XDATA) records in AutoCAD DWG and DXF format files, entity attribute dictionary key-value records in SketchUp SKP format files, and application data groups in other non-parametric CAD file formats "non-parametric renovation design file payload" means a design data payload derived from a computer-aided design file that contains vector geometry entity records, layer table records, block definition records, annotation text records, coordinate data, or equivalent visual drafting records, without requiring or relying upon native parametric object relationships within the originating authoring application HK 20137562 A 5 "persistent object-state identifier" means a stable, machine-generated identifier derived from a composite identity vector and assigned to a renovation object candidate record, which identifier remains uniform across a plurality of software environments, file sessions, and downstream destination registers and is not dependent on transient application memory addresses or native file handles that may change between file operations "professional-authority dependency map" means a machine-readable data structure associating each persistent object-state identifier with one or more professional authority roles — drawn from at minimum: structural-integrity authority, quantity- surveying authority, procurement authority, compliance authority, and project- management authority — derived from a built-environment configuration register during the identity encoding and validation phase when the renovation object candidate record is first registered, stored as a pre-computed stable attribute of the governed object-state record at identity-creation time, and readable at any subsequent mutation-routing operation without re-deriving from a live canonical authority register, and updatable through a governed configuration-update event when the built-environment configuration register is amended, with prior versions preserved in the append-only audit registry "viewport-localised validation packet" means a data structure that links an inferred renovation object candidate record to source-entity reference data, coordinate or viewport localisation information, a computed confidence vector, a mandatory justification string field, and one or more selectable correction fields, such that a validation interface can present the inferred object state at or near the location of the originating drawing entity within the authoring application viewport FIG. 1 illustrates the overall architecture of the system. The upstream pipeline (Family A) comprises a non-parametric design file input payload

[600] , an input interface

[502] that receives the unstructured non-parametric renovation design file payload, an entity-parsing engine

[504] that transforms vector entity records and annotation text into renovation object candidate records, an identity encoding module

[506] that derives a persistent object-state identifier from each candidate's composite identity vector and writes it back into the originating file as native application metadata, a viewport validation interface

[508] that computes a confidence vector and routes low-confidence candidates through a viewport-localised correction workflow, a governed object- state store

[510] that persists validated renovation object-state records with their mandatory binding keys, and a pseudo-parametric relationship engine

[512] that maintains non-native pseudo-parametric dependency records between governed object-state records. HK 20137562 A 6 The downstream pipeline (Family B) comprises a Governance Supervisor

[514] that intercepts proposed state mutations targeting governed object-state records, derives a machine-generated governance-consequence vector from the professional-authority dependency map associated with the targeted record's persistent object- state identifier, and routes each mutation through an Observation Pathway

[530] , an Advisory Pathway

[532] , or a Governed Pathway

[534] based on the governance tier of the highest-impact professional authority role identified. Downstream destination registers

[516] receive permitted propagated object-state updates. For avoidance of doubt, the reference signs appearing in the drawings identify the following corresponding computer-implemented components, data records, and routing operations. In FIG. 2,

[600] denotes the non-parametric design file payload,

[602] the binary-level file extraction pass,

[610] vector entity records,

[612] layer table records,

[614] block definition records,

[616] text annotation records,

[604] NLP tokenisation and layer signal parsing,

[606] the material flag matrix and thickness scalars,

[608] spatial containment boundary derivation, and

[620] renovation object candidate records. In FIG. 3,

[506] denotes the identity encoding module, [520a]-[520d] respectively denote the spatial containment path, normalised object-class token, source-entity cryptographic fingerprint, and version-stable instance discriminator components of the composite identity vector,

[522] denotes the persistent object-state identifier,

[524] denotes native metadata write-back, and

[526] denotes injection as a mandatory binding key. In FIG. 4,

[702] denotes confidence vector computation,

[706] automatic identity proposal,

[526] the viewport-localised validation packet,

[708] user interaction with correction fields,

[528] writing a modification metric to the extraction-weight table,

[710] Bootstrap-Seeded Mode, and

[712] Cold Encounter Mode. In FIG. 5,

[500] denotes a proposed state-mutation payload,

[510] the state- mutation transaction interface,

[520] retrieval of the pre-stored professional-authority dependency map,

[530] the Governance Supervisor Engine,

[540] identification of the highest-impact HK 20137562 A 7 governance tier,

[550] commitment to the main production object-state store,

[560] telemetry streaming to the audit registry,

[570] commitment to the main production object-state store in the advisory pathway,

[580] advisory token and consequence notification record injection,

[590] propagation to downstream destination registers,

[600] isolation in a volatile computer staging buffer with blocked downstream propagation,

[610] cryptographic clearance token validation,

[620] canonical diff commitment and downstream propagation, and

[630] discard, buffer clearing, and propagation invalidation notice generation. In FIG. 6,

[900] denotes the prior object-state record,

[902] the updated candidate record,

[904] fundamental type-change detection,

[906] the identity retirement event, [906a]-[906d] the preservation, new identifier generation, superseded-by linkage, and linked-record review operations, and

[908] the new persistent object-state identifier with active superseded-by linkage. In FIG. 7,

[506] denotes the identity encoding module,

[522] the persistent object-state identifier,

[526] viewport-localised validation packets,

[510] governed object-state records,

[1000] pseudo-parametric dependency records,

[524] machine- generated resource-control flags,

[1002] append-only audit registry entries, and

[1004] downstream register payloads. In FIG. 8,

[600] denotes the non-parametric design file payload,

[506] the identity encoding module,

[1100] write-back as XDATA or native metadata,

[1102] an external governed object-state store,

[1104] a sidecar metadata file,

[1106] a plugin-managed local cache,

[1108] a project-level identity registry,

[1110] re-derivation of the composite identity vector from source-entity references on a next parsing pass, and

[1112] cross-session and cross-application identity persistence. No component of this system requires or modifies the originating non-parametric design file into a native parametric format. The system operates directly on the binary or text-encoded file payload and writes identity data back using native extension mechanisms (XDATA in DWG / DXF; entity attribute dictionary in SKP) without altering the parametric structure of the originating application. For clarity, several terms used in this Detailed Description are defined as follows. "Persistent object-state identifier" means a stable, machine-generated identifier derived from a composite identity vector and assigned to a renovation object candidate record, which identifier remains uniform across a plurality of software HK 20137562 A 8 environments, file sessions, and downstream destination registers and is not dependent on transient application memory addresses or native file handles that may change between file operations. "Composite identity vector" means a machine-computed vector derived from a calculated spatial containment path, a normalised object-class token, a source- entity cryptographic fingerprint derived from vector entity records, and a version- stable instance discriminator. "Governance-consequence vector" means a machine-generated data structure derived by the Governance Supervisor Engine from a professional-authority dependency map associated with a persistent object-state identifier, encoding the set of professional authority roles causally impacted by a proposed mutation, together with their respective governance tier (observation, advisory, or governed). "Professional-authority dependency map" means a machine-readable data structure associating each persistent object-state identifier with one or more professional authority roles, derived from a built-environment configuration register, recording which professional authority roles are causally impacted when the associated object-state record is mutated. "Governance Supervisor Engine" means the computer processing component that intercepts proposed state-mutation payloads, retrieves the pre-stored professional- authority dependency map from the targeted governed object-state record (derived at identity-creation time and stored as a pre-computed stable attribute of that record), derives a machine-generated governance-consequence vector from that pre-stored map, and routes the proposed mutation through one of the Observation, Advisory, or Governed propagation pathways based on the governance tier of the highest-impact professional authority role identified. "Observation pathway" means the propagation pathway applied when the governance-consequence vector identifies no downstream professional authority role as causally impacted, committing the proposed mutation to the main production object-state store without a blocking hold. "Advisory pathway" means the propagation pathway applied when the governance- consequence vector identifies one or more advisory-tier professional authority roles as causally impacted, committing the mutation while injecting machine-readable advisory tokens into the downstream destination registers of the affected roles. "Governed pathway" means the propagation pathway applied when the governance- consequence vector identifies one or more governed-tier professional authority roles — including structural-integrity authority or compliance authority — as causally impacted, isolating the mutation in a volatile computer staging buffer pending cryptographic clearance token issuance. The system initialises a memory-resident parsing interface configured to execute binary-level file extraction on unstructured, non-parametric renovation CAD drawing data. The engine targets vector entity table records, block definition references, layer table records, and embedded annotation text data directly from the drawing data block, bypassing graphical rendering pipelines entirely. In preferred embodiments the engine operates on AutoCAD DWG or DXF format files. In alternative embodiments the engine operates on SketchUp SKP format files, MicroStation DGN format files, or other non-parametric vector-format design files used in renovation drafting practice. HK 20137562 A 9 Annotation-parsing routines process text entity records and multi-line text records within the drawing layers to isolate material composition parameters and regulatory compliance markers. For example, a text string reading "12.5mm Fire-Rated Gypsum Assembly" is parsed into a deterministic material flag (fire-rated: TRUE; material: gypsum) and a thickness dimension scalar (12.5mm). The engine transforms unstructured drawing entities into defined renovation object candidate records detailing: implied spatial containment boundaries, object class data derived from layer name conventions and annotation proximity, material specification data, and source-entity reference data comprising the coordinate data, layer table records, and block definition records from which each candidate was derived. At no stage does the engine require or produce a native parametric object relationship within the originating authoring application. As used in this specification, "cryptographically bound" means that the persistent object-state identifier, the source-entity fingerprint, and the version state hash are stored together or cross-referenced together in the governed object-state store, such that any later proposed mutation can be verified against the recorded object- state identity by re-deriving the fingerprint and comparing hash values. The identity encoding module generates a persistent object-state identifier for each renovation object candidate record. This identifier is constructed from a composite identity vector: I = [ P_spatial | T_class | F_entity | D_instance ] where P_spatial is a calculated spatial containment path encoding the physical room, level, and zone boundaries within which the source entity falls; T_class is a normalised object-class token derived from layer table records and annotation- parsing output; F_entity is a source-entity cryptographic fingerprint derived from the originating source vector entity records including entity handle, coordinate data, and layer identifier; and D_instance is a version-stable instance discriminator. Uniqueness of the persistent object-state identifier is determined from the composite identity vector as a whole, not from any single component. The primary technical operation of the identity encoding module is the write-back of the persistent object-state identifier into the originating non-parametric renovation design file as native application metadata. In AutoCAD DWG and DXF format files, this write-back inserts an extended entity data (XDATA) record — comprising an application-registered group code and the persistent object-state identifier value — directly into the vector entity record of each matched source entity within the file's entity table. In SketchUp SKP format files, the write-back inserts an attribute dictionary key-value pair — keyed by a registered application namespace — into the entity definition record of each matched source entity. In other non-parametric CAD file formats, the write-back uses the nearest equivalent native metadata storage mechanism supported by the file format specification. This write-back operation modifies the machine-readable state of the originating design file in a manner that: (a) persists across file save, reopen, and inter-session events; (b) is readable by any subsequent parsing operation that has access to the same file, without requiring query of an external registry; and (c) enables downstream plugin interfaces accessing the same source file to retrieve the pre- assigned persistent object-state identifier without executing a new identity encoding pass. These properties constitute a specific technical improvement to the HK 20137562 A 10 information-carrying capacity of the originating non-parametric design file that does not exist natively in DWG, DXF, or SKP file formats. Following write-back, the persistent object-state identifier is injected as a mandatory binding key across all subsequent data structures generated or managed by the system, specifically: viewport-localised validation packets, governed object-state store records, pseudo-parametric dependency records, governance-consequence vector records, append-only audit registry entries, and downstream destination register payloads. In alternative embodiments, where write-back to the originating file is unavailable, disabled, unsupported, or undesirable, the persistent object-state identifier is maintained in an external governed object-state store, sidecar metadata file, plugin- managed local cache, or project-level identity registry as described in Section 3.8. Every renovation object candidate record is passed to an interactive validation pipeline where a real-time parsing confidence vector is computed against a parameterised validation threshold. The confidence vector comprises component scores derived from: object-class signal strength (layer token match quality), spatial containment certainty (bounding geometry within room boundary), material specification match confidence (annotation alignment with material library), and source-entity reference data completeness. When all confidence vector components meet or exceed the parameterised validation threshold, the system proceeds to automatic identity proposal. When any component falls below the threshold, the interface generates a viewport-localised validation packet containing the inferred renovation object candidate record, corresponding source-entity reference data including coordinate data and source file entity handle, the confidence vector components with individual sub-scores, and a set of context-specific correction fields matched to the detected object class. Each validation packet includes a mandatory justification string field that must be populated — either automatically from annotation-parsing output or through user correction — before the renovation object candidate record may be promoted to a validated governed object-state record. A record lacking a populated justification string is rejected by the system as an incomplete validation event. The validation interface operates in two machine-configured operating modes: (a) Bootstrap-Seeded Mode: When project context data — including room code records, naming convention templates, and package structure records — has been pre-loaded into the governed object-state store, the validation interface operates with elevated prior context. Confidence scores are computed against this pre- existing context, producing a higher proportion of above-threshold automatic proposals. (b) Cold Encounter Mode: When no prior project context exists in the governed object-state store, the validation interface executes a pre-scan signal quality assessment before generating any object-state records. The pre-scan produces a structured signal quality report categorising detected objects by signal-strength tier. The interface then executes a priority-ordered guided confirmation sequence in which room spatial-boundary candidates must be confirmed before any dependent object candidate records are processed, because downstream spatial containment paths depend on confirmed room identity records. HK 20137562 A 11 In both operating modes, when a user interacts with the correction fields of a viewport-localised validation packet and commits a correction, the system writes a validation status entry and a modification metric directly into an extraction-weight table utilised by the entity-parsing engine, systematically improving the accuracy coefficients of future automated extraction passes. During the validation phase, the system also derives, from the built-environment configuration register, the professional-authority dependency map for each renovation object candidate record — encoding the set of professional authority roles that would be causally impacted by any future mutation to that record — and stores this map as a pre-computed stable attribute of the governed object-state record. This derivation occurs once, at the moment of identity creation and validation, not at the time of each subsequent mutation proposal. When a mutation is later intercepted, the Governance Supervisor Engine reads the pre-stored map directly from the governed object-state record rather than performing a live traversal of a canonical authority register. A defining architectural property of this system is that the professional-authority dependency map evaluated by the Governance Supervisor Engine is not computed at mutation time. It was derived from the built-environment configuration register during the identity encoding and validation phase, when the renovation object candidate record was first registered, and pre-stored as a pre-computed stable attribute of the governed object-state record. The Governance Supervisor Engine reads this pre-stored map rather than performing a live traversal of a canonical authority register. This precompute-and-stamp approach means the routing basis for any mutation to an identity-bearing object is determined by the object's identity attributes — stamped at birth from a built-environment configuration register — not by a real-time computation against a changing system state. The pre-stored professional-authority dependency map remains stable for the lifetime of the governed object-state record associated with a given persistent object-state identifier. Where a change to the built-environment configuration register alters the authority-impact classification of a renovated object class — for example, a regulatory change that reclassifies a material from non-governed to compliance-authority-governed — the system updates the stored professional- authority dependency map for all affected governed object-state records through a governed configuration-update event, with the prior map version preserved as a timestamped entry in the append-only audit registry. This version-controlled update mechanism does not require a new identity-creation pass and does not alter the persistent object-state identifier of the affected records. The downstream lifecycle of each governed object-state record is controlled by the Governance Supervisor Engine. When a mutation proposal targeting a validated object-state record is intercepted, the Governance Supervisor Engine evaluates the professional-authority dependency map associated with the persistent object-state identifier of the targeted record. The professional-authority dependency map is derived from a built-environment configuration register maintained by the system and records, for each persistent object-state identifier, the set of professional authority roles — drawn from at minimum: structural-integrity authority, quantity- surveying authority, procurement authority, compliance authority, and project- management authority — that are causally impacted when the associated object- state record is mutated. HK 20137562 A 12 From this evaluation, the Governance Supervisor Engine derives a machine- generated governance-consequence vector encoding, for each identified professional authority role, the governance tier (observation, advisory, or governed) applicable to that role's causal impact. The routing pathway is determined by the governance tier of the highest-impact authority role identified in the governance- consequence vector: (1) Observation Pathway — applied when the governance-consequence vector indicates no downstream professional authority role is causally impacted by the proposed mutation. The proposed mutation is written directly to the main production object-state store without workflow interruption. A parallel transaction telemetry replica is streamed to an independent append-only audit registry. No blocking lock is applied. (2) Advisory Pathway — applied when the governance-consequence vector identifies one or more advisory-tier professional authority roles — including quantity-surveying authority or project-management authority — as causally impacted. The proposed mutation is committed to the main production object-state store, but a machine-readable advisory token and a consequence notification record encoding the affected professional authority role identifiers are injected into the transaction response metadata block and propagated into all downstream destination register payloads bound to the persistent object-state identifier, requiring acknowledgment within a configured time window. (3) Governed Pathway — applied when the governance-consequence vector identifies one or more governed-tier professional authority roles — including structural-integrity authority or compliance authority — as causally impacted. The proposed mutation is isolated within a volatile computer staging buffer. Data propagation to all downstream destination registers is blocked unless a cryptographic clearance token validates against both the persistent object-state identifier and a generated hash of the proposed mutation payload. If cryptographic clearance is not received within a configured hold window, or if the proposed mutation is rejected by the relevant professional authority role, the staged mutation is discarded, the volatile staging buffer is cleared, and a propagation invalidation notice is broadcast to all connected downstream destination registers referencing the targeted persistent object-state identifier. When the identity encoding module determines that an updated renovation object candidate record exhibits a composite identity vector that diverges fundamentally from the composite identity vector of a previously confirmed object-state record sharing the same source-entity reference data — indicating that the originating physical component has been replaced by a component of a different object class — the system triggers an Identity Retirement Event comprising: (a) preserving the prior persistent object-state identifier as an immutable historical record with a retirement timestamp and a fundamental-type-change reason code; (b) generating a new persistent object-state identifier from the composite identity vector of the replacement object candidate record; (c) creating a superseded-by linkage record associating the retired and new persistent object-state identifiers; and (d) flagging all governed object-state store records, dependency records, and downstream destination register payloads linked to the retired identifier for review. The operation does not destroy historical records and does not silently reassign the prior identifier to the replacement object. The Identity Retirement Event also triggers derivation of a fresh professional-authority dependency map for the replacement governed object- state record, computed from the built-environment configuration register for the HK 20137562 A 13 new object class and stored as a pre-computed stable attribute of the replacement record at the moment of its identity creation. The retired record's professional- authority dependency map is preserved as part of the immutable historical record. In certain embodiments, the persistent object-state identifier is written back into the originating non-parametric renovation design file as native application metadata as described above In other embodiments, where native metadata write-back is unavailable, disabled, unsupported by the originating file format, or undesirable for a given deployment configuration, the persistent object-state identifier is maintained using one or more of the following alternative persistence mechanisms: (a) an external governed object-state store keyed by source-entity reference data; (b) a sidecar metadata file stored in association with the originating design file containing a mapping of source-entity reference data to persistent object-state identifiers; (c) a plugin- managed local cache maintained by an authoring-environment plugin and synchronised with the governed object-state store; or (d) a project-level identity registry accessible to all plugin interfaces and downstream destination registers within the same project context. In such alternative embodiments, cross-session and cross-application identity persistence is maintained by re-deriving at least a portion of the composite identity vector from source-entity reference data present in the non-parametric design file payload and resolving the re-derived composite identity vector against the alternative persistence mechanism to retrieve the previously assigned persistent object-state identifier. Where a source-entity handle is unavailable, unstable, or altered during file operations, the source-entity cryptographic fingerprint component of the composite identity vector may be derived from one or more of: coordinate bounds, layer identifier, block reference, geometry signature, annotation proximity, spatial containment relationship, entity type, or file-level checksum context. The system and method described herein produce specific technical effects in computer-aided design data processing infrastructure, including: (a) Specific technical improvement to non-parametric CAD file processing: The write-back operation constitutes a specific improvement to the way computer systems process and store identity information in non-parametric CAD files. Non- parametric CAD formats — DWG, DXF, SKP, and equivalents — do not natively store persistent cross-application object identity. The present invention extends these file formats by writing a machine-derived persistent object-state identifier into native data structures of the originating file (XDATA in DWG / DXF; entity attribute dictionary in SKP), thereby enabling any subsequent parsing system that reads the same file to retrieve that identity directly from the file, without requiring query of an external registry and without re-executing the derivation computation. This improvement to the information-carrying capacity of the originating file is a specific technical advance over prior-art non-parametric CAD processing systems. (b) Persistent cross-session and cross-application object identity: The system maintains a persistent object-state identifier for each renovation design element across non-parametric file save, export, import, file-format conversion, and downstream register synchronisation events — a capability that prior-art non- parametric CAD processing systems do not provide. HK 20137562 A 14 (c) Reduction of redundant extraction computation: By writing the persistent object- state identifier into the originating design file's native data structure, the system enables subsequent parsing passes to retrieve the identifier without executing a full new composite identity vector derivation, reducing repeated computation and enabling stateless downstream integrations. (d) Prevention of silent object identity reassignment: The identity retirement event mechanism prevents the system from silently reassigning a prior persistent object- state identifier to a replacement object of a different class, preserving historical audit integrity and preventing downstream register corruption. (e) Non-native pseudo-parametric dependency tracking: The relationship engine generates logical dependency records between governed object-state records without converting or altering the originating non-parametric design file, enabling constraint and dependency tracking in authoring environments that do not natively support parametric relationships. (f) Machine-executed governance-consequence mutation routing: The Governance Supervisor Engine routes proposed mutations through processor-executed propagation pathways selected by machine-generated governance-consequence vectors derived from the professional-authority dependency map of each object- state record, rather than by manual human classification or abstract risk scoring. This enables automated, authority-grounded enforcement of renovation governance constraints — routing each mutation along the pathway appropriate to the professional authority roles it causally impacts. (g) Phase-transition-resilient object identity: By writing the persistent object-state identifier into the native application metadata of the originating non-parametric design file, and injecting it as a mandatory binding key across governed object-state store records and downstream destination register payloads, the system enables the object identity established during the design phase to survive operational phase transitions — including project package issuance, construction award, and procurement handover — without requiring re-derivation by the receiving system. Construction-phase execution systems consuming the governed object-state records can resolve object identity directly from the persistent object-state identifier without re-executing the composite identity vector derivation computation. This phase-transition resilience is a specific technical improvement over prior-art systems in which the identity graph assembled during the design phase is discarded at the handover boundary, forcing downstream construction-phase systems to reconstruct object identity from unstructured document exports. These technical effects represent specific improvements to the operation of computer systems processing non-parametric renovation design data and are not limited to human project management, business organisation, or abstract information handling. The following before-and-after description illustrates the concrete technical problem solved by the present invention and the specific machine-state change caused by its operation: Before application of the invention: A non-parametric AutoCAD DWG renovation drawing file contains a wall element represented as two LINE entity records on a layer named "WALL-PARTITION". The LINE entities have transient entity handles assigned by the authoring application. No persistent, cross-application identity record is stored within the DWG file. When a cost-estimation system reads the file in HK 20137562 A 15 a subsequent session, it cannot determine whether the LINE entities correspond to the same physical wall whose cost was estimated in a prior session. The cost- estimation system must re-derive an identity from scratch, or overwrite the prior cost record, or maintain a fragile external mapping that may break if entity handles change. After application of the invention: The entity-parsing engine ingests the DWG file and identifies the LINE entities as a partition wall candidate. The identity encoding module computes a composite identity vector from the spatial containment path (room boundary), normalised object-class token ("WALL-PARTITION"), source- entity fingerprint (hash of entity handles, coordinates, and layer), and instance discriminator. The resulting persistent object-state identifier is written back into the DWG file as an XDATA record appended to each matched LINE entity. The machine- readable state of the DWG file is now modified: it contains a format-native data field that was not present before and that carries the persistent object-state identifier as part of the file's own data structure. When a cost-estimation system or any other downstream application reads the same DWG file in any subsequent session, it can extract the persistent object-state identifier directly from the XDATA record of the LINE entity, match it against the governed object-state store, and retrieve the prior cost record — without requiring re-execution of the identity encoding computation and without consulting a separate external registry. The present invention is applicable in any industry or professional practice that employs non-parametric computer-aided design tools for the documentation, planning, or execution of renovation, refurbishment, fit-out, or built-environment modification projects, particularly where data integrity and object-state continuity must be maintained across multiple software applications, heterogeneous downstream destination registers, and successive project phases. Specific application domains include: interior renovation contractors and fit-out specialists maintaining material procurement and installation records; architectural practices managing renovation documentation for regulatory compliance submissions; facilities management organisations tracking built-environment component states across asset life cycles; construction cost consultants requiring persistent object identity continuity between design file revisions and cost database records; and built-environment software platform providers developing governance layers above existing non-parametric authoring tools. The invention provides a concrete technical benefit in each such context by enabling persistent, cross- application object identity in non-parametric CAD files without requiring file-format conversion or the replacement of existing authoring tool infrastructure. The invention is further applicable across multi-profession project coordination contexts in which multiple professional disciplines — including architectural designers, structural engineers, mechanical, electrical, and plumbing consultants, quantity surveyors, specialist trade suppliers, and construction contractors — each contribute governed object-state records to a shared project identity graph. In such contexts, the persistent object-state identifier functions as a universal binding key that enables object-state records contributed by different professional workstations and different authoring applications to be resolved to the same governed physical component, regardless of the non-parametric file format or professional discipline from which each record originated. The governance-consequence routing layer ensures that mutations impacting the authority scope of multiple professional HK 20137562 A 16 disciplines are routed through the appropriate propagation pathway automatically, without requiring manual classification by any individual professional role. HK 20137562 A 1 What is claimed is: 1. A computer-implemented system for establishing persistent cross-application object-state identity in non-parametric renovation design files and converting renovation object candidates into governed object-state records, the system comprising: an input interface configured to receive an unstructured non-parametric renovation design file payload comprising vector entity records, layer table records, block definition records, text annotation records, and coordinate data; an entity-parsing engine, comprising one or more computer processors, configured to parse the non-parametric renovation design file payload without requiring native parametric object relationships in the originating design file, and to generate renovation object candidate records comprising object classification data, spatial containment data, material specification data, and source-entity reference data derived from the layer table records and text annotation records; an identity encoding module configured to: (i) generate, for each renovation object candidate record, a persistent object-state identifier derived from a composite identity vector comprising a calculated spatial containment path, a normalised object-class token, a source-entity cryptographic fingerprint derived from the vector entity records, and a version-stable instance discriminator, wherein uniqueness of the persistent object-state identifier is determined from the composite identity vector as a whole; (ii) write the persistent object-state identifier into the originating non-parametric renovation design file as native application metadata, thereby causing a concrete modification to the machine-readable state of the originating file that enables retrieval of the persistent object-state identifier by a subsequent parsing operation on the same file without re-executing the identity encoding computation and without converting the originating file to a native parametric format; and (iii) inject the persistent object-state identifier as a mandatory binding key across subsequent data structures generated or managed by the system comprising validation packets, object-state records, dependency records, governance-consequence vector records, audit entries, and downstream destination register payloads; a validation interface configured to compute a confidence vector for each renovation object candidate record, compare the confidence vector with a parameterised validation threshold, and, when the confidence vector fails the parameterised validation threshold, generate a viewport-localised validation packet containing the renovation object candidate record, corresponding source-entity reference data, confidence vector components, a mandatory justification string field, and context-specific correction fields, wherein a received user interaction with the correction fields writes a validation status entry and a modification metric into an extraction-weight table utilised by the entity-parsing engine, and wherein a renovation object candidate record lacking a populated mandatory justification string is rejected as an incomplete validation event; a governed object-state store configured to record validated renovation object-state records associated with the persistent object-state identifiers, the source-entity reference data, an immutable version state hash, a populated mandatory justification string, and a pre-computed professional-authority dependency map HK 20137562 A 2 entry derived from a built-environment configuration register during the identity encoding and validation phase and stored as a pre-computed stable attribute of the governed object-state record at identity-creation time, the pre-computed professional-authority dependency map encoding the professional authority roles that are causally impacted when the associated object-state record is mutated; and a relationship engine configured to evaluate validated renovation object-state records against a built-environment configuration ruleset comprising spatial containment, material compatibility, dependency, and compliance constraints to generate non-native pseudo-parametric dependency records between the persistent object-state identifiers without altering the originating non-parametric renovation design file into a native parametric model. 2. The system of Claim 1, wherein the entity-parsing engine executes an annotation- parsing routine on the text annotation records to parse and transform text metadata strings into deterministic material composition tags, assembly thickness dimensions, and localised architectural zone markers. 3. The system of Claim 1, wherein the native application metadata written by the identity encoding module comprises: extended entity data (XDATA) records inserted into vector entity records of the originating design file when the originating file is in AutoCAD Drawing (DWG) or Drawing Exchange Format (DXF) format, the XDATA records containing an application-registered group code and the persistent object- state identifier value; entity attribute dictionary key-value records inserted into entity definition records of the originating design file when the originating file is in SketchUp (SKP) format, the key-value records keyed by a registered application namespace; or equivalent native attribute storage records supported by the file format specification of the originating design file in other non-parametric CAD formats; wherein the persistent object-state identifier is retrievable by a subsequent parsing operation on the same originating design file by reading the corresponding native metadata record, without executing a new identity encoding computation and without converting the originating design file to a parametric format. 4. The system of Claim 1, wherein the validation interface operates in a first operating mode when project context data pre-exists in the governed object-state store, said first operating mode applying the pre-existing project context data as prior information in the confidence vector computation; and in a second operating mode when no project context data pre-exists in the governed object-state store, said second operating mode executing a signal quality pre-scan assessment of the entire non-parametric renovation design file payload before generating any object- state records, and enforcing a priority-ordered confirmation sequence in which room-boundary spatial candidates must be confirmed before any dependent object candidate records are processed. 5. The system of Claim 1, wherein the identity encoding module, upon detecting that an updated renovation object candidate record exhibits a composite identity vector that diverges fundamentally from the composite identity vector of a previously confirmed object-state record sharing the same source-entity reference data, triggers an identity retirement event comprising: preserving the prior persistent object-state identifier as an immutable historical record with a retirement timestamp and a fundamental-type-change reason code; generating a new persistent object- state identifier from the composite identity vector of the replacement renovation HK 20137562 A 3 object candidate record; creating a superseded-by linkage record associating the retired and new persistent object-state identifiers; and flagging all governed object- state store records, dependency records, and downstream destination register payloads linked to the retired identifier for review. 6. The system of Claim 1, wherein the persistent object-state identifier remains uniform and synchronised across a plurality of independent downstream destination registers comprising a three-dimensional rendering engine, a Building Information Modelling (BIM) verification system, a material procurement database, a project scheduling database, and a field verification register. 7. A computer-implemented method for establishing persistent cross-application object-state identity in non-parametric renovation design files and converting renovation object candidates into governed object-state records, the method comprising: ingesting, via an input interface, an unstructured non-parametric renovation design file payload containing vector entity records, layer table records, block definition records, annotation text records, and coordinate data; parsing the payload via an entity-parsing engine to generate renovation object candidate records comprising object class tokens, spatial containment paths, material specification data, and source-entity reference data, without modifying the originating renovation design file into a native parametric structure; generating, via an identity encoding module, a persistent object-state identifier for each renovation object candidate record derived from a composite identity vector comprising a calculated spatial containment path, a normalised object class token, a source-entity cryptographic fingerprint derived from the vector entity records, and a version-stable instance discriminator, wherein uniqueness of the persistent object-state identifier is determined from the composite identity vector as a whole; writing the persistent object-state identifier into the originating non-parametric renovation design file as native application metadata, thereby causing a concrete modification to the machine-readable state of the originating file that enables retrieval of the persistent object-state identifier by a subsequent parsing operation on the same file without re-executing the identity encoding computation and without converting the originating file to a native parametric format; injecting the persistent object-state identifier as a mandatory binding key across subsequent data structures generated or managed by the method comprising validation packets, dependency records, governance-consequence vector records, audit entries, and destination register payloads; computing a confidence vector for each renovation object candidate record and, when the confidence vector fails a parameterised validation threshold, generating a viewport-localised validation packet containing the renovation object candidate record, source-entity reference data, confidence vector components, a mandatory justification string field, and selectable correction fields, wherein user interaction with the correction fields writes a modification metric into an extraction-weight table utilised by the entity-parsing engine, and wherein the record is rejected as an HK 20137562 A 4 incomplete validation event until the mandatory justification string field is populated; establishing non-native pseudo-parametric dependency records between persistent object-state identifiers of validated renovation object candidate records via a relationship engine evaluating a built-environment configuration ruleset; and storing validated renovation object-state records in a governed object-state store, each record associated with the persistent object-state identifier, source-entity reference data, an immutable version state hash, a populated mandatory justification string, and a pre-computed professional-authority dependency map entry derived from a built-environment configuration register during the identity encoding and validation phase and stored as a pre-computed stable attribute of the record at identity-creation time, the pre-computed professional-authority dependency map encoding the professional authority roles causally impacted when the associated object-state record is mutated. 8. A computer-implemented governance system for enforcing variable state- mutation propagation pathways across heterogeneous downstream destination registers based on governance-consequence classification of proposed mutations to validated renovation object-state records, the system comprising: a state-mutation transaction interface configured to intercept a proposed state- mutation payload targeting a validated renovation object-state record stored in a governed object-state store, the targeted record associated with a persistent object- state identifier injected as a mandatory binding key across subsequent data structures generated or managed by the governed object-state environment; a Governance Supervisor Engine comprising one or more processors configured to: retrieve and evaluate the pre-stored professional-authority dependency map derived at identity-creation time and stored as a pre-computed stable attribute of the targeted governed object-state record, to derive a machine-generated governance- consequence vector encoding which professional authority roles — drawn from at minimum: structural-integrity authority, quantity-surveying authority, procurement authority, compliance authority, and project-management authority — are causally impacted by the proposed mutation, and the governance tier of each such role; and determine a routing pathway by identifying the highest-impact governance tier among the causally impacted professional authority roles and executing the determined pathway from among: an observation pathway configured to commit the proposed mutation to a main production object-state store while concurrently streaming a parallel transaction telemetry replica to an independent append-only audit registry configured to calculate real-time built-environment ruleset divergence analytics, applied when the governance-consequence vector identifies no downstream professional authority role as causally impacted; an advisory pathway configured to commit the proposed mutation to the main production object-state store while structurally injecting a machine-readable advisory token and a consequence notification record — encoding the identifiers of the causally impacted advisory-tier professional authority roles — into a transaction response metadata block, wherein the machine-readable advisory token is HK 20137562 A 5 propagated into all downstream destination register payloads bound to the persistent object-state identifier, applied when the governance-consequence vector identifies one or more advisory-tier professional authority roles as causally impacted; and a governed pathway configured to isolate the proposed mutation within a volatile computer staging buffer, block data propagation to all downstream destination registers, permit propagation only upon verification of a cryptographic clearance token that validates against at least the persistent object-state identifier and a generated hash of the proposed state-mutation payload, and upon validation failure or rejection by the identified governed-tier professional authority role, discard the staged mutation, clear the volatile computer staging buffer, and issue a propagation invalidation notice to all connected downstream destination registers referencing the persistent object-state identifier, applied when the governance-consequence vector identifies one or more governed-tier professional authority roles — including structural-integrity authority or compliance authority — as causally impacted; and an independent append-only audit registry configured to archive each accepted transaction state, advisory token injection event, clearance token event, and rejected-mutation discard event as a discrete frozen node, preventing database entry overwrite operations and constructing a hash-linked immutable state log. 9. The system of Claim 8, wherein the professional-authority dependency map is derived from a built-environment configuration register associating each canonical object classification with one or more professional authority roles, and wherein the governance-consequence vector encodes a separate impact-tier field for each identified professional authority role. 10. The system of Claim 9, wherein the Governance Supervisor Engine automatically forces selection of the governed pathway when the governance-consequence vector identifies structural-integrity authority or compliance authority as causally impacted, regardless of other pathway selection criteria. 11. The system of Claim 9, wherein the Governance Supervisor Engine automatically forces selection of the observation pathway when the governance-consequence vector encodes an empty authority impact set, confirming that the proposed mutation affects no record referenced by any downstream professional authority destination register. 12. The system of Claim 8, wherein the independent append-only audit registry archives each accepted transaction state as a discrete frozen node, preventing database entry overwrite operations and constructing a hash-linked immutable state log that maps current object-state configurations back to parent authorisation events. 13. The system of Claim 8, wherein the downstream destination registers across which the persistent object-state identifier remains synchronised comprise at least two of: a bill-of-quantities register, a three-dimensional rendering engine, a Building HK 20137562 A 6 Information Modelling (BIM) verification system, a material procurement database, a project scheduling database, and a field verification register. 14. A computer-implemented method for enforcing variable state-mutation propagation pathways across heterogeneous downstream destination registers based on governance-consequence classification of proposed mutations to validated renovation object-state records, the method comprising: intercepting, via a state-mutation transaction interface, a proposed state-mutation payload targeting a validated renovation object-state record associated with a persistent object-state identifier; retrieving and evaluating, via a Governance Supervisor Engine, the pre-stored professional-authority dependency map derived at identity-creation time and stored as a pre-computed stable attribute of the targeted governed object-state record, to derive a machine-generated governance-consequence vector encoding which professional authority roles — drawn from at minimum: structural-integrity authority, quantity-surveying authority, procurement authority, compliance authority, and project-management authority — are causally impacted by the proposed mutation, and the governance tier of each such role; determining a routing pathway by identifying the highest-impact governance tier among the causally impacted professional authority roles; and executing the determined routing pathway as one of: an observation pathway that commits the proposed mutation to a main production object-state store while streaming a parallel transaction telemetry replica to an independent append-only audit registry, applied when the governance-consequence vector identifies no downstream professional authority role as causally impacted; an advisory pathway that commits the proposed mutation to the main production object-state store while injecting a machine-readable advisory token and a consequence notification record into a transaction response metadata block propagated to all downstream destination register payloads bound to the persistent object-state identifier, applied when the governance-consequence vector identifies one or more advisory-tier professional authority roles as causally impacted; or a governed pathway that isolates the proposed mutation within a volatile computer staging buffer, blocks data distribution to all downstream destination registers pending verification of a cryptographic clearance token against the persistent object-state identifier and a hash of the proposed mutation payload, and upon validation failure, discards the staged mutation, clears the volatile staging buffer, and generates a propagation invalidation notice to all connected downstream destination registers referencing the persistent object-state identifier, applied when the governance-consequence vector identifies one or more governed-tier professional authority roles as causally impacted. HK 20137562 A 7 15. The method of Claim 14, wherein the observation pathway executes background telemetry logging without applying synchronous database locking to the main production object-state store or to user input operations in an upstream authoring workspace. 16. The method of Claim 14, wherein the advisory pathway propagates the injected machine-readable advisory token into downstream inventory tracking registers and professional-authority notification interfaces bound to the persistent object-state identifier, requiring acknowledgment within a configured time window from each identified advisory-tier professional authority role. 17. The method of Claim 14, wherein the governed pathway clears the volatile computer staging buffer and broadcasts the propagation invalidation notice to all connected downstream destination registers when the cryptographic clearance token is absent, expired, or fails to match the hash of the proposed state-mutation payload, or when the identified governed-tier professional authority role explicitly rejects the proposed mutation. 18. A non-transitory computer-readable storage medium storing computer-readable instructions that, when executed by one or more processors, cause the processors to perform a method comprising: ingesting a non-parametric renovation design file payload comprising vector entity records, layer table records, block definition records, text annotation records, and coordinate data from an unstructured drafting environment; parsing the layer table records and text annotation records to generate renovation object candidate records comprising object class tokens, spatial containment data, material specification data, and source-entity reference data, without modifying the originating renovation design file into a native parametric structure; generating a persistent object-state identifier for each renovation object candidate record from a composite identity vector comprising a calculated spatial containment path, a normalised object class token, a source-entity cryptographic fingerprint derived from the vector entity records, and a version-stable instance discriminator, wherein uniqueness of the persistent object-state identifier is determined from the composite identity vector as a whole; writing the persistent object-state identifier into the originating non-parametric renovation design file as native application metadata, thereby causing a concrete modification to the machine-readable state of the originating file that enables retrieval of the persistent object-state identifier by a subsequent parsing operation on the same file without re-executing the identity encoding computation; injecting the persistent object-state identifier as a mandatory binding key across subsequent data structures generated or managed by the method comprising validation packets, dependency records, governance-consequence vector records, audit entries, and downstream destination register payloads; computing a confidence vector for each renovation object candidate record and, when the confidence vector fails a parameterised validation threshold, generating a HK 20137562 A 8 viewport-localised validation packet containing the renovation object candidate record, source-entity reference data, confidence vector components, a mandatory justification string field, and selectable correction fields, and writing user-supplied correction data into an extraction-weight table, and rejecting the record as an incomplete validation event until the mandatory justification string field is populated; establishing non-native pseudo-parametric dependency records between persistent object-state identifiers via a relationship engine evaluating a built-environment configuration ruleset; and storing validated renovation object-state records in a governed object-state store with an immutable version state hash, a populated mandatory justification string, and a pre-computed professional-authority dependency map entry derived from a built-environment configuration register during the identity encoding and validation phase and stored as a pre-computed stable attribute of each record at identity- creation time. 19. A non-transitory computer-readable storage medium storing computer-readable instructions that, when executed by one or more processors, cause the processors to perform a method comprising: intercepting a proposed state-mutation payload targeting a stored renovation object-state record, the payload referencing a persistent object-state identifier injected as a mandatory binding key; retrieving and evaluating the pre-stored professional-authority dependency map derived at identity-creation time and stored as a pre-computed stable attribute of the targeted governed object-state record, to derive a machine-generated governance- consequence vector encoding which professional authority roles are causally impacted by the proposed mutation and their respective governance tier; determining a routing pathway by identifying the highest-impact governance tier in the governance-consequence vector; and routing the proposed mutation through one of: an observation pathway that commits the mutation while streaming a telemetry replica to an independent append-only audit registry when no professional authority role is causally impacted; an advisory pathway that commits the mutation while injecting machine-readable advisory tokens into downstream destination registers of identified advisory-tier professional authority roles when advisory-tier roles are causally impacted; or a governed pathway that isolates the mutation in a volatile staging buffer, blocks propagation to downstream destination registers pending cryptographic clearance token verification against the persistent object-state identifier and a hash of the proposed mutation, and discards the staged mutation and issues a propagation invalidation notice upon validation failure or rejection by the identified governed-tier professional authority role when governed-tier roles are causally impacted. HK 20137562 A 9 20. The non-transitory computer-readable storage medium of Claim 18, wherein the instructions further cause the processors to: detect that an updated renovation object candidate record exhibits a composite identity vector that diverges fundamentally from a composite identity vector of a previously confirmed object- state record sharing the same source-entity reference data; preserve the prior persistent object-state identifier as an immutable historical record with a retirement timestamp and a fundamental-type-change reason code; generate a new persistent object-state identifier for the replacement object; and create a superseded-by linkage record associating the retired and new persistent object-state identifiers. 21. The system of Claim 1, wherein, when native application metadata write-back is unavailable, disabled, or unsupported by the originating non-parametric renovation design file format, the persistent object-state identifier is maintained in one or more of: an external governed object-state store, a sidecar metadata file stored in association with the originating design file, a plugin-managed local cache, or a project-level identity registry; and wherein, during a subsequent parsing pass on the same source file, the persistent object-state identifier is retrieved by re-deriving at least a portion of the composite identity vector from source-entity reference data present in the non-parametric renovation design file payload and resolving the re- derived composite identity vector against the external governed object-state store, sidecar metadata file, plugin-managed local cache, or project-level identity registry. 22. The system of Claim 1, wherein the governed object-state store maintains cross- phase object identity continuity such that the persistent object-state identifier generated from a design-phase non-parametric renovation design file payload remains the canonical binding key when the corresponding governed object-state record is consumed by a construction-phase execution system, thereby enabling the construction-phase execution system to resolve object identity without re- deriving the composite identity vector from source-entity reference data and without requiring re-issuance of the design-phase non-parametric renovation design file payload. 23. The system of Claim 1, wherein the relationship engine generates, for a validated renovation object-state record subject to a proposed mutation, a causal propagation record comprising: a derived quantity change record in a bill-of-quantities data structure linked to the affected spatial containment path and object class token; a derived material specification update record in a procurement register linked to the material tag of the affected renovation object-state record; and a derived scheduling constraint record in a project scheduling database linked to the dependency graph position of the affected renovation object-state record; each derived record bound to the same persistent object-state identifier as the originating renovation object- state record, such that the causal impact of the proposed mutation is machine- traceable across cost, procurement, and scheduling downstream destination registers through the mandatory binding key. 24. The system of Claim 1, wherein the governed object-state store emits, for each governed object-state record, a machine-readable freshness indicator associated with the persistent object-state identifier, the freshness indicator encoding one of: a current state indicating that the persistent object-state identifier is the active canonical binding key for the corresponding built-environment component across all connected downstream destination registers; a superseded state indicating that the persistent object-state identifier has been retired pursuant to an identity HK 20137562 A 10 retirement event and replaced by a successor persistent object-state identifier associated with a superseded-by linkage record; a provisional state indicating that the renovation object candidate record associated with the persistent object-state identifier has not yet received a validated confirmation from the validation interface; or an invalidated state indicating that a propagation invalidation notice has been issued to downstream destination registers following a failed cryptographic clearance token verification in the governed pathway; wherein downstream destination registers receiving the governed object-state record payload obtain the freshness indicator as part of the mandatory binding key data structure associated with the persistent object-state identifier. HK 20137562 A 1 Drawings Fig. 1 HK 20137562 A 2 Fig. 2 HK 20137562 A 3 Fig. 3 HK 20137562 A 4 Fig. 4 HK 20137562 A Fig. 5 5 HK 20137562 A 6 Fig. 6 HK 20137562 A 7 Fig. 7 HK 20137562 A 8 Fig. 8 HK 20137562 A