A smart governance execution method, platform, equipment, storage medium, and computer program product based on a unified task object and internal and external dual closed loops.

By generating unified event objects and an intelligent governance execution method with internal and external double closed loops, the problem of inconsistent event identities and statuses between different systems is solved, unified result verification and automatic updates of internal tasks by external feedback are achieved, and the costs of redundant development and interface integration are reduced.

CN123118017APending Publication Date: 2026-11-17丁万万
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611280336.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-22
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

The fact that different terminals and business systems store records of the same matter separately leads to inconsistencies in identity and status. The different formats of results returned by personnel, business systems, smart devices, and executing smart agents result in inconsistent status calculations, inconsistencies between external progress and internal execution results, and the inability of external feedback to automatically update internal tasks and results. This also leads to high costs of redundant development across different industry systems.

Method used

By generating unified event objects and an intelligent governance execution method with internal and external double closed loops, heterogeneous event objects are received and source event objects are generated, aggregated into unified event objects, an internal task graph is generated based on the governance template, converted into standardized node result vouchers, binding relationships are verified, the status of authoritative events is calculated, and internal tasks and results are updated through external feedback mapping.

Benefits of technology

It achieves consistency in the identity and status of items across different systems, unifies result verification, automatically updates internal tasks with external feedback, and reduces the cost of redundant development and interface integration.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123118017A_ABST
    Figure CN123118017A_ABST
Patent Text Reader

Abstract

This invention relates to computer workflow orchestration, heterogeneous execution adaptation, and data state consistency technologies. It discloses an intelligent governance execution method and platform based on a unified event object and internal / external dual closed loops. The platform converts heterogeneous events generated by public terminals, internal personnel terminals, business systems, smart devices, or execution agents into append-type source event objects, generating a unified event object containing template versions, participating entities, task graphs, feedback mappings, and disclosure strategies. Based on the governance template, task nodes are generated. Standardized node result credentials bound to events, nodes, templates, and inputs are obtained using execution adapters. The state of a single authoritative event is calculated, and internal processing views and external participation views are generated respectively. External supplements, corrections, confirmations, objections, or reviews form new source events, which reverse-locate relevant internal nodes, invalidating inconsistent results and derived views, while retaining irrelevant valid results and recalculating the state. This solution reduces state conflicts between heterogeneous systems, error completion judgments, duplicate processing, and expired progress displays.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the fields of computer workflow orchestration, heterogeneous system integration, event-driven data processing, task graph scheduling, access control, and data state consistency. In particular, it relates to an intelligent governance execution method and platform that converts heterogeneous event data generated by external participant terminals, internal personnel terminals, organizational business systems, smart devices, and execution agents into unified event objects, and realizes event acceptance, task execution, result verification, feedback processing, and progress synchronization through governance templates, execution adapters, standardized node result credentials, and internal and external double closed-loop state mapping. Background Technology

[0002] Existing government, enterprise, property management, hospital, school, and customer service systems typically have separate application forms, work orders, approval forms, task orders, complaint records, and progress records. When the same matter flows between different business systems, it is often copied into multiple independent records, each with different numbers, fields, and statuses. This results in inconsistent statuses for the same matter on the external participants' end, the internal processing end, and the execution system end.

[0003] Existing government service systems can already provide online acceptance, cross-departmental processing, document transfer, progress inquiry, supervision and feedback, and time-limited supervision. Existing work order technology can also use language models or knowledge graphs to analyze user requests, create work orders, and assign them to departments or personnel. Therefore, simply combining public submission, AI recognition, work order dispatch, process flow, and progress inquiry cannot solve the data consistency problem caused by multiple heterogeneous systems writing statuses for the same matter separately.

[0004] The results returned by staff, business interfaces, smart devices, and executing agents differ in format: staff may submit forms, images, videos, files, or confirmation operations; business systems may return status codes, business data, or third-party platform receipts; devices may return sensor data, device identity, and operation logs; and executing agents may return action logs, generated files, external system results, or verification results. If the platform only stores ordinary logs, it is difficult to uniformly verify the binding relationship between the above results and specific matters, task nodes, governance template versions, and node inputs, and it is also difficult to use a single calculation mechanism to summarize the overall status of matters.

[0005] In the existing system, after the public or customers supplement materials, correct original requests, confirm results, raise objections, or apply for review, the relevant content is often only added as a note. It cannot automatically determine which internal tasks, which results have been formed, and which progress has been made public. Staff may still continue to refer to old results that are inconsistent with the new feedback, and external pages may continue to display an expired status.

[0006] On the other hand, while organizations such as governments, enterprises, property management companies, hospitals, and schools use different fields and processes, they all include common computational processes such as event access, event aggregation, task decomposition, execution, result verification, exception handling, external feedback, and progress display. Building separate data models, interface adaptations, and status calculation logic for each industry would result in redundant development and high cross-system integration costs.

[0007] Therefore, there is a need for a technical solution that can establish a unified digital identity for the same matter, convert heterogeneous execution results into verifiable standardized node result credentials, enable internal processing views and external participation views to both originate from a single authoritative matter status, and enable external supplements, corrections, confirmations, objections, or reviews to update relevant internal tasks and results in reverse. Summary of the Invention

[0008] I. Technical problems to be solved The technical problems to be solved by this invention include: different terminals and business systems saving the same matter as multiple unrelated records, resulting in inconsistencies in the identity and status of the matter; different return formats from personnel, business systems, smart devices, and execution agents, making it impossible to participate in status calculations using unified fields; internal processing terminals and external participant terminals maintaining completion status separately, leading to inconsistencies between external progress and actual internal execution results; after external participants supplement, correct, confirm, object, or review, old internal task results and old public views cannot be automatically located and become invalid; and different industry systems repeatedly implementing matter models, execution interfaces, and status logic. To address the aforementioned technical problems, this invention provides an intelligent governance execution method based on a unified event object and internal and external dual closed loops, comprising the following steps:

[0009] It receives heterogeneous event information from external participant terminals, internal personnel terminals, organizational business systems, smart devices, or executing intelligent agents, and generates an append-only source event object for each heterogeneous event information.

[0010] Based on the relationships between events and participating entities, multiple source event objects are aggregated into a unified event object. The unified event object records the event identifier, a summary of the source event set, the relationships between participating entities, the governance template identifier, a summary of the governance template version, internal task graph references, a set of execution result contracts, external feedback mappings, information disclosure strategies, and authoritative event status records.

[0011] A governance template is loaded based on the organization type and task type, and an internal task graph with dependencies is generated based on the governance template. The governance template defines event field mapping, task node generation rules, execution entity type, execution adapter mapping, node input / output contract, external feedback mapping, and internal / external view mapping.

[0012] The task nodes in the internal task graph are sent to internal personnel, organizational business systems, smart devices, or execution agents respectively; the corresponding execution adapters convert the raw results returned by different execution entities into unified standardized node result credentials.

[0013] Verify the binding relationship between standardized node result vouchers and item identifiers, task node identifiers, governance template version summaries, and node input summaries; only valid result vouchers that pass the binding relationship verification and satisfy the node result contract are used for authoritative item status calculation.

[0014] The authoritative matter status record is calculated based on the node dependencies, valid result voucher set, pending node set, pending review result set, exception set, and pending external feedback set in the internal task graph. An internal processing view and an external participation view are generated based on the authoritative matter status record, and the two views are bound to the same matter version summary and the same authoritative status summary.

[0015] Receive supplementary, corrective, confirmatory, objection, or review events submitted by external participants, generate new source event objects from the events, and locate the internal task nodes, standardized node result credentials, and view fields related to the event based on the external feedback mapping.

[0016] Mark old result vouchers that are inconsistent with the newly added source event objects as pending review or invalid, retain valid result vouchers that are not affected by the newly added source event objects, and recalculate the authoritative event status record, internal processing view and external participation view based on the retained valid result vouchers and the changed unified event objects.

[0017] III. Data Objects (a) Source event object The source event object can be represented using JSON, Protocol Buffers, relational database records, event stream records, or other machine-readable structures, and must include at least the following parameters: source_event_id, matter_candidate_id, source_type, source_subject_id, event_type, occurred_at, content_reference, content_digest, access_scope, and previous_event_reference. The content_digest can be calculated using a hash algorithm after normalizing the original content. The source event object is stored in an append-only manner; subsequent additions or corrections do not overwrite the original event.

[0018] (ii) Unified Scope of Matters The unified matter objects include at least matter_id, source_event_set_digest, participant_relation_set, organization_type, matter_type, template_id, template_version_digest, internal_task_graph_reference, executor_contract_set, external_feedback_mapping, disclosure_policy_reference, authoritative_state_record and matter_version_digest.

[0019] (iii) Standardized node result vouchers A standardized node result credential includes at least the following: result_credential_id, matter_id, task_node_id, template_version_digest, node_input_digest, executor_type, executor_id_or_adapter_id, output_reference, evidence_reference_set, result_status, started_at, completed_at, and credential_digest. The credential digest can be calculated from the normalized fields other than the digest field.

[0020] (iv) Status record of authoritative matters The authoritative event status record is used to represent the current computable status of a unified event object. It can include the current stage, the set of valid task nodes, the set of nodes to be processed, the set of results to be reviewed, the set of exceptions, the set of results to be externally fed back, a status summary, and the generation time. Management terminals, external terminals, or execution adapters cannot directly write this record as the overall completion status; instead, the status processing layer calculates it based on valid result vouchers and the internal task graph.

[0021] This invention binds related events from different entry points and systems to the same digital object through event identifiers and source event set summaries, reducing duplicate records and identity mismatches; it shields differences in return formats from personnel, interfaces, devices, and agents by standardizing node result credentials, enabling heterogeneous results to be uniformly bound, validated, and aggregated; it reduces progress conflicts caused by multiple endpoints writing status by binding the same event version summary and authoritative status summary to internal processing views and external participation views; it locates relevant internal nodes and results through external feedback mapping, invalidating expired results and derived views while retaining irrelevant legitimate results, reducing computational and communication overhead caused by re-executing the entire process from scratch; and it enables different organizations or industries to share the underlying platform by reusing unified event objects, execution adapters, and status processing layers through governance template reuse, reducing redundant development and interface integration costs. Attached Figure Description

[0022] Figure 1 This is a schematic diagram of the overall architecture of the intelligent governance execution platform.

[0023] Figure 2 A diagram illustrating the unified data structure for object items.

[0024] Figure 3 This is a schematic diagram illustrating a shared authority state with internal and external closed loops.

[0025] Figure 4 A schematic diagram of heterogeneous execution adaptation and standardized node result credentials.

[0026] Figure 5 A schematic diagram of the internal task flow for external correction and reverse association. Detailed Implementation

[0027] I. Overall Architecture and Implementation Method like Figure 1 As shown, the platform includes a heterogeneous event entry point 100, an event access layer 200, an event orchestration layer 300, an execution adaptation layer 400, a state processing layer 500, and a view service layer 600. The heterogeneous event entry point 100 includes external participant terminals 110, internal personnel terminals 120, organizational business systems 130, smart devices 140, and execution intelligent agents 150.

[0028] The event access layer 200 includes a source event object generation module 210 and an event association module 220. The source event object generation module 210 establishes an event identifier, source entity identifier, time information, original content storage reference, and original content summary for each input. The event association module 220 associates related source event objects with the same event candidate based on explicit event numbers, participating entity relationships, time and space relationships, business object relationships, upstream and downstream reference relationships, or manual confirmation relationships.

[0029] The item orchestration layer 300 includes a unified item object management module 310, a governance template module 320, and an internal task graph generation module 330. The unified item object management module 310 maintains append-only item versions. The governance template module 320 stores executable governance templates, which can be represented using a BPMN extended structure, a directed acyclic graph definition, a rule table, or a domain-specific language. The internal task graph generation module 330 converts item fields and template rules into task nodes with prerequisite, parallel, conditional, waiting, and manual review relationships.

[0030] The execution adaptation layer 400 includes a personnel task adapter 410, a business system interface adapter 420, a smart device adapter 430, an execution agent adapter 440, and a standardized node result credential module 450. Each execution adapter does not require different execution agents to return the same original structure; instead, it converts the original structure into standardized node result credentials at the platform boundary.

[0031] The status processing layer 500 includes a credential binding and verification module 510, an authority matter status calculation module 520, and an external feedback reverse mapping module 530. The view service layer 600 includes an internal processing view 610 and an external participation view 620.

[0032] II. Implementation Method for Generating Items When the platform receives new heterogeneous events, it first standardizes the original content and calculates a content summary, then generates source event objects. For events with explicit event numbers, they are directly added to the corresponding event; for events without event numbers, event candidates are generated based on the source entity, business object, time range, location range, upstream and downstream references, and similarity results, and manual confirmation is requested when the automatic association confidence level is lower than a preset threshold. The association algorithm can employ rule matching, vector similarity, graph matching, or a combination thereof; this invention does not limit the specific model.

[0033] An event version summary can be obtained by summarizing the previous event version summary, the set of newly added source event identifiers, the set of changed fields, the governance template version summary, and the normalized sequence of current key fields. Based on the event version summary, it can be determined whether the standardized node result vouchers and external participant views are still consistent with the current event version.

[0034] III. Implementation Methods of Governance Templates and Internal Task Diagrams Governance templates are not ordinary display templates, but machine-readable packages that can be loaded and executed by the event orchestration layer. A governance template can include field patterns, event mapping rules, task node generation syntax, node preconditions, execution subject types, input / output patterns, exception branches, external feedback mappings, and state projection rules.

[0035] For example, the public road waterlogging template can generate nodes for address verification, management entity identification, on-site inspection, responsible unit receipt, on-site handling, result review, and public confirmation; the enterprise equipment procurement template can generate nodes for demand verification, on-site condition confirmation, solution generation, quotation approval, contract confirmation, installation and delivery, and customer acceptance; the property leakage template can generate nodes for emergency safety assessment, spatial relationship verification, on-site evidence collection, responsibility confirmation, repair, and feedback from both parties. The underlying platform does not modify the unified object and voucher verification logic due to industry changes.

[0036] IV. Heterogeneous Execution Adaptation Implementation Methods Personnel task adapter 410 can receive structured forms, images, videos, file summaries, timestamps, and confirmation operations; business system interface adapter 420 can convert HTTP responses, message queue receipts, database business status, or third-party platform receipts into credentials; smart device adapter 430 can receive sensor values, device identity, and operation logs; execution smart agent adapter 440 can receive action logs, generated files, external system returns, and verification results.

[0037] When the adapter generates standardized node result credentials, it reads the expected event identifier, task node identifier, governance template version summary, and node input summary from the task node. If the original result lacks necessary fields, a credential with a result status of "to be supplemented" can be generated; if the bound fields are inconsistent, the credential is placed in an isolated set and does not participate in the authoritative event status calculation.

[0038] V. Implementation Method for Authority Matters Status The authoritative task status calculation module 520 can perform topological traversal of the internal task graph. Each task node can have at least one status: not generated, pending execution, executing, pending supplementation, pending review, validly completed, failed, or canceled. The overall task status is jointly determined by the valid result credentials of necessary task nodes, prerequisite dependencies, pending external feedback, and exception set.

[0039] To avoid duplication with the authorization, idempotency, and external delivery verification mechanisms within the executor, this implementation does not limit how the executor performs the aforementioned internal processing. These capabilities can be provided by an independent execution service; the platform only receives the standardized node result credentials ultimately output by the execution service and performs event-level aggregation based on the credential's bound fields and result status.

[0040] VI. Internal and External Dual Closed-Loop Implementation Method Internal processing view 610 can display task graphs, responsible entities, inputs and outputs, result vouchers, anomalies, and internal evidence citations; external participation view 620 only displays the public status allowed by the information disclosure policy, the current stage, content to be supplemented, conditions for the next state transition, update time, and view version summary. The two views are adapted to different permissions, but both are bound to the same matter_version_digest and authoritative_state_digest.

[0041] When the internal valid results change, the state processing layer generates a new authoritative state summary, and the old external participant view is no longer considered a valid view due to the inconsistency of the summary. External participants cannot directly access the original text of internal sensitive evidence; the system can display anonymized fields, evidence type, time information, and evidence summary.

[0042] VII. External Feedback Reverse Mapping Implementation Method like Figure 5 As shown, when an external participant submits supplements, corrections, confirmations, objections, or reviews on the external participant view, the event must at least include an event identifier, the current external view version, the identifier of the field or result being responded to, the event type, and a reference to new content. After verifying the relationship between the submitting entity and the event, the system generates an append-only source event object.

[0043] External feedback mapping can be defined by governance templates to represent relationships between item fields, task nodes, standardized node result credentials, and view fields. For example, an address field can be mapped to an address verification node and an on-site inspection node; an equipment quantity field can be mapped to a scheme, quotation, and installation plan node; and a dispute over the cause of leakage can be mapped to a responsibility pending confirmation and repair path node.

[0044] The system compares the newly added source event object with the node input summary and result content of the mapped task node. Result credentials that are still consistent with the current event version remain valid; inconsistent results enter a pending review or invalidation state; internal states and external participation views derived from inconsistent results become invalid. Subsequently, the system recalculates the authoritative event status record based on the retained valid result credentials and the changed unified event object.

[0045] VIII. Examples of Government-Public Matters Residents can submit reports of persistent road flooding via mobile phone, including text, voice messages, photos, and location information. The platform establishes source event objects for each type of content and aggregates related source event objects into a unified event object. The process involves generating a public event governance template, verifying the address, identifying the road management entity, inspecting drainage facilities on-site, receiving the report from the responsible unit, processing the on-site issue, reviewing the results, and receiving confirmation from the public.

[0046] On-site personnel upload photos and processing records via the personnel task adapter, while the drainage monitoring system returns detection data via the business system interface adapter or smart device adapter. All results are converted into standardized node result certificates, and the statuses displayed on the public terminal, such as "Accepted," "Under On-site Verification," and "Processing Result Pending Confirmation," are all derived from authoritative event status records.

[0047] If the public provides further details that the waterlogged area is located on the other side of the intersection, the platform generates a new correction event. Based on the external feedback, it maps the location address verification and on-site inspection nodes, causing the inspection results corresponding to the old location to enter a pending review state. However, it retains the identity verification and matter type verification results that have already been completed and do not depend on the location change.

[0048] IX. Examples of Business Operations Customers submit equipment procurement and installation requests through the enterprise portal. A unified system connects customers, sales personnel, technical solution providers, the quotation system, installation personnel, the after-sales system, and the management terminal for the boss. The enterprise governance template generates requests for verification, confirms on-site conditions, generates solutions, approves prices, confirms contracts, and handles installation, delivery, and customer acceptance.

[0049] After the customer discovered an error in the understanding of the equipment quantity in the plan and submitted a correction, the system mapped and located the plan, quotation, and installation schedule nodes based on external feedback, rendering the old quotation and its derivatives invalid; the customer's identity, address, and previously confirmed basic conditions remain valid. Both the management and client sides display the recalculated current status.

[0050] 10. Examples of Property Leakage Issues The homeowner submits a report of a ceiling leak, including videos, photos, the time of discovery, and the location of the leak. The property management template generates a process for emergency safety assessment, spatial relationship verification, contacting upstairs residents, inspecting public utilities and in-unit facilities, collecting on-site evidence, confirming liability, assigning repair tasks, verifying results, and providing feedback to both parties.

[0051] The platform does not automatically determine legal liability; instead, it converts the results of on-site personnel, equipment, and business systems into standardized node result vouchers. If the homeowner repairs the leak after upstairs renovations, the event is linked to renovation verification, liability confirmation, and repair path nodes. Objective on-site photos and humidity records are retained, and the old liability analysis results enter a pending review state. The external participation view hides other residents' contact information and internal sensitive parameters.

[0052] XI. Implementation Example of Mobile Command Center for Intelligent Headquarters The business owner submits operational or system management tasks via mobile terminal, and the source event object stores the owner's original instructions and a summary of the content. The governance template breaks down the task into status query, risk assessment, approval, cross-device or cross-agent execution, result summary, and owner confirmation nodes. Personnel, server executors, and business systems return standardized node result vouchers through different execution adapters.

[0053] The "Executing," "Pending Approval," and "Completed" statuses seen on the boss's phone all originate from the same authoritative event status record. When the boss corrects the task objective or narrows the scope of authorization, the platform generates a new source event object and locates the affected tasks and results, while retaining the unaffected read-only inspection results to avoid continuing to use the execution results under the old objective as the current result.

[0054] 12. Optional Implementation and Exception Handling Unified event objects and internal task graphs can be stored in relational databases, graph databases, document databases, or event flow systems. The digest algorithm can use SHA-256 or other digest algorithms capable of recognizing content changes. Execution adapters can be deployed on central servers, edge nodes, or clients.

[0055] When the original source event is temporarily unavailable, the platform can retain the content summary and stored reference and mark it as pending recovery; when the execution adapter times out or the returned result format is incomplete, it generates a result to be supplemented instead of completing the whole thing; when the external feedback mapping is missing or there are multiple conflicting nodes, the matter enters manual mapping review and does not automatically invalidate all results.

[0056] The above embodiments are used to illustrate the present invention and not to limit the scope of protection of the present invention. Without departing from the inventive concept of unified subject matter objects, standardized node result credentials, internal and external dual closed-loop shared authoritative states, and external feedback updating internal tasks, equivalent substitutions can be made for data fields, storage methods, task graph representations, adapter protocols, and view formats.

Claims

1. A smart governance execution method based on a unified item object and internal and external dual closed loops, applied to a smart governance execution platform including an item access layer, an item orchestration layer, an execution adaptation layer, a state processing layer, and a view service layer, characterized in that, include: Receive heterogeneous event information from external participant terminals, internal personnel terminals, organizational business systems, smart devices, or execution smart agents, and generate an append-only source event object for each heterogeneous event information. The source event object includes at least a source event identifier, a source entity identifier, an event type, time information, a reference to the original content storage, and a summary of the original content. A unified event object is generated based on the event associations and participating entity relationships among multiple source event objects. The unified event object includes at least an event identifier, a source event set summary, a participating entity relationship set, a governance template identifier, a governance template version summary, an internal task graph reference, an execution result contract set, an external feedback mapping, an information disclosure strategy reference, and an authoritative event status record. An internal task graph is generated based on the governance template, and the corresponding task nodes are sent to the corresponding execution entities through personnel task adapters, business system interface adapters, smart device adapters, or execution smart agent adapters according to the execution entity type corresponding to the task nodes in the internal task graph. Receive node results returned by each execution adapter, and convert the node results returned by different execution entities into standardized node result vouchers. The standardized node result vouchers are bound to at least the event identifier, task node identifier, governance template version summary, node input summary, execution adapter identifier, output data reference, result evidence reference, node result status, and result voucher summary. Verify the binding relationship between the standardized node result voucher and the unified matter object and corresponding task node, and calculate the authoritative matter status record based on the valid standardized node result voucher and the node dependency relationship in the internal task graph; Based on the authoritative matter status record, an internal processing view and an external participation view are generated respectively, so that the internal processing view and the external participation view are both bound to the same matter version summary and the same authoritative status summary; Receive supplementary, corrective, confirmatory, objection, or review events submitted by external participants in relation to the external participant view, convert the events into new source event objects, and determine the internal task nodes and standardized node result credentials associated with the event based on the external feedback mapping; Standardized node result vouchers that are no longer consistent with the newly added source event object are marked as pending review or invalid. Valid standardized node result vouchers that are not affected by the newly added source event object are retained, and the authoritative event status record, internal processing view, and external participation view are recalculated.

2. The method according to claim 1, characterized in that, The appended source event object also includes access scope and reference to previous events; the unified event object adopts an appended version structure, and each event version saves the summary of the previous event version, the set of source event identifiers added this time, the set of changed fields and the summary of the current event version. Subsequent supplements or corrections do not overwrite the original source event object.

3. The method according to claim 1, characterized in that, The governance template also includes event field mapping rules, item type identification rules, task node generation rules, node dependencies, execution subject type, execution adapter mapping rules, node input / output contracts, external feedback and internal task association rules, and internal view and external view mapping rules. By loading different governance templates, the item orchestration layer can generate different internal task diagrams for different organizational types or industries without modifying the core program of the item orchestration layer.

4. The method according to claim 1, characterized in that, The execution adapter converts personnel operation records, business interface returns, equipment operation data, or execution agent outputs into standardized node result credentials, and verifies the item identifier, task node identifier, governance template version summary, and node input summary item by item; standardized node result credentials with inconsistent binding fields are isolated and stored and do not participate in the calculation of authoritative item status records.

5. The method according to claim 1, characterized in that, The authoritative event status record is calculated based on the dependency satisfaction status of each task node in the internal task graph, valid standardized node result credentials, pending external feedback, and the set of abnormal nodes. Internal personnel terminals, external participant terminals, or execution adapters cannot directly modify the unified event object to the overall completion status. The overall completion status is only generated when all necessary task nodes corresponding to the target completion status have valid standardized node result credentials and there is no unprocessed external feedback blocking downstream nodes.

6. The method according to claim 1, characterized in that, The external participation view includes at least the public status, the current processing stage, information to be supplemented by the external participant, the conditions for the next status transition, the update time, and a view version summary. When the correction or objection event submitted by the external participant changes the source event set summary, the system locates the affected task node and its derived view based on the external feedback mapping, and prevents the external participation view bound to the old source event set summary from continuing to be displayed as the current valid progress.

7. An intelligent governance execution platform based on a unified matter object and internal and external dual closed loops, characterized in that, include: The module includes a heterogeneous event access module, a source event object generation module, a unified event object management module, a governance template management module, an internal task graph generation module, an execution adapter routing module, a standardized node result voucher processing module, an authoritative event status calculation module, an internal and external view generation module, an external feedback event processing module, and a related result invalidation and recalculation module. Each module is configured to perform the method described in any one of claims 1 to 6.

8. An electronic device comprising a processor and a memory, characterized in that, The memory stores a computer program, which, when executed by the processor, causes the electronic device to perform the method described in any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method described in any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method described in any one of claims 1 to 6.