A method and system for verifying the consistency of asynchronous graphical interface object file associations

By forming object identity packets, session identity packets, and unique operation sources in an asynchronous graphical interface, and collecting resource sets before and after the interaction, a context of expected and actual attachments is formed, which solves the problem of file association consistency verification in asynchronous graphical interfaces and ensures the accuracy of file sources and the reliability of persistence.

CN123114972APending Publication Date: 2026-11-17GUANGZHOU KUNJIE TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611379692.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-07
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In asynchronous graphical interfaces, existing technologies cannot effectively prove the consistency of the association between objects, sessions, resources, and files, resulting in the inability to verify file integrity. Furthermore, byte replacements after disk writes cannot be overwritten, leading to the repeated use of erroneous files.

Method used

By acquiring graphical interface nodes, target object selection conditions, and controlled storage root directories, object identity packets and session identity packets are formed to determine the unique source of the operation. Resource sets before and after the interaction are collected to form expected and actual attachment contexts, and evidence chain verification is performed to form a trusted file record.

Benefits of technology

Ensure a continuous correspondence between the object, the unique activity panel, the current operation, and the unique newly added resource; suppress initial attribution errors; prevent files with incorrect file formats, sizes, and normal summaries from being misused; and reduce the risk of erroneous file propagation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123114972A_ABST
    Figure CN123114972A_ABST
Patent Text Reader

Abstract

The application discloses a kind of asynchronous graphic interface object file association consistency verification method, it is related to graphical user interface technical field, it solves the technical problem that existing graphic interface technology fails to associate evidence, cannot prove file source and cannot cover the byte replacement after falling disk.The method includes, step one: according to graphic interface node and target object selection condition forms object identity package;Step two: object identity package is bound with unique active panel and forms session identity package;Step three: determine the only operation source in unique active panel;Step four: compare the resource set before interaction with the resource set after interaction to obtain unique new resource;Step five: compare expected attachment context with measured attachment context, and verify file transfer evidence and file to form pending record.The application also discloses a kind of asynchronous graphic interface object file association consistency verification system.The application suppresses initial attribution error.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of graphical user interface technology, and more specifically, to an asynchronous graphical user interface object file association consistency verification method and system. Background Technology

[0002] An asynchronous master-slave interface refers to an interface where one side displays a list of objects, while the other side displays the details, session, or attachments of the current object. When a user selects an item from the list, the selection style, network response, details rendering, and resource preview are not completed in the same atomic action. Therefore, a brief or persistent state may occur where "object A is selected in the list, but object B is still displayed in the details panel."

[0003] In a graphical interface that changes asynchronously and whose background associations cannot be directly trusted, how can we improve the consistency of associations between objects, sessions, current operations, resources, and current file bytes through verifiable technical evidence, and ensure that subsequent programs accessing the controlled access architecture refuse to use files with inconsistent context, version, or current bytes?

[0004] The existing technology also has the following drawbacks: (1) List selection, activity panel switching, network return, DOM update and resource loading are completed at different times. The object list has already shown that object A is selected, but the activity content panel is still stuck on object B.

[0005] (2) Visibility is not equal to current: old panels, hidden pop-ups and residual previews may still exist in the interface structure. The automatic program finds an attachment control with the same name in the entire page range. This control is located in the old panel, hidden pop-up or residual node.

[0006] (3) The occurrence of an event does not equate to causal attribution: Opening a window or completing a download only proves that the event has occurred, but does not prove that it was caused by the operation on the target object in this round. After clicking, the old preview exists in the interface; the program accepts the resource simply because it "sees the preview", without proving that the resource was added by the operation in this round.

[0007] (4) Path is not equal to bytes: The same path can be overwritten, replaced, or bypassed through a symbolic link. The file format, size, and content digest are all normal, but the file completely belongs to object B, but is subsequently recorded to object A.

[0008] (5) Entry verification does not equal continuous trust: When a file is used asynchronously by multiple consumers, any consumer may bypass the existing verification by reading it based solely on the path or historical state. The file association is correct during collection, but it is overwritten by the same path after being written to disk; the parsing, evaluation, display, or exporting programs continue to use it.

[0009] The common thread in these failures is that file integrity itself is not compromised; what is compromised is the evidence of the association between the object, operation, resource, and file. Simply verifying the format, path, size, or summary cannot definitively prove the file's original origin; merely verifying the selected state in the interface cannot overwrite the byte replacements made after the file was written to disk. Summary of the Invention

[0010] The technical problem to be solved by the present invention is to provide an asynchronous graphical interface object file association consistency verification method and system to address the shortcomings of the existing technology, and to solve the technical problems of existing graphical interface technology in providing evidence of association between objects, operations, resources and files, proving the source of files and overwriting byte replacements after they have been written to disk.

[0011] The present invention discloses an asynchronous graphical user interface object file association consistency verification method, the method comprising: Step 1: Obtain the graphical interface node G, target object selection condition K, controlled storage root directory D, and evidence chain version V; and form the object identity package O based on the graphical interface node G and target object selection condition K. Step 2: Based on the graphical interface node G, a unique active panel P is formed, and the object identity package O is bound to the unique active panel P to form a session identity package S; Step 3: Determine the unique source of operation U within the unique activity panel P; Step 4: Collect the resource set B before interaction and the resource set A after interaction, and compare the resource set B before interaction and the resource set A after interaction to obtain the unique new resource Rnew; Step 5: Based on the object identity packet O, session identity packet S, unique operation source U, and unique new resource Rnew, form the expected attachment context Cexpected; Based on the graphical interface node G, object identity package O, unique activity panel P, session identity package S, operation source U, unique newly added resource Rnew, and controlled storage root directory D, the actual attachment context Cobserved, file transfer evidence Etransfer, and file Efile are formed. The evidence chain version V compares the expected attachment context Cexpected and the actual attachment context Cobserved, and verifies the file transfer evidence Etransfer and the file Efile to form a pending record that is not visible to the consumer; Step Six: Based on the pending records, persist the official file Efile and activate the version to establish a unique, active, and trusted version; Step 7: Obtain the controlled consumer request Q, and perform a public verification on the unique activity trusted version based on the controlled consumer request Q to output a trusted consumption result.

[0012] To further improve this approach, in step one, the method for forming the object identity package O based on the graphical interface node G and the target object selection condition K is as follows: An interface snapshot is formed based on the graphical interface node G. Within the same interface snapshot, a list item corresponding to the target object selection condition K is obtained. The unique identifier, normalized display identifier, selection status, and snapshot identifier of the list item are read. Candidate deduplication is performed on the unique identifier, normalized display identifier, selection status, and snapshot identifier to form a relocatable descriptor targetItemLocator with an expiration date. The unique identifier, normalized display identifier, selected state, snapshot identifier, and relocatable descriptor targetItemLocator are packaged into an object identity package O.

[0013] Furthermore, in step two, the method for binding the object identity packet O to the unique activity panel P and forming the session identity packet S is as follows: The target object is relocated and verified using the relocatable descriptor targetItemLocator; Get the content of the activity panel. When the activity panel P contains the unique identifier of the target object, directly write the target object and the unique activity panel P into the stable identity core S_core. When the unique activity panel P is not directly identified, two bridging fields from different interface areas are combined to form a bridging result. When the bridging result is unique in the current interface snapshot, the target object, activity panel and bridging result are written to the stable identity core S_core, the message count, start and end content and timestamp of the target object are written to the variable state S_state, and the stable identity core S_core and the variable state S_state are combined to form the session identity packet S.

[0014] Furthermore, in step three, the method for determining the unique operation source U within the unique active panel P is as follows: Find the pickup control in the DOM, accessibility, or automation subtree corresponding to the unique active panel P; Filter out the pick-up controls that are invisible, unavailable, obscured, extend beyond the boundary of the unique active panel P, or belong to other panels; The resource ID is formed by using the native message, attachment, or control identifier within the unique activity panel P; a one-time operation ID is generated based on the resource ID, and a resource observer is registered before the interaction to form a pre-registered resource observer, an association token, and a mutually exclusive observation range; the resource ID, operation ID, pre-registered resource observer, association token, and mutually exclusive observation range are packaged into an operation source U.

[0015] Furthermore, in step four, the method for comparing the resource set B before the interaction and the resource set A after the interaction to obtain the unique newly added resource Rnew is as follows: Normalize the resource addresses, window handles, download tasks, or file event identifiers in the resource set B before interaction and the resource set A after interaction, and filter out resources with mismatched scopes, hidden resources, or invalid resources; calculate the difference between the normalized resource set B before interaction and the resource set A after interaction based on the normalized resource key, and use the difference as the unique newly added resource Rnew.

[0016] Furthermore, in step five, the method for forming the expected attachment context Cexpected based on the object identity packet O, session identity packet S, unique operation source U, and unique newly added resource Rnew is as follows: The stable fields in the unique newly added resource Rnew are normalized, and the resource fingerprint Fr is calculated based on the stable fields. The object identity packet O, session identity packet S, and unique operation source U are serialized according to a fixed field order and the field boundary ambiguity is eliminated by using a length prefix or equivalent method. The attachment context Cexpected is formed based on the fingerprint Fr, the object identity packet O, session identity packet S and unique operation source U after eliminating the field boundary ambiguity.

[0017] Furthermore, in step five, the method for forming the experimental attachment context Cobserved, file transfer evidence Etransfer, and file Efile based on the graphical interface node G, object identity packet O, unique activity panel P, session identity packet S, operation source U, unique newly added resource Rnew, and controlled storage root directory D is as follows: Relocate the object identity package O and the unique activity panel P, and retrieve all fields of J from the object identity package O; Based on the controlled read or download task bound to the unique new resource Rnew, the task writes the byte stream in the unique new resource Rnew into a temporary ordinary file T in the controlled directory D, and establishes a file transfer evidence Etransfer initial segment that overwrites the unique new resource Rnew to the temporary ordinary file T; Read all the actual current bytes of the temporary ordinary file T from the unique active panel P, calculate the digest H based on all the actual current bytes, and obtain the size L, file identifier fileIdentity and read count readTime; The object identity packet O, session identity packet S, operation source U, and resource fingerprint Fr are observed independently again to form a measured attachment context Cobserved. Based on the measured attachment context Cobserved and the file transfer evidence Etransfer initial segment, a file Efile is formed.

[0018] Furthermore, in step five, the method for comparing the expected attachment context Cexpected and the actual attachment context Cobserved, and verifying the file transfer evidence Etransfer and the file Efile to form a pending record invisible to the consumer, is as follows: Extract a first common verification projection Jexpected from the expected attachment context Cexpected, and extract a second common verification projection Jobserved from the measured attachment context Cobserved. Compare the corresponding fields in the first common verification projection Jexpected and the second common verification projection Jobserved. If the corresponding fields are consistent, it meets the expectation; if the corresponding fields are inconsistent, it does not meet the expectation. Perform equivalent persistence on the temporary ordinary file T, and then perform atomic promotion on the equivalently persisted temporary ordinary file T with an immutable filename within the same controlled file system; After the atomic boosting is performed, the temporary ordinary file T is reopened through the controlled root directory without following the symbolic link, and the final file Efile_final is formed from the same read handle of the temporary ordinary file T. Using the evidence chain version V as the comparison condition, a pending record using the final file Efile_final is written in the persistent state transaction.

[0019] Furthermore, in step six, the method for persisting the official file Efile and activating the version based on the pending records to establish a unique active trusted version is as follows: Retrieve the old activity record of the same object, and review the official file and the pending record without following symbolic links. After the review is passed, compare the old activity record and the pending record, switch the pending record to activity verification, switch the old activity record to invalid verification, and write the activity verification and invalid verification to the unique trusted version of the activity and the expiration time set.

[0020] A system applying the above-described asynchronous graphical user interface object file association consistency verification method, the system comprising, The object identity snapshot module is used to read the unique identifier, normalized display identifier, selection status, and snapshot identifier of the list item; The session binding module is used to bind the object identity package O to the unique activity panel P and form a session identity package S; The operation source binding module is used to determine the unique operation source U within the unique activity panel P; The preview binding module is used to collect the resource set B before interaction and the resource set A after interaction, and compare the resource set B before interaction and the resource set A after interaction to obtain the unique new resource Rnew; The document evidence module is used to form the measured attachment context Cobserved, file transfer evidence Etransfer, and file Efile based on the graphical interface node G, object identity packet O, unique activity panel P, session identity packet S, operation source U, unique newly added resource Rnew, and controlled storage root directory D. The persistent verification module is used to persist the official file Efile and activate the version based on the pending records to establish a unique active trusted version; The consumption verification module is used to perform a public verification of the unique activity trusted version based on the controlled consumer's request Q in order to output a trusted consumption result.

[0021] Beneficial effects The advantages of this invention are: 1. This invention ensures that the object, unique activity panel, current operation, and unique newly added resource must correspond continuously; even if the file format, size, and digest are normal, it will be rejected because the source chain is invalid, thereby suppressing initial attribution errors.

[0022] 2. This invention separates Cexpected and Cobserved. Etransfer assigns the only new resource to Efile. Trusted records are only activated when both common projection and file evidence pass, thereby suppressing resource-to-byte and persistence mismatches.

[0023] 3. This invention re-verifies the active version and the actual current bytes before each controlled consumer uses it; trust level failure renders the file and its derivatives that depend on the old version unreadable, and retains the staged rejection reason, thereby inhibiting the continued propagation of untrusted data.

[0024] 4. This invention sets up verification gates for two types of faults: "attribution error" and "content change", thereby reducing the risk of erroneous files being allowed to pass and continue to spread: the former is when a complete file is associated with an erroneous object, and the latter is when a correct file is replaced after persistence. Attached Figure Description

[0025] Figure 1 This is a flowchart of the asynchronous graphical user interface object file association consistency verification method of the present invention; Figure 2 This is a schematic diagram of the process of independent formation of dual-path evidence, common projection comparison, document evidence admission and continuous re-verification in the asynchronous graphical interface object file association consistency verification method of the present invention. Figure 3This is a sequence diagram of evidence formation, pending persistence, active version CAS switching, and pre-consumption verification in the asynchronous graphical interface object file association consistency verification method of the present invention. Figure 4 This is a compatible flowchart for the asynchronous graphical interface object file association consistency verification method of the present invention, which generates MANUAL records for historical files lacking AUTO source evidence and enters the subtype consumption re-verification. Figure 5 This is a modular schematic diagram of the asynchronous graphical interface object file association consistency verification system of the present invention; Figure 6 This is a schematic diagram illustrating the improvement of the asynchronous graphical interface object file association consistency verification method of the present invention compared to the prior art; Figure 7 This is a simplified flowchart of the asynchronous graphical user interface object file association consistency verification method of the present invention. Detailed Implementation

[0026] The present invention will be further described below with reference to embodiments, but this does not constitute any limitation on the present invention. Any limited modifications made by any person within the scope of the claims of the present invention are still within the scope of the claims of the present invention.

[0027] See Figures 1-6 The present invention provides an asynchronous graphical user interface object file association consistency verification method, such as... Figure 1 and Figure 7 As shown, the solution of this method is divided into three parts: steps one to four (i.e. Figure 1 (F1-F4) Establish the ownership chain between the object and the newly added resource; Steps five to six (i.e. Figure 1 Step F5-F6 in the process uses an independent evidence path to trace the resource down to the actual file bytes, and after comparison, forms a unique and trustworthy activity record; Step Seven (i.e. Figure 1 F7 in the code extends established trust to every downstream use. The output of the previous section is the mandatory input of the next section.

[0028] The continuous data flow is as follows: Object O → Unique activity panel P and session S → Operation source U → Unique new resource Rnew → Cexpected and independently formed Cobserved, Etransfer, Efile → Activity Record → Controlled consumption result.

[0029] First paragraph | Prove "who the resource originally belonged to" (F1-F4): Fix the target object in the same snapshot, bind the object to a unique active panel; determine the source of the operation only within this panel; compare the set of observable resources before and after the interaction, and only accept the unique new resource associated with this operation.

[0030] The second paragraph | Proving "which byte was written to disk" (F5-F6): One evidence path is formed by the object, session, operation and new resource to form Cexpected, and the other path is formed independently by the current interface, read-only event, actual resource and file byte after retrieval to form Cobserved, Etransfer and Efile; only when the common verification fields are consistent and the file evidence passes, is the unique trusted version persisted and activated.

[0031] The third paragraph | Prove that "the same copy will still be used in the future" (F7): Controlled consumers such as parsing, displaying, evaluating, exporting, and synchronizing recheck the active version, object, controlled location, file identity, and actual current bytes before each use; trust level failures immediately reject use and make derived results that depend on the old version unreadable.

[0032] The above three sections are not checklists that can be arbitrarily separated: Without object-panel binding, the newly added resource cannot prove who it belongs to; without attribution for this operation, the file summary can only prove that "a certain file" is complete; without independent byte binding and activity record, there is no reliable benchmark for consumption verification; without pre-consumption verification, the trust in the collection stage cannot cover the replacement after disk write.

[0033] The external inputs to this method include the graphical interface root node G, the target object selection criteria K, the controlled storage root directory D, and the evidence chain version V. The following steps S101-S110 constitute the complete technical flow; each step is executed only if the previous step's successful output exists. When a stage error E_stage occurs, intermediate data must not be marked as trusted records and must be rejected, cleaned, or isolated according to the failure type.

[0034] S101: Form object identity packet O (corresponding to...) Figure 1 (F1 in the middle) Input: The root node G of the graphical interface and the selection criteria K for the target object.

[0035] deal with: (1) Obtain the list item corresponding to K within the same interface snapshot, and read the object's unique identifier, normalized display identifier, selected status, and snapshot identifier.

[0036] (2) Remove duplicates from candidates and check for identity conflicts; form a targetItemLocator with an expiration date based on stable attributes and structural paths.

[0037] Output: Only output the object identity package O if the target candidate is unique, the identity fields are consistent, and a targetItemLocator can be formed.

[0038] Failure: Output E_object and terminate the round if target not found, multiple candidates exist, unique identifier is missing, identity field conflict, or descriptor cannot be uniquely relocated in G.

[0039] S102: Bind the unique activity panel P and generate a session identity packet S (corresponding to...) Figure 1 (F2 in the middle) Input: The graphical interface root node G and the object identity package O.

[0040] deal with: (1) Use O.targetItemLocator to relocate and verify the target object, and then perform selection and bounded wait.

[0041] (2) Target list items must be selected uniquely, and the activity content panel must be unique. When the panel contains a unique object identifier, it must be consistent with O.objectId.

[0042] (3) When the panel does not have a direct identifier, at least two bridging fields from different interface areas should be used, and their combination should be unique in the current snapshot; failure will occur if any field conflicts.

[0043] (4) Write the object, panel and bridging result to the stable identity core S_core; write the message count, beginning and end content and timestamp to the variable state S_state.

[0044] Output: Activity panel handle P and session identity packet S.

[0045] Failure: If relocation fails, waits for a timeout, has zero or multiple panels, has insufficient bridging evidence, or is not unique or conflicting, output E_panel and terminate.

[0046] S103: Determine the unique source of operation U within the activity panel (corresponding to...) Figure 1 (F3 in the middle) Input: Activity panel handle P and session identity packet S.

[0047] deal with: (1) Only search for the pick-up control in the DOM, accessibility or automation subtree corresponding to P.

[0048] (2) Filter candidates that are invisible, unavailable, occluded, outside the P boundary, or belong to other panels; candidates must be unique.

[0049] (3) The resource ID sourceId should be formed by using native message, attachment or control identifiers as a priority; if native identifiers are not available, it should be formed by stable structure, quantitative position and standardized semantic determinism.

[0050] (4) Generate a one-time selection ID operationId and register a resource observer before interaction to form observerRegistrationId, correlationToken and exclusiveScope.

[0051] Output: Operation source U={controlHandle, sourceId, operationId, observerRegistrationId, correlationToken, exclusiveScope, semantics}.

[0052] Failure: zero candidates, more than one, hit test failed, deterministic sourceId could not be formed, or E_source could not be output and terminated before the interaction was registered.

[0053] S104: Collect the resource sets before and after the interaction and execute the pre-defined interaction (corresponding to...) Figure 1 (The first half of F4 in the middle) Input: graphical interface root node G, object identity packet O, session identity packet S, activity panel handle P, and operation source U.

[0054] deal with: (1) Press U.exclusiveScope to obtain the bounded mutual exclusion operation gate and prevent other automatic pickup actions in the same session.

[0055] (2) Confirm that the observer has been pre-registered, save S_core and collect the resource set B before interaction; the descriptor records panelScope, observer identifier, event sequence and available source evidence.

[0056] (3) Perform a scheduled pickup interaction on U.controlHandle and collect the resource set A after the interaction after a bounded wait.

[0057] (4) Use G and O.targetItemLocator to retrieve P′ and S′ again; only S_core is required to remain consistent, and S_state is allowed to be updated due to the current operation.

[0058] Output: When S_core is consistent, P′ is still unique, and the states of the mutex gates and observers are valid, output P′, S′, B, A, and U with the completion status.

[0059] Failure: When the stable identity core changes, the activity panel is no longer unique, other resource generation actions enter the exclusiveScope, the observer is interrupted, the operationId becomes invalid, or the interaction fails, output E_interaction, close the operationId and terminate.

[0060] S105: Acquire the unique newly added resource Rnew (corresponding to Figure 1 (Second half of F4) Input: Post-interaction activity panel P′, operation source U, pre-interaction resource descriptor set B, and post-interaction resource descriptor set A.

[0061] deal with: (1) Normalize the resource addresses, window handles, download tasks or file event identifiers in B and A, and filter out resources with incompatible scopes, hidden or invalid resources.

[0062] (2) Calculate the difference Δ=A according to the normalized resource key. B.

[0063] (3) Priority should be given to the request initiator, download task, opener or event token of the candidate resource that directly corresponds to operationId / correlationToken.

[0064] (4) When the platform does not have a directly associated field, it must simultaneously satisfy the following conditions: observer pre-registration, mutex gate is valid throughout the process, event is located in the current time window and there are no other resource generation actions.

[0065] Output: Only if the number of candidates passing through the source gate is one, output Rnew={resourceDescriptor, associationMode, originEvidence}.

[0066] Failure: If there are zero candidates for the source gate, output either E_no_new_resource or E_origin_unprovable, depending on the situation; if there are more than one, output E_resource_ambiguous. Under no circumstances should resources be guessed or arbitrarily selected based solely on time approximation.

[0067] S106: Generate the expected attachment context Cexpected (corresponding to...) Figure 1 (First half of F5) Input: Object identity packet O, post-interaction session identity packet S′, operation source U, unique newly added resource Rnew, and evidence chain version V.

[0068] deal with: (1) Normalize the stable fields of Rnew and calculate the resource fingerprint Fr.

[0069] (2) Serialize objectId, S_core, panelId, sourceId, operationId, observerRegistrationId, correlationToken, exclusiveScope, associationMode, originEvidenceDigest, resourceFingerprint and V in a fixed field order; eliminate field boundary ambiguity by using length prefix or equivalent methods.

[0070] Output: Expected attachment context C.

[0071] Failure: Output E_context and terminate if any necessary field is missing, field cannot be normalized, operationId is expired, or V is not supported.

[0072] S107: Obtain the file and generate Cobserved, Etransfer, and Efile_temp (corresponding to...) Figure 1 (Second half of F5) Inputs: Graph interface root node G, object identity packet O, activity panel P′, session identity packet S′, operation source U, unique new resource Rnew, and controlled storage root directory D. Cexpected is not used as input for the value of Cobserved.

[0073] deal with: (1) Relocate the object and unique activity panel; retrieve all fields of J from the current interface, read-only operation events, mutual exclusion scope audit records and actual resource descriptors, where correlationToken and exclusiveScope are read or recalculated independently by the read-only audit records in this round, and the corresponding values ​​in Cexpected are not read.

[0074] (2) Based on the controlled read or download task bound to Rnew, write the byte stream of the resource into a temporary ordinary file T in the controlled directory D, and create an Etransfer initial segment that overwrites Rnew→T; check the path level by level and reject symbolic links, path out of bounds and non-ordinary files.

[0075] (3) Read all the actual current bytes of T from the same read handle, calculate the digest H, and obtain the size L, fileIdentity and readTime; failure occurs if the identity or size changes during the reading process.

[0076] (4) After taking the object, observe the object, stable session, operation source and resource fingerprint again to form Cobserved; the observation path is isolated from the construction path of Cexpected and the source audit reference is retained.

[0077] Output: Etransfer initial segment, Efile_temp={canonicalPath_T, fileType, L, H, fileIdentity_T, readTime} and the measured attachment context Cobserved.

[0078] Failure: If an independent observation field is missing, the stable identity is inconsistent before and after the file is retrieved, Etransfer cannot associate Rnew with the actual file, the path or file type is non-compliant, the read fails, the fileIdentity changes, or the resource is inconsistent with the operationId, output E_file and delete or isolate T.

[0079] S108: Perform evidence comparison and create an invisible pending record (corresponding to) Figure 1 (Second half of F5, first half of F6) Input: Cexpected from the output of S106, Cobserved, Etransfer initial segment, and Efile_temp from the output of S107, and the old active record version expectedRecordVersion read consistently from persistent state storage.

[0080] deal with: (1) S108A (F5 comparison gate): Extract the common verification projections Jexpected and Jobserved from Cexpected and Cobserved respectively; compare the context only if the corresponding fields are consistent, and separately check the fileIdentity_T, size and current summary in the initial Etransfer segment and Efile_temp. This rule cannot be replaced by the equality of all fields of the two context objects.

[0081] The comparison results include two types: comparison pass and comparison fail. When the corresponding fields of the first co-validation projection Jexpected and the second co-validation projection Jobserved are consistent, the context comparison is considered to pass, indicating that the expected attachment context and the actual attachment context are consistent in their association on the co-validation projection, which meets expectations. When the corresponding fields of Jexpected and Jobserved are inconsistent, the context comparison is considered to fail, indicating that the actual observed object-session-operation-resource association is inconsistent with expectations, and a trusted verification result should not be formed or activated.

[0082] (2) S108B (F6 Persistence Gate): Perform flush / fsync or equivalent persistence on T, and then atomically promote it with an immutable filename within the same controlled file system.

[0083] (3) After the atomic promotion, the formal immutable file is reopened through the controlled root directory without following the symbolic link; canonicalPath_final, fileIdentity_final, L, H and readTime are obtained from the same read handle, and L and H are required to be consistent with Efile_temp, and Efile_final is formed accordingly; at the same time, the transfer segment T→formal immutable file in Etransfer is completed.

[0084] (4) Using expectedRecordVersion as the comparison condition, write VERIFIED_PENDING records using Efile_final in the persistent state transaction; this state is not visible to consumers. When the database fails, orphan files are registered, and the recovery task scans for orphan files and incomplete records.

[0085] (5) File systems and databases do not advocate sharing physical transactions; logical atomic visibility is achieved through immutable files, record states, and access gates.

[0086] Output: Record_pending includes at least objectId, evidenceMethod=AUTO, Cexpected or its normalized summary, Cobserved or its normalized summary, J and comparison receipt, complete Etransfer, Efile_final, originEvidenceRef, evidence chain version V, recordLifecycleState=VERIFIED_PENDING, recordVersion, expectedRecordVersion, and createdAt; Record.Efile explicitly points to Efile_final.

[0087] Failures: New versions must not be activated if there is inconsistency in common projection, invalid transfer binding or file evidence, atomic promotion failure, database write failure, or version comparison conflict; temporary files, orphan files, and pending records are deleted or isolated by the compensation process.

[0088] S109: Event version switching and derived data invalidation (corresponding) Figure 1 (Second half of F6) Input: Record_pending passed by S108, old active Record of the same object, expectedRecordVersion, and a set of derived relations with derivedFromRecordVersion.

[0089] deal with: (1) Before activation, verify the fileIdentity, size and digest of the official file and Record_pending.Efile without following symbolic links; after verification, compare expectedRecordVersion in the same persistent state transaction, switch the new Record to ACTIVE_VERIFIED and switch the old Record to INACTIVE_VERIFIED.

[0090] (2) Simultaneously write activeRecordVersion and failure event I. All derived results must satisfy derivedFromRecordVersion=activeRecordVersion when read.

[0091] (3) After a transaction is committed, old derivatives can be deleted or isolated asynchronously; if cleanup fails, the version gate will still make the old results unreadable and enter the retry or manual isolation queue.

[0092] Output: New activity record, activeRecordVersion, and failure event set I.

[0093] fail: (1) When the formal document review, version comparison, transaction switching or failure event writing fails, the new version shall not be activated.

[0094] (2) Physical cleanup failure does not roll back the version gate, but records E_invalidation and continues to reject old derived results.

[0095] S110: The public validator performs pre-consumption verification (corresponding to...) Figure 1 Medium F7) Input: Consumer request Q = {objectId, recordVersion, purpose, consumerId, capabilityToken}.

[0096] deal with: (1) All controlled consumers submit Q to the public validator and do not directly obtain the raw path.

[0097] (2) Verify consumerId, capabilityToken, object, request version and purpose.

[0098] (3) Read the active record and verify ACTIVE_VERIFIED, activeRecordVersion, evidenceMethod, evidence chain version, and object. AUTO records must also have valid two-sided contextual evidence, a passed J comparison receipt, Etransfer, and Efile; MANUAL records must have Cmanual, a manual verification audit field, and Efile. Derived results must also verify derivedFromRecordVersion.

[0099] (4) Reopen Record.Efile.canonicalPath without following the symbolic link, obtain the current fileIdentity from the same read handle to be returned and calculate Hnow, and compare it with the fileIdentity and H in Record.Efile.

[0100] Output: (1) Returns the same read handle reset to the starting position, the corresponding controlled byte stream, or a derived result generated based on that byte stream.

[0101] (2) At the same time, a receipt for this consumption verification will be generated.

[0102] fail: (1) Request-level failure E_request: Parameter, object, version, purpose, permission or compatibility policy error; only reject and audit, do not change the Record.

[0103] (2) Transient failure E_transient: lock, resource busy or temporary I / O error; reject this access and retry within bounds, without immediately and permanently invalidating the Record.

[0104] (3) Trust level failure E_trust: necessary context is missing, state is corrupted, path is out of bounds, symbolic link, fileIdentity changes or digest is inconsistent; convert Record to INVALID and make dependent derivatives unreadable.

[0105] F1-F7 are mandatory admission conditions for S101-S110, with the unique correspondence as follows: F1=S101; F2=S102; F3=S103; F4=S104-S105; F5=S106-S107 and S108A; F6=S108B-S109; F7=S110. F5 is responsible for independently forming dual-path evidence and performing common projection and current document fact comparison; F6 is responsible for pending persistence, active version switching, and derived version gates; and F7 is responsible for pre-use subtyping verification for each controlled consumer.

[0106] like Figure 1 and Figure 2 As shown, the rules for common failures, retries, concurrency, and idempotency are: Failure latch: If any step fails, trusted output cannot be passed to the next step; temporary files and some records are deleted or isolated, and E_stage is logged.

[0107] Retry: Identity, panel, and resource baselines must be re-collected from S101, and new operationId and correlationToken must be generated; handles, differences, or temporary files from failed rounds must not be reused.

[0108] Concurrency: S102-S108 sets bounded mutual exclusion by object and S_core; exclusiveScope prevents other resource generation actions in the same session.

[0109] Idempotency: S108-S109 Implement unique constraints or compare and exchange based on object identifier, expectedRecordVersion, recordVersion, V, and H; different contexts must not override each other.

[0110] Invalidation: Records are only converted to INVALID upon trust level failure. Physical cleanup can be postponed, but lifecycle states and derived version gates must immediately render the invalidated data unreadable.

[0111] Recovery: The system scans for temporary files, orphan files, VERIFIED_PENDING records, and incomplete invalid events; after successful re-verification, the system continues to commit, while the remaining items are isolated and reclaimed.

[0112] like Figure 4 As shown, the alternative confirmation branch for historical files: Historical documents lack the automated source evidence generated in S101-S106 and cannot be disguised as main process products or have S, U, and Fr added. This branch is only an optional compatible implementation: Records are identified by evidenceMethod=MANUAL, use an independent necessary field pattern, and only enter the type verification in S110 after going through the pending, version comparison, and activity switching processes equivalent to S108-S109.

[0113] S201-S202: Identify, preview under controlled conditions, and confirm explicitly Input: historical files, existing object records, and authenticated user sessions.

[0114] Processing: Detect whether automatic source evidence is missing; display the file in a controlled preview without exposing the raw path to ordinary consumers, and have certified users explicitly select the corresponding object and confirm the technical association.

[0115] Output: Clear and unambiguous confirmation intent, authentication subject, and status of the record to be created.

[0116] Failure: Remain unavailable and do not automatically downgrade to allow if there is no confirmation, invalid authentication, or object ambiguity.

[0117] S203-S204: Create manual evidence records and integrate them into the typing verification process. Input: Confirmation intent, object identity, authentication subject, actual current bytes of the file, and previous active version.

[0118] Processing: A formal Efile_final is formed using the same read handle that does not follow symbolic links, and a Cmanual is formed based on its current digest, recording the object, acknowledgment subject, unique acknowledgment number, acknowledgment time with time zone, and manualEvidenceSchemaVersion; a pending record is formed through MANUAL persistence equivalent to S108B, and activated after comparison with version S109. S110 reviews the object, active version, controlled path, fileIdentity, and current digest according to the MANUAL field schema.

[0119] Output: If successful, an ACTIVE_VERIFIED MANUAL Record is created; if unsuccessful, the record is rejected and isolated.

[0120] Failure: Manual verification only proves the manually established object-file association, not the original GUI automatic source.

[0121] Replaceable implementations and their mounting locations: In S101, an O can be formed from the DOM, accessibility tree, or application automation bridging. OCR can only capture display identifiers; an O can only be formed when combined with a uniquely relocatable stable object identifier or composite descriptor.

[0122] In S102, P can be determined by the active attribute, window level, focus, and visible area. In S104-S105, B and A can come from the preview window, network resources, download tasks, or file system events; the digest algorithm and controlled storage implementation in S107 can be replaced.

[0123] Any replacement must output data with the same name and meet the same admission conditions. The continuity between object-panel binding, current round resource attribution, current byte binding, and pre-consumption verification must not be deleted.

[0124] This invention does not claim novelty for any single point in object identification, GUI differentiation, file digest, or data invalidation. Its protection center is a continuous combination of F2→F3→F4→F5→F6→F7: First, the object is bound to a unique activity panel, and the operation is limited to that panel; then, the unique newly added resource is determined by the difference in resource sets before and after the operation and the source association gate; subsequently, Cexpected and Cobserved are formed from different evidence paths, and implemented to the actual current byte using Etransfer and Efile; only when the common projection is consistent and the file evidence passes is a unique, trustworthy version of the activity visible to the consumer formed; finally, each controlled consumer verifies the activity version, object, file identity, and current digest before use. The output of the previous stage constitutes the mandatory input of the next stage; therefore, this combination is not a parallel concatenation of "GUI positioning + download + hash". Specific deduplication and relocation methods, specific association patterns, crash recovery, and authentication details of F1 can be considered as subordinate limitations or embodiments.

[0125] like Figure 5 As shown, an asynchronous graphical user interface object file association consistency verification system is provided, which includes: Object Identity Snapshot Module 110: Obtains the object's unique identifier, display identifier, selection status, and deduplication evidence from snapshots of the same interface.

[0126] Session Binding Module 120: Select an object and confirm a unique activity content panel, forming bridging evidence through panel identifiers, normalized display identifiers, session anchors, or beginning and end content identifiers.

[0127] Operation Source Binding Module 130: Only searches for attachment-related controls within the verified panel and generates or obtains a stable operation source identifier.

[0128] Preview Binding Module 140: Records the set of observable resources before and after the interaction, performs set difference and source association gates, and only accepts the unique new resource that passes the attribution rule.

[0129] File Evidence Module 150: Binds the controlled task corresponding to the unique newly added resource to the actual disk file, verifies the path and file identity, and reads the actual current bytes to form a digest.

[0130] Persistent verification module 160: Compares expected and actual evidence, writes to file association records, and manages active file versions.

[0131] Consumption verification module 170: Re-verifies the current record and current bytes before each use, such as parsing, displaying, evaluating, exporting, and synchronizing.

[0132] Isolation Module 180: Reject writes or consumption based on failure type; only trust-level failures render activity logs and related derived results unreadable.

[0133] Historical Document Manual Verification Module 280: Provides controlled previews for historical documents lacking automatic source evidence, records the manual verification context, and connects to the same consumer verification interface; this module must not create session, operation, or resource source fields.

[0134] The following are specific embodiments provided by the present invention: This embodiment employs a universal data management workbench that is independent of any specific website, brand, or business layout. The client graphical interface 200 includes an object list 210, an asynchronously updated content panel 220, resource acquisition controls 230, and observable resources 240; the system 100 generates evidence through structured attributes, accessibility information, event logs, or automated bridging layers.

[0135] When processing object A, the system first verifies the binding between object A and the unique activity panel, then restricts resource acquisition operations to that panel, accepting only the unique newly added resource from the current source gate. After retrieval, a test context, transfer evidence, and document evidence are independently formed. After comparison and version activation, consumers can only verify and obtain the document before use, including parsing, displaying, evaluating, exporting, and synchronizing. Failure at any stage will result in no consumable trusted record being generated.

[0136] (1) Binding objects to activity panels: In a general data management workbench, each item in the object list 210 contains a data-object-id, a display name, and a selected attribute; the content panel 220 contains a panel-id and an optional data-object-id. Module 110 reads the above fields in the same snapshot and forms a targetItemLocator with the data-object-id, stable attributes, structure path, and snapshot validity period.

[0137] Module 120 uses this descriptor to relocate and verify the target before performing clicks and polling. P and S are only output if the object-id is directly consistent, or if at least two independent bridging fields are unique and consistent; a conflict in any field results in failure. The message count and the beginning and end of the message are written to S_state, not as constant fields in S_core.

[0138] (2) Difference between operation source and resource set: Module 130 calls querySelectorAll, accessibility child node query, or equivalent interface with the container corresponding to P as the root to filter out controls with the role of buttons or links, the semantic meaning of "get data", and that are actually visible, usable, and unobstructed. When there is only one candidate, the sourceId is formed by the native attachment identifier first; otherwise, the sourceId is calculated based on S_core, stable structure, quantized position, and normalized text.

[0139] Before clicking, register a resource observer and obtain a mutual exclusion gate. Module 140 collects resource descriptors before and after the operation, and performs set difference based on normalized fields such as URL, window handle, download task ID, panelScope, request initiator, opener, or event token.

[0140] The unique difference candidate must also be directly associated with operationId / correlationToken; if the platform does not have a direct field, it must simultaneously satisfy the following conditions: observer pre-registration, mutex validity, current timing window, and no other resource generation actions; otherwise, output E_origin_unprovable.

[0141] (3) Current bytes of the file and persistence: Module 150, based on the controlled task bound to Rnew, writes the byte stream to an exclusive temporary file T under D and forms Etransfer. The path components from D to T are checked step-by-step, rejecting symbolic links, out-of-bounds paths, and non-ordinary files; pre-read checks, block digests, size accumulation, and post-read checks are performed on the same file handle. After file promotion, the system reopens the actual file through the controlled root directory and re-verifies fileIdentity, size, and digest.

[0142] Object, panel, and session fields in Cobserved are re-observed by G and O.targetItemLocator; source and resource fields are recalculated from read-only event logs and actual resources, and copying from Cexpected is prohibited.

[0143] Module 160 explicitly receives Cexpected, Cobserved, Etransfer initial segment, Efile_temp, and expectedRecordVersion. T is promoted to a formal immutable file only when Jexpected = Jobserved and the temporary file evidence passes; subsequently, the formal file is reopened to form Efile_final, Etransfer is completed, and only the VERIFIED_PENDING record is written as Efile_final. The record is only visible to consumers after being switched to ACTIVE_VERIFIED via version comparison.

[0144] (4) Multi-consumer and derived failure examples: The file parsing consumer 271, display consumer 272, state calculation consumer 273, evaluation consumer 274, export consumer 275, and synchronization consumer 276 all call the getVerifiedArtifact(Q) interface of module 170. This interface verifies the consumer, object, purpose, and requested version, and requires the Record to be ACTIVE_VERIFIED; the derived result must also come from the current activeRecordVersion.

[0145] The interface does not return the raw path. Instead, it reopens Record.Efile.canonicalPath in the current request and compares the current fileIdentity and Hnow with the baseline value in Record.Efile using the same read handle to be returned. Request errors are only rejected and audited; transient errors are closed and retried; trust-level failures convert Record to INVALID and make dependent derived items unreadable.

[0146] (5) Retrying on failure and concurrency: When S104 generates E_interaction, S105 generates E_resource_ambiguous, or S108 generates E_persist, the operationId for this round is closed, T is deleted or isolated, and Rnew that can be reused in subsequent rounds must not be retained. Retry must start from S101, re-register the observer and collect new B.

[0147] When two threads process the same objectId simultaneously, only the one that first acquires object-level mutual exclusion can enter S103; the persistence layer then uses expectedRecordVersion to perform comparison and swap.

[0148] The new record is only visible after the active version switch and the invalidation event are committed within the same transaction. When derived data cleanup fails, the version gate continues to reject old data and records E_invalidation; after a bounded retry fails, manual isolation is initiated.

[0149] (5) Historical documents: For files that existed before the upgrade but lack automatic source evidence, the system displays "Pending manual confirmation" instead of "Verified". After an authenticated user confirms the object in the controlled preview, module 280 forms Cmanual and formal Efile_final with the same read handle, and establishes a Record with evidenceMethod=MANUAL through MANUAL persistence equivalent to S108B, S109 version comparison, and activity switching; it does not contain forged session, operationId, or resource fingerprints. The consumer verifies the object, activity version, controlled path, fileIdentity, and current digest according to the MANUAL field pattern.

[0150] The above description is only a preferred embodiment of the present invention. It should be noted that those skilled in the art can make several modifications and improvements without departing from the structure of the present invention, and these will not affect the effectiveness of the implementation of the present invention or the practicality of the patent.

Claims

1. A method for verifying the consistency of asynchronous graphical interface object file associations, comprising: The method includes, Step 1: Obtain the graphical interface node G, target object selection condition K, controlled storage root directory D, and evidence chain version V; and form the object identity package O based on the graphical interface node G and target object selection condition K. Step 2: Based on the graphical interface node G, a unique active panel P is formed, and the object identity package O is bound to the unique active panel P to form a session identity package S; Step 3: Determine the unique source of operation U within the unique activity panel P; Step 4: Collect the resource set B before interaction and the resource set A after interaction, and compare the resource set B before interaction and the resource set A after interaction to obtain the unique new resource Rnew; Step 5: Based on the object identity packet O, session identity packet S, unique operation source U, and unique new resource Rnew, form the expected attachment context Cexpected; Based on the graphical interface node G, object identity package O, unique activity panel P, session identity package S, operation source U, unique newly added resource Rnew, and controlled storage root directory D, the actual attachment context Cobserved, file transfer evidence Etransfer, and file Efile are formed. The evidence chain version V compares the expected attachment context Cexpected and the actual attachment context Cobserved, and verifies the file transfer evidence Etransfer and the file Efile to form a pending record that is not visible to the consumer; Step Six: Based on the pending records, persist the official file Efile and activate the version to establish a unique, active, and trusted version; Step 7: Obtain the controlled consumer request Q, and perform a public verification on the unique activity trusted version based on the controlled consumer request Q to output a trusted consumption result.

2. The method of claim 1, wherein the method further comprises: In step one, the method for forming the object identity package O based on the graphical interface node G and the target object selection condition K is as follows: An interface snapshot is formed based on the graphical interface node G. Within the same interface snapshot, a list item corresponding to the target object selection condition K is obtained. The unique identifier, normalized display identifier, selection status, and snapshot identifier of the list item are read. Candidate deduplication is performed on the unique identifier, normalized display identifier, selection status, and snapshot identifier to form a relocatable descriptor targetItemLocator with an expiration date. The unique identifier, normalized display identifier, selected state, snapshot identifier, and relocatable descriptor targetItemLocator are packaged into an object identity package O.

3. The method of claim 2, wherein the method further comprises: In step two, the method for binding the object identity packet O to the unique activity panel P and forming the session identity packet S is as follows: The target object is relocated and verified using the relocatable descriptor targetItemLocator; Get the content of the activity panel. When the activity panel P contains the unique identifier of the target object, directly write the target object and the unique activity panel P into the stable identity core S_core. When the unique activity panel P is not directly identified, two bridging fields from different interface areas are combined to form a bridging result. When the bridging result is unique in the current interface snapshot, the target object, activity panel and bridging result are written to the stable identity core S_core, the message count, start and end content and timestamp of the target object are written to the variable state S_state, and the stable identity core S_core and the variable state S_state are combined to form the session identity packet S.

4. The method of claim 1, wherein the method further comprises: In step three, the method for determining the unique operation source U within the unique active panel P is as follows: Find the pickup control in the DOM, accessibility, or automation subtree corresponding to the unique active panel P; Filter out the pick-up controls that are invisible, unavailable, obscured, extend beyond the boundary of the unique active panel P, or belong to other panels; The resource ID is formed by using the native message, attachment, or control identifier within the unique activity panel P; a one-time operation ID is generated based on the resource ID, and a resource observer is registered before the interaction to form a pre-registered resource observer, an association token, and a mutually exclusive observation range; the resource ID, operation ID, pre-registered resource observer, association token, and mutually exclusive observation range are packaged into an operation source U.

5. The method of claim 1, wherein the method further comprises: In step four, the method for comparing the resource set B before the interaction and the resource set A after the interaction to obtain the unique newly added resource Rnew is as follows: Normalize the resource addresses, window handles, download tasks, or file event identifiers in the resource set B before interaction and the resource set A after interaction, and filter out resources with mismatched scopes, hidden resources, or invalid resources; calculate the difference between the normalized resource set B before interaction and the resource set A after interaction based on the normalized resource key, and use the difference as the unique newly added resource Rnew.

6. The method of claim 5, wherein the method further comprises: In step five, the method for forming the expected attachment context Cexpected based on the object identity packet O, session identity packet S, unique operation source U, and unique newly added resource Rnew is as follows: The stable fields in the unique newly added resource Rnew are normalized, and the resource fingerprint Fr is calculated based on the stable fields. The object identity packet O, session identity packet S, and unique operation source U are serialized according to a fixed field order and the field boundary ambiguity is eliminated by using a length prefix or equivalent method. The attachment context Cexpected is formed based on the fingerprint Fr, the object identity packet O, session identity packet S and unique operation source U after eliminating the field boundary ambiguity.

7. The method of claim 1, wherein the method further comprises: determining whether the asynchronous GUI object file association is consistent with a second asynchronous GUI object file association. In step five, the method for forming the experimental attachment context Cobserved, file transfer evidence Etransfer, and file Efile based on the graphical interface node G, object identity packet O, unique activity panel P, session identity packet S, operation source U, unique newly added resource Rnew, and controlled storage root directory D is as follows: ​ Relocate the object identity package O and the unique activity panel P, and retrieve all fields of J from the object identity package O; Based on the controlled read or download task bound to the unique new resource Rnew, the task writes the byte stream in the unique new resource Rnew into a temporary ordinary file T in the controlled directory D, and establishes a file transfer evidence Etransfer initial segment that overwrites the unique new resource Rnew to the temporary ordinary file T; Read all the actual current bytes of the temporary ordinary file T from the unique active panel P, calculate the digest H based on all the actual current bytes, and obtain the size L, file identifier fileIdentity and read count readTime; The object identity packet O, session identity packet S, operation source U, and resource fingerprint Fr are observed independently again to form a measured attachment context Cobserved. Based on the measured attachment context Cobserved and the file transfer evidence Etransfer initial segment, a file Efile is formed.

8. The asynchronous graphical user interface object file association consistency verification method according to claim 7, characterized in that, In step five, the method for comparing the expected attachment context Cexpected and the actual attachment context Cobserved, and verifying the file transfer evidence Etransfer and the file Efile to form a pending record invisible to the consumer is as follows: Extract a first common verification projection Jexpected from the expected attachment context Cexpected, and extract a second common verification projection Jobserved from the measured attachment context Cobserved. Compare the corresponding fields in the first common verification projection Jexpected and the second common verification projection Jobserved. If the corresponding fields are consistent, it meets the expectation; if the corresponding fields are inconsistent, it does not meet the expectation. Perform equivalent persistence on the temporary ordinary file T, and then perform atomic promotion on the equivalently persisted temporary ordinary file T with an immutable filename within the same controlled file system; After the atomic boosting is performed, the temporary ordinary file T is reopened through the controlled root directory without following the symbolic link, and the final file Efile_final is formed from the same read handle of the temporary ordinary file T. Using the evidence chain version V as the comparison condition, a pending record using the final file Efile_final is written in the persistent state transaction.

9. The asynchronous graphical user interface object file association consistency verification method according to claim 1, characterized in that, In step six, the method for persisting the official file Efile and activating the version based on the pending records to establish a unique active trusted version is as follows: Retrieve the old activity record of the same object, and review the official document and the pending record without following symbolic links. After the review is passed, compare the old activity record and the pending record, and switch the pending record to activity verification. Switch the old activity record to invalid verification, and simultaneously write the activity verification and invalid verification into the unique activity trusted version and expiration time set.

10. A system applying the asynchronous graphical user interface object file association consistency verification method according to any one of claims 1-9, characterized in that, The system includes, The object identity snapshot module is used to read the unique identifier, normalized display identifier, selection status, and snapshot identifier of the list item; The session binding module is used to bind the object identity package O to the unique activity panel P and form a session identity package S; The operation source binding module is used to determine the unique operation source U within the unique activity panel P; The preview binding module is used to collect the resource set B before interaction and the resource set A after interaction, and compare the resource set B before interaction and the resource set A after interaction to obtain the unique new resource Rnew; The document evidence module is used to form the measured attachment context Cobserved, file transfer evidence Etransfer, and file Efile based on the graphical interface node G, object identity packet O, unique activity panel P, session identity packet S, operation source U, unique newly added resource Rnew, and controlled storage root directory D. The persistent verification module is used to persist the official file Efile and activate the version based on the pending records to establish a unique active trusted version; The consumption verification module is used to perform a public verification of the unique activity trusted version based on the controlled consumer's request Q in order to output a trusted consumption result.