A professional document phase state and export binding consistency verification method and system, electronic equipment and storage medium

Abstract

The application relates to the technical field of professional document processing, and discloses a professional document stage state and export binding consistency verification method and system, electronic equipment and a storage medium. The method generates a first stage state summary and a component summary table based on a recalculation stage output fingerprint, a reserved stage output fingerprint, a target stage input fingerprint, a quality gate fingerprint, a manual editing fingerprint and a repair record fingerprint when a local recalculation is submitted, and writes the first stage state summary and the component summary table into a non-intrusive audit list which is saved in parallel with a target document and does not write into a text. The stage information object is read again before export to generate a second stage state summary, and the second stage state summary is compared with the first stage state summary. When the first stage state summary and the second stage state summary are consistent, an export binding summary is generated based on the second stage state summary, an export file fingerprint and a document assembly configuration fingerprint. When the first stage state summary and the second stage state summary are inconsistent, the export is blocked or a review task is generated, so that the consistency of an export file and a stage state is verified.

Description

Technical Field

[0001] This invention relates to the field of professional document processing technology, specifically to a method, system, electronic device, and storage medium for verifying the consistency between the stage status and export binding of professional documents. Background Technology

[0002] The generation process of evidence-constrained professional documents typically involves multiple rigorous and interdependent stages, including initial content generation, multiple rounds of quality checks, issue feedback and revisions, and final standardized export. In this complex process, local recalculation mechanisms are widely used. Their core advantage lies in their ability to accurately identify and re-execute only the specific stages affected by input changes, effectively avoiding unnecessary duplication of calculations for other unaffected stages and significantly improving overall processing efficiency. However, while this optimization strategy improves performance, it also introduces new challenges to state consistency: when the document is finally exported, its content may be a mixture of output generated after the latest round of local recalculation and output from previous stages that were not recalculated. If this mixed state is not effectively controlled, it can easily lead to inconsistencies in the document's internal logic or data mismatches. Specifically, if the system only performs consistency checks on the overall content of the final exported file, it will be unable to determine whether the retained stage outputs still accurately reflect the latest state of the current task. Conversely, if the system only focuses on checking those stages that have undergone recalculation, it may overlook potential inconsistencies caused by changes in the original input data of the retained stages, updates to the associated quality gating check results, or adjustments to document assembly configuration parameters, thus creating potential errors.

[0003] Currently, mainstream document export systems typically handle audit trace requirements by recording relevant audit information in system logs, embedding it in text annotations, or attaching it to export notes. However, these methods each have significant drawbacks: directly writing audit information into the text content contaminates the officially delivered document, affecting its professionalism and readability, and failing to meet high-quality delivery standards; while relying solely on backend log storage of audit data makes it difficult to effectively establish a clear and verifiable correspondence between the exported file and key nodes in its generation process afterward. Especially in complex multi-stage automated generation pipelines, even if a stage has been submitted and entered a cached state, various interfering factors may still occur before the final export operation is executed. These include direct manual editing of intermediate results, rework operations targeting localized issues, temporary adjustments to document format or assembly template configurations, and even accidental loss or expiration of data in the retention stage due to cache mechanism failure. Therefore, relying solely on a single digital fingerprint of the exported file is insufficient to comprehensively and reliably prove the true state and consistency of all internal processing stages corresponding to that file. A more refined, end-to-end audit and state binding mechanism is urgently needed to ensure the credibility and compliance of documents.

[0004] Therefore, a non-intrusive audit consistency verification mechanism is needed to store the audit checklist and the target document side by side, and to verify the consistency between the exported document and the stage status through fingerprints output during the recalculation stage, fingerprints output during the retention stage, fingerprints input during the target stage, fingerprints of the quality gate, and fingerprints of the exported document. Summary of the Invention

[0005] To address the shortcomings of existing technologies, this invention provides a method, system, electronic device, and storage medium for verifying the consistency between the stage status and the exported document in a professional document generation process. This method can non-intrusively bind and verify the status of each stage, quality inspection results, and manual operation records in a multi-stage document generation process with the final exported document. It solves the technical problems of existing auditing methods that easily contaminate formal documents, cannot correspond the exported file to the specific status in the multi-stage generation process, and cannot verify the consistency between the exported file and the internal stage status using a single file fingerprint.

[0006] To achieve the above objectives, the present invention provides the following technical solution: a method for verifying the consistency between the stage status and export binding of professional documents, comprising the following steps: S1. Obtain the stage information object in the target document generation process. The stage information object includes stage identifier, stage output fingerprint, target stage input fingerprint, quality gate fingerprint, manual editing fingerprint, rework record fingerprint, failure status and most recently valid output reference. S2. Determine the set of recalculation stages based on the local recalculation results, and determine the set of retained stages based on the impact judgment records; obtain the recalculation stage output fingerprint in the set of recalculation stages, the retained stage output fingerprint in the set of retained stages, and the target stage input fingerprint corresponding to the set of retained stages; S3. During stage submission, the fingerprints of the recalculation stage output, the fingerprints of the retention stage output, the fingerprints of the target stage input, the fingerprints of the quality gate, the fingerprints of manual editing, and the fingerprints of rework records are standardized according to the preset field order to generate the first stage status summary and component summary table, and written into the non-intrusive audit checklist that is saved alongside the target document but not written into the main text; among them, the fingerprints of the retention stage output and the fingerprints of the target stage are both included in the first stage status summary to distinguish the state where the main text of the retention stage has not changed but its effective input has changed; S4. Assemble the target document based on the latest valid stage output and document assembly configuration, and generate the export file fingerprint based on the standardized export file content; S5. Before exporting the target document, reread the phase information object and non-intrusive audit checklist, and generate the second phase status summary according to the same field order; S6. When the second-stage state summary is inconsistent with the first-stage state summary, locate the source of inconsistency based on the component summary table, and block the export or generate an export review task. S7. When the second-stage state summary is consistent with the first-stage state summary, an export binding summary is generated based on the second-stage state summary, the exported file fingerprint, and the document assembly configuration fingerprint, and the export binding summary is written into the non-intrusive audit checklist. S8. When exporting for review or re-exporting, regenerate the export binding summary and compare it with the export binding summary in the non-intrusive audit checklist. If they do not match, block the export or generate an export review task.

[0007] Furthermore, the non-intrusive audit checklist includes one or more of the following: task identifier, document type, configuration fingerprint, document assembly configuration fingerprint, stage node list, stage output fingerprint set, target stage input fingerprint set, quality gate fingerprint set, manual editing fingerprint set, rework record fingerprint set, first stage status summary, second stage status summary, exported file fingerprint, exported raw byte stream fingerprint, exported binding summary, quality defect summary, component summary table, quality summary, evidence status summary, manual review status, and export time; wherein, the export time is not included in the first stage status summary, second stage status summary, and exported binding summary.

[0008] Furthermore, generating the first-stage status summary and the second-stage status summary includes: sorting the structured fields according to a preset field order or field name; standardizing the line breaks in the text content, deleting invisible control characters, and merging consecutive whitespace characters; generating the stage output component summary, the target stage input component summary, the quality gate component summary, the manual editing component summary, and the rework record component summary, respectively; generating the export binding summary includes: standardizing the second-stage status summary, the exported file fingerprint, and the document assembly configuration fingerprint according to a preset field order.

[0009] Further, determining the set of retention stages includes: reading the impact judgment record, which includes the candidate downstream stage set, the affected stage set, the retention stage set, the impact judgment result, the retention stage output fingerprint, the target stage input fingerprint, and the retention reason; when the impact judgment result indicates that the corresponding stage is not affected by the manual editing event and the target stage input fingerprint has not changed, the corresponding stage is determined as the retention stage.

[0010] Furthermore, the set of stage output fingerprints includes both recalculated stage output fingerprints and retained stage output fingerprints; when any retained stage output fingerprint is missing, any target stage input fingerprint is missing, the retained stage output fingerprint is inconsistent with the most recent valid output reference, or the target stage input fingerprint is inconsistent with the impact judgment record, the system blocks the export or generates a review task.

[0011] Furthermore, the partial recalculation results are first written to a temporary output area, which includes a temporary output reference, a temporary output fingerprint, a temporary quality gate fingerprint, and a temporary rework record fingerprint. When the quality gate review passes, the system submits the temporary output area as the most recent valid output and writes the temporary rework record fingerprint to the non-intrusive audit list. When the quality gate review fails, the system rolls back the temporary output area and retains the first-stage state summary before the stage submission.

[0012] Furthermore, when the second-stage status summary is inconsistent with the first-stage status summary, the system compares the stage output component summary, target stage input component summary, quality gate component summary, manual editing component summary, and rework record component summary in the component summary table, and outputs the source of the stage status inconsistency; when the export binding summary verification fails, the system compares the second-stage status summary, export file fingerprint, and document assembly configuration fingerprint, and outputs the source of the export binding inconsistency.

[0013] Furthermore, when the target document is a document package file, the system reads the relevant files in the main text according to the file path order within the package, filters one or more non-main text changes such as creation time, modification time, application version number, compressed package entry order, temporary relationship number, and preview thumbnail, and generates an export file fingerprint based on the main text, paragraph level, table content, image reference relationship, and export format configuration.

[0014] Furthermore, when the target document is a patent application document, the system writes the claim output fingerprint, specification support mapping fingerprint, embodiment paragraph output fingerprint, drawing description fingerprint, drawing label consistency check fingerprint, abstract output fingerprint, quality gate fingerprint, exported file fingerprint, and document assembly configuration fingerprint into a non-intrusive audit checklist; when any of the fingerprints mentioned above before export is inconsistent with the corresponding component in the first-stage status summary or export binding summary, the system blocks the export or generates a patent document export review task.

[0015] To achieve the above objectives, this invention also provides a professional document stage status and export binding consistency verification system, which employs the aforementioned professional document stage status and export binding consistency verification method. The system comprises: a stage status reading module for acquiring stage information objects; a stage retention identification module for determining the set of stages to be retained based on impact judgment records; a stage submission control module for submitting a temporary output area when the quality gate review passes and rolling back the temporary output area when the quality gate review fails; a stage status summary generation module for generating a first stage status summary, a second stage status summary, and a component summary table; an audit checklist generation module for generating and saving a non-intrusive audit checklist; an export file fingerprint generation module for generating an export file fingerprint based on the normalized export file content and generating an export original byte stream fingerprint as an additional verification field; an export binding summary generation module for generating an export binding summary based on the second stage status summary, the export file fingerprint, and the document assembly configuration fingerprint; a component comparison module for locating the source of stage status inconsistency or export binding inconsistency; and an export verification module for blocking export or generating an export review task when the summary is inconsistent.

[0016] To achieve the above objectives, the present invention also provides an electronic device, characterized in that it includes a processor and a memory, wherein the memory stores a computer program executable by the processor, and the computer program, when executed by the processor, implements the above-described method for verifying the consistency between the stage state and the export binding of a professional document.

[0017] To achieve the above objectives, the present invention also provides a computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program, which, when executed by a processor, implements the above-described method for verifying the consistency between the stage state and the export binding of a professional document.

[0018] Compared with existing technologies, this invention can verify the consistency between exported files, recalculation stages, retention stages, target stage inputs, quality gate results, manual editing records, and rework records without changing the main text of the target document. By comparing the first and second stage status summaries, it reduces the risk that status changes after stage submission will not be detected by the export process. By binding the export summary to the standardized exported file content, document assembly configuration, and stage status, it reduces the risk of file mismatch caused by re-exporting or format assembly changes. By simultaneously verifying the retention stage output fingerprint and the target stage input fingerprint, it avoids the incorrect reuse of expired inputs simply because the retention stage text has not changed. By locating the source of inconsistency through the component summary table, it reduces manual investigation time and the number of repeated exports. Attached Figure Description

[0019] Figure 1This is a schematic diagram of the overall system flow and data flow according to an embodiment of the present invention; Figure 2 This is a schematic diagram illustrating the generation of a stage state summary according to an embodiment of the present invention; Figure 3 This is a schematic diagram illustrating the generation and verification of an exported binding digest according to an embodiment of the present invention; Figure 4 This is a schematic diagram of component summary comparison and positioning according to an embodiment of the present invention; Figure 5 This is a schematic diagram illustrating the export of a patent application document for consistency verification according to an embodiment of the present invention; In the diagram: 100: Stage Status Reading Module; 110: Retain Stage Identification Module; 120: Stage Submission Control Module; 130: Non-Intrusive Audit Checklist; 140: Export Binding Summary Generation Module; 150: Component Comparison Module; 160: Export Verification Module; 170: Output Source Location Result; 180: Normalize Field Order; 190: Retain Stage Output Fingerprint; 200: First Stage Status Summary; 210: Second Stage Status Summary; 220: Component Summary Table; 230: Stage Output Fingerprint 240: Target stage input fingerprint; 250: Quality gate fingerprint; 260: Manual editing fingerprint; 270: Rework record fingerprint; 280: Exported file fingerprint; 290: Exported raw byte stream fingerprint; 300: Document assembly configuration fingerprint; 310: Exported file content; 320: Claims output fingerprint; 330: Specification support mapping fingerprint; 340: Embodiment paragraph output fingerprint; 350: Drawing description fingerprint; 360: Drawing label consistency check fingerprint; 370: Abstract output fingerprint. Detailed Implementation

[0020] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention. Example 1

[0021] This embodiment 1 provides a method for verifying the consistency between the stage status of a professional document and its export binding, characterized by the following steps: S1. Obtain the stage information object in the target document generation process. The stage information object includes stage identifier, stage output fingerprint 230, target stage input fingerprint 240, quality gate fingerprint 250, manual editing fingerprint 260, rework record fingerprint 270, failure status, and most recently valid output reference. S2. Determine the recalculation stage set based on the local recalculation results, and determine the retention stage set based on the impact judgment record; obtain the recalculation stage output fingerprint 230 in the recalculation stage set, the retention stage output fingerprint 190 in the retention stage set, and the target stage input fingerprint 240 corresponding to the retention stage set; wherein, determining the retention stage set includes: reading the impact judgment record, the impact judgment record including the candidate downstream stage set, the affected stage set, the retention stage set, the impact judgment result, the retention stage output fingerprint 190, the target stage input fingerprint 240, and the retention reason; when the impact judgment... The results indicate that the corresponding stage was not affected by manual editing events, and the target stage input fingerprint 240 remained unchanged. Therefore, the corresponding stage is designated as a retained stage. The local recalculation results are first written to a temporary output area, which includes a temporary output reference, a temporary output fingerprint, a temporary quality gate fingerprint 250, and a temporary rework record fingerprint 270. When the quality gate review passes, the system submits the temporary output area as the most recently valid output and writes the temporary rework record fingerprint 270 to the non-intrusive audit checklist 130. When the quality gate review fails, the system rolls back the temporary output area and retains the first stage state summary 200 before stage submission. S3. During stage submission, the recalculation stage output fingerprint 230, retention stage output fingerprint 190, target stage input fingerprint 240, quality gate fingerprint 250, manual editing fingerprint 260, and rework record fingerprint 270 are standardized according to a preset field order to generate a first-stage status summary 200 and a component summary table 220. These are then written into a non-intrusive audit checklist 130 that is saved alongside the target document but not included in the main text. The retention stage output fingerprint 190 and the target stage input fingerprint 240 are both included in the first-stage status summary 200 to distinguish states where the main text of the retention stage remains unchanged but its effective input has changed. The first-stage status summary 200 includes: sorting structured fields according to a preset field order or field name; unifying line breaks in the text content, deleting invisible control characters, and merging consecutive whitespace characters; generating stage output component summaries, target stage input component summaries, quality gate component summaries, manual editing component summaries, and rework record component summaries respectively; the non-intrusive audit checklist 130 includes task identifiers, document types, configuration fingerprints, document assembly configuration fingerprints 300, stage node lists, a set of stage output fingerprints 230, a set of target stage input fingerprints 240, a set of quality gate fingerprints 250, a set of manual editing fingerprints 260, and a rework record component summary. The system comprises one or more of the following: a set of repair record fingerprints 270, a first-stage state digest 200, a second-stage state digest 210, an exported file fingerprint 280, an exported raw byte stream fingerprint 290, an exported binding digest, a quality defect digest, a component digest table 220, a quality digest, an evidence state digest, a manual review status, and an export time; wherein, the export time is not included in the first-stage state digest 200, the second-stage state digest 210, and the exported binding digest; the set of stage output fingerprints 230 includes both the recalculation stage output fingerprint 230 and the retention stage output fingerprint 190; when any retention stage output fingerprint 190 is missing, any If the target stage input fingerprint 240 is missing, the retention stage output fingerprint 190 is inconsistent with the most recent valid output reference, or the target stage input fingerprint 240 is inconsistent with the impact judgment record, the system blocks the export or generates a review task; when the target document is a patent application document, the system writes the claim output fingerprint 320, specification support mapping fingerprint 330, embodiment paragraph output fingerprint 340, drawing description fingerprint 350, drawing label consistency check fingerprint 360, abstract output fingerprint 370, quality gate fingerprint 250, exported file fingerprint 280, and document assembly configuration fingerprint 300 into the non-intrusive audit checklist 130; S4. Assemble the target document based on the latest valid stage output and document assembly configuration, and generate an export file fingerprint 280 based on the standardized export file content 310; when the target document is a document package file, the system reads the relevant files in the main text according to the file path order in the package, filters one or more non-main text changes in the creation time, modification time, application version number, compressed package entry order, temporary relationship number and preview thumbnail, and generates an export file fingerprint 280 based on the main text, paragraph level, table content, image reference relationship and export format configuration; S5. Before exporting the target document, reread the stage information object and non-intrusive audit checklist 130, and generate the second stage status summary 210 according to the same field order; generating the second stage status summary 210 includes: sorting the structured fields according to the preset field order or field name; unifying the line breaks in the text content, deleting invisible control characters and merging consecutive whitespace characters; and generating the stage output component summary, the target stage input component summary, the quality gate component summary, the manual editing component summary and the rework record component summary respectively. S6. When the second-stage status digest 210 is inconsistent with the first-stage status digest 200, the source of inconsistency is located based on the component digest table 220, and the export or export review task is blocked. The system compares the stage output component digest, target stage input component digest, quality gate component digest, manual editing component digest, and rework record component digest in the component digest table 220 respectively, and outputs the source of stage status inconsistency. When the target document is a patent application document, if any of the fingerprints mentioned before export is inconsistent with the corresponding component in the first-stage status digest 200 or the export binding digest, the system blocks the export or generates a patent document export review task. S7. When the second-stage state digest 210 is consistent with the first-stage state digest 200, an export binding digest is generated based on the second-stage state digest 210, the exported file fingerprint 280, and the document assembly configuration fingerprint 300, and the export binding digest is written into the non-intrusive audit checklist 130; generating the export binding digest includes: normalizing the second-stage state digest 210, the exported file fingerprint 280, and the document assembly configuration fingerprint 300 according to a preset field order; S8. During export review or re-export, regenerate the export binding summary and compare it with the export binding summary in the non-intrusive audit checklist 130. If they are inconsistent, block the export or generate an export review task. When the export binding summary verification fails, the system compares the second-stage status summary 210, the exported file fingerprint 280, and the document assembly configuration fingerprint 300 respectively, and outputs the source of the export binding inconsistency. When the target document is a patent application document, if any of the fingerprints before export is inconsistent with the corresponding component in the first-stage status summary 200 or the export binding summary, the system blocks the export or generates a patent document export review task. Example 2

[0022] This embodiment 2 provides a professional document stage status and export binding consistency verification system. The system's architecture closely relies on and fully reuses the professional document stage status and export binding consistency verification method proposed in embodiment 1 to ensure the logical rigor and technical feasibility of the entire verification process. The system specifically includes the following nine functional modules, which work collaboratively to achieve accurate verification and effective control of the consistency between the stage status and the final export result throughout the document's entire lifecycle: Module 1: Stage Status Reading Module 100 is used to accurately obtain the stage information object corresponding to the currently processed document from the document management system or related business database. This object contains key metadata such as the development or review stage of the document, timestamp, responsible person, and status identifier, providing basic input for subsequent consistency verification.

[0023] Module 2: Retention Stage Identification Module 110 is used to dynamically identify and determine the set of stages that should be retained based on the preset change impact analysis results, dependency graphs or historical audit trajectory impact judgment records, to ensure that key intermediate states are not accidentally deleted or overwritten during multi-stage iteration.

[0024] Module 3: Phase Submission Control Module 120 is used to formally submit the phase results in the temporary output area to the target storage area if the quality gate review process is successfully passed; otherwise, if the quality gate review fails, the rollback mechanism is automatically triggered to restore the temporary output area to the previous stable state, thereby ensuring the compliance and reliability of the output content.

[0025] Module 4: Stage State Summary Generation Module, which generates a first stage state summary 200 and a second stage state summary 210 based on current and historical stage information, and further constructs a component summary table 220. This table records the state hash values ​​of each sub-module or component in detail, providing data support for fine-grained comparison.

[0026] Module 5: Audit Checklist Generation Module, which automatically generates a non-intrusive audit checklist 130 and persists it in the security log library; the checklist fully records the operation steps, participating modules, input and output parameters and timestamps in this verification process, which facilitates subsequent traceability and compliance review, and does not affect the normal execution of the main business process.

[0027] Module 6: Export File Fingerprint 280 Generation Module, which performs hash operation on the normalized export file content 310 to generate a uniquely identified export file fingerprint 280; at the same time, to further enhance the verification strength, this module also generates an additional export original byte stream fingerprint 290, which is embedded in the export metadata as an additional verification field to prevent content tampering or transmission distortion.

[0028] Module 7: Export Binding Summary Generation Module 140, which integrates the second-stage status summary 210, the exported file fingerprint 280, and the document assembly configuration fingerprint 300 (a unique identifier reflecting configuration information such as document structure template and style rules), and generates the final export binding summary through multi-source information fusion calculation. This summary serves as the core basis for determining whether "status-export" is consistent.

[0029] Module 8: Component comparison module 150 is used to perform item-by-item comparison and analysis between the component summary table 220 and the export-related fingerprints when a summary inconsistency is detected, so as to accurately locate the specific source of the inconsistency, that is, whether it is due to abnormal changes in the stage state itself, or configuration deviations or data misalignments in the export binding process.

[0030] Module 9: Export Verification Module 160 is used to immediately block the current export operation to prevent the leakage of erroneous results when there is an inconsistency between the status summary and the export binding summary during the system judgment phase. At the same time, it can automatically generate export review tasks according to preset strategies, which are then handed over to manual or advanced automated processes for secondary confirmation and correction, thereby forming a closed-loop quality assurance mechanism.

[0031] The working principle of the above embodiments is as follows: During use, the stage status reading module 100 receives the target document task data and standardizes it into task objects. Task objects can include target document type, jurisdiction configuration, language configuration, delivery format configuration, original input data index, evidence data index, rule version identifier, and export configuration. The system generates a stage relationship diagram based on the task objects and generates a stage information object for each stage node. The stage information object can store the stage identifier, input fingerprint, output fingerprint, rule version fingerprint, quality gate fingerprint 250, manual editing fingerprint 260, rework record fingerprint 270, failure status, and most recently valid output reference.

[0032] After the system completes the partial recalculation, it determines the set of recalculation stages based on the partial recalculation task, and the retention stage identification module 110 determines the set of retention stages based on the impact judgment records. The impact judgment records can originate from the upstream impact relationship judgment process, be supplemented by the stage submission control module 120 during the partial recalculation process, or be provided by external stage status records. They must include at least the candidate downstream stage set, the affected stage set, the retention stage set, the impact judgment result, the retention stage output fingerprint 190, the target stage input fingerprint 240, and the retention reason. The impact judgment result serves as the basis for explaining why the retention stage was not affected by manual editing events or partial recalculation events.

[0033] like Figure 2 As shown, during stage submission, the system first reads the recalculated stage set and the retained stage set, then reads the stage output fingerprint 230, the retained stage output fingerprint 190, the target stage input fingerprint 240, the quality gate fingerprint 250, the manual editing fingerprint 260, and the rework record fingerprint 270. The system normalizes the above fields according to the normalized field order 180, generating stage output component summaries, target stage input component summaries, quality gate component summaries, manual editing component summaries, and rework record component summaries respectively, and generates the first stage status summary 200 based on each component summary. The retained stage output fingerprint 190 is used to confirm whether the content of the retained stage is still the most recently valid output, and the target stage input fingerprint 240 is used to confirm whether the valid input set corresponding to the retained stage is still consistent with that at the time of stage submission. Only when both conditions are met is the retained stage considered a valid stage that can be exported.

[0034] The non-intrusive audit checklist 130 is saved alongside the target document but not written into the target document text. The audit checklist may include task identifier, document type, configuration fingerprint, document assembly configuration fingerprint 300, stage node list, stage output fingerprint set, target stage input fingerprint set, quality gate fingerprint set, manual editing fingerprint set, rework record fingerprint set, first stage status summary, second stage status summary 210, exported file fingerprint 280, exported raw byte stream fingerprint 290, export binding summary, quality defect summary, component summary table 220, quality summary, evidence status summary, manual review status, and export time. The export time is saved as an audit field and is not included in the first stage status summary, second stage status summary, or export binding summary.

[0035] The non-intrusive audit checklist can be stored using a structured object. This structured object includes task identifiers, a list of stage nodes, a recalculation stage output fingerprint table, a retention stage output fingerprint table, a target stage input fingerprint table, a quality gate fingerprint table, a manual editing fingerprint table, a rework record fingerprint table, a first-stage status summary, a second-stage status summary (210), an exported file fingerprint (280), an exported raw byte stream fingerprint (290), a document assembly configuration fingerprint (300), and an exported binding summary and component summary table (220). The recalculation stage output fingerprint table and the retention stage output fingerprint table are indexed by the stage identifier, respectively. The target stage input fingerprint table is indexed by the target stage identifier and the input set version. The component summary table (220) stores the stage output component summary, the target stage input component summary, the quality gate component summary, the manual editing component summary, and the rework record component summary.

[0036] The results of partial recalculation are first written to the temporary output area. The temporary output area may include temporary output references, temporary output fingerprints, temporary quality gate fingerprints, and temporary rework record fingerprints. When the quality gate review passes, the system submits the temporary output area as the most recent valid output and writes the temporary rework record fingerprint to the non-intrusive audit checklist 130. When the quality gate review fails, the system rolls back the temporary output area and retains the first-stage state summary 200 before the stage commit.

[0037] The system assembles the target document based on the latest valid stage output. For the exported file content 310, the system generates an exported file fingerprint 280 based on the normalized exported file content. The normalized exported file content can exclude one or more of the following: export time, file package metadata, compression order, temporary identifiers, and non-text control fields in headers and footers. When the target document is in document package format, the system can read the relevant documents according to the file path within the package, exclude attribute files that record creation time or modification time, unify the order of temporary identifiers in the relation files, and generate the exported file fingerprint 280 after normalizing the text nodes and attribute order of the relevant documents. In a specific embodiment, when the target document is a document package file, the system reads the main content file, style file, relation file, and media manifest file, and filters one or more non-text changes from the following: creation time, modification time, last print time, application version number, compressed package entry order, temporary relation number, and preview thumbnail. Then, the system serializes the main text, paragraph levels, table content, image reference relationships, and export format configuration according to the preset order of the path within the package, and generates the exported file fingerprint 280 based on the serialization result. The system can also generate an exported raw byte stream fingerprint 290 based on the exported file's raw byte stream. This fingerprint 290 is saved as an additional verification field and is not included in the exported binding digest. For text content, the system can generate a fingerprint by standardizing line breaks, deleting invisible control characters, and merging consecutive whitespace characters. For structured fields, the system can generate a fingerprint by sorting them according to a preset field order or field names.

[0038] like Figure 3 As shown, before exporting, the system rereads the phase information object and the non-intrusive audit checklist 130, and generates a second phase status summary 210 according to the same field order as when the phase was committed. If the second phase status summary 210 is consistent with the first phase status summary 200, the export binding summary generation module 140 generates an export binding summary based on the second phase status summary 210, the exported file fingerprint 280, and the document assembly configuration fingerprint 300. The export binding summary is used to represent the binding relationship between a specific exported file, a specific phase status, and a specific assembly configuration.

[0039] If the target document is re-exported, the system recalculates the exported file fingerprint 280 based on the normalized exported file content, and regenerates the export binding summary based on the current second-stage state summary 210 and the document assembly configuration fingerprint 300. If the regenerated export binding summary is inconsistent with the export binding summary recorded in the non-intrusive audit checklist 130, the system blocks the export or generates an export review task. If the two are consistent, the system allows the export and updates the export time; the export time is saved as an audit field and is not included in the first-stage state summary 200, the second-stage state summary 210, and the export binding summary.

[0040] like Figure 4 As shown, when the second-stage status summary 210 is inconsistent with the first-stage status summary 200, the component comparison module 150 compares the stage output component summary, target stage input component summary, quality gate component summary, manually edited component summary, and rework record component summary in the component summary table 220, and outputs the output source location result 170. If the stage output component summaries are inconsistent, the output source location result 170 indicates the source of change in the stage output fingerprint 230; if the target stage input component summaries are inconsistent, the output source location result 170 indicates the source of change in the target stage input fingerprint 240; if the quality gate component summaries are inconsistent, the output source location result 170 indicates the source of change in the quality gate fingerprint 250; if the manually edited component summaries are inconsistent, the output source location result 170 indicates the source of change in the manually edited fingerprint 260; if the rework record component summaries are inconsistent, the output source location result 170 indicates the source of change in the rework record fingerprint 270.

[0041] The stage output fingerprint set includes both the recalculated stage output fingerprint and the retained stage output fingerprint 190. If any retained stage output fingerprint 190 is missing, or if the retained stage output fingerprint 190 is inconsistent with the most recent valid output reference, the system blocks the export or generates a review task. If the target stage input fingerprint 240 is inconsistent with the target stage input fingerprint 240 saved in the impact judgment record, the system determines that the retained stage input state has changed and generates an export review task.

[0042] In the case of input changes during the retention phase, the background technology generation phase was not hit by the local recalculation in this round, and its retention phase output fingerprint 190 is consistent with the most recently valid output reference. However, after the user submitted the phase, they modified the prior art material index, which is the input for that phase, causing the target phase input fingerprint 240 to be inconsistent with the target phase input fingerprint 240 in the impact judgment record. Based on this, the system determines that although the text of the retention phase has not changed, its valid input set has changed, and locates the retention phase input change through the target phase input component summary, thereby blocking the export or generating the export review task.

[0043] In the patent application document scenario, the system can write the claim output fingerprint 320, specification support mapping fingerprint 330, embodiment paragraph output fingerprint 340, drawing description fingerprint 350, drawing mark consistency check fingerprint 360, abstract output fingerprint 370, and quality gate fingerprint 250 into the first-stage state digest 200, and write the exported file fingerprint 280 and document assembly configuration fingerprint 300 into the exported binding digest. If the user modifies the technical features of the claims and only recalculates the specification support mapping stage and related embodiment paragraphs, the output fingerprints of the background technology and irrelevant drawing descriptions that are not recalculated still participate in the calculation of the second-stage state digest 210.

[0044] like Figure 5 As shown, the user modifies "first sealing edge" in claim 1 to "folded sealing edge." After the system completes the partial recalculation of the specification support mapping stage and related embodiment paragraphs, the stage submission control module 120 submits the temporary output area and generates the first stage status summary 200. Before exporting, the system rereads the claim output fingerprint 320, specification support mapping fingerprint 330, embodiment paragraph output fingerprint 340, drawing description fingerprint 350, drawing label consistency check fingerprint 360, summary output fingerprint 370, and quality gate fingerprint 250 to generate the second stage status summary 210. If the summary generation stage or drawing description stage is manually modified after submission, and the second stage status summary 210 is inconsistent with the first stage status summary 200, the system locates the change in the summary output fingerprint 370, drawing description fingerprint 350, or drawing label consistency check fingerprint 360 through the component summary table 220, and blocks the export through the export verification module 160.

[0045] In the scenario of regulatory application materials, the system can write the regulatory clause mapping fingerprint, test data attachment fingerprint, conclusion paragraph output fingerprint, and quality gate fingerprint 250 into the stage status summary, and write the exported file fingerprint 280 and document assembly configuration fingerprint 300 into the export binding summary. If only the conclusion paragraph is recalculated, the unrecalculated organization information and attachment index will still participate in the second stage status summary 210 verification by retaining the stage output fingerprint 190 and the target stage input fingerprint 240.

[0046] In the contract review report scenario, the system can write the contract clause parsing fingerprint, definition term fingerprint, risk conclusion fingerprint, and clause citation consistency check fingerprint into the stage status summary, and write the exported file fingerprint 280 and document assembly configuration fingerprint 300 into the export binding summary. If the clause citation consistency check fingerprint before export is inconsistent with the component summary in the first stage status summary 200, the system outputs a quality gate fingerprint 250 that is inconsistent and blocks the export. Example 3

[0047] This embodiment 3 provides an electronic device, specifically including one or more processors and a memory communicatively connected thereto. The memory stores computer program instructions, which, when called and executed by the processors, can fully implement the consistency verification method for the binding between the stage state and export of a professional document, as described in detail in embodiment 1. In other words, through the collaborative work of its internal hardware structure and software logic, this electronic device can perform consistency verification on the binding relationship between the different stage states of a document and its export operation during the processing of professional documents. This ensures that the state information of the document in each lifecycle stage remains strictly consistent with the actual export behavior, avoiding data inconsistencies or business logic errors caused by state mismatches. Example 4

[0048] This embodiment 4 provides a computer-readable storage medium, which may be, but is not limited to, a hard disk, solid-state storage, flash memory, optical disk, magnetic tape, or any other physical medium capable of storing program code and being read by a computer system. The computer-readable storage medium stores a set of computer programs. When these programs are loaded and executed by one or more processors, they can accurately and error-free implement the consistency verification method for professional document stage states and export binding as described in embodiment 1. By embedding the relevant program logic in this storage medium, any device with computing power can automatically execute the consistency verification process between different stage states and export operations of a professional document after reading and running the program, thereby improving the reliability, security, and automation level of the document management system.

[0049] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0050] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A method for verifying the consistency between the stage status of a professional document and its export binding, characterized in that, Includes the following steps: S1. Obtain the stage information object in the target document generation process. The stage information object includes stage identifier, stage output fingerprint (230), target stage input fingerprint (240), quality gate fingerprint (250), manual editing fingerprint (260), rework record fingerprint (270), failure status and most recent valid output reference. S2. Determine the set of recalculation stages based on the local recalculation results, and determine the set of retained stages based on the impact judgment records; obtain the recalculation stage output fingerprint (230) in the set of recalculation stages, the retained stage output fingerprint (190) in the set of retained stages, and the target stage input fingerprint (240) corresponding to the set of retained stages. S3. During stage submission, the recalculation stage output fingerprint (230), retention stage output fingerprint (190), target stage input fingerprint (240), quality gate fingerprint (250), manual editing fingerprint (260), and rework record fingerprint (270) are normalized according to the preset field order to generate the first stage status summary (200) and component summary table (220), and written into the non-intrusive audit checklist (130) which is saved alongside the target document but not written into the main text; among them, the retention stage output fingerprint (190) and the target stage input fingerprint (240) are both included in the first stage status summary (200) to distinguish the state where the main text of the retention stage has not changed but its effective input has changed; S4. Assemble the target document based on the latest valid stage output and document assembly configuration, and generate the export file fingerprint (280) based on the normalized export file content (310). S5. Before exporting the target document, reread the phase information object and non-intrusive audit list (130) and generate the second phase status summary (210) according to the same field order. S6. When the second-stage state summary (210) is inconsistent with the first-stage state summary (200), locate the source of inconsistency based on the component summary table (220) and block the export or generate the export review task. S7. When the second-stage state summary (210) is consistent with the first-stage state summary (200), an export binding summary is generated based on the second-stage state summary (210), the exported file fingerprint (280), and the document assembly configuration fingerprint (300), and the export binding summary is written into the non-intrusive audit list (130). S8. When exporting for review or re-exporting, regenerate the export binding summary and compare it with the export binding summary in the non-intrusive audit checklist (130). If they are inconsistent, block the export or generate an export review task.

2. The method for verifying the consistency between the stage status and export binding of a professional document as described in claim 1, characterized in that, The non-intrusive audit checklist (130) includes one or more of the following: task identifier, document type, configuration fingerprint, document assembly configuration fingerprint (300), stage node list, stage output fingerprint (230) set, target stage input fingerprint (240) set, quality gate fingerprint (250) set, manual editing fingerprint (260) set, rework record fingerprint (270) set, first stage status summary (200), second stage status summary (210), exported file fingerprint (280), exported raw byte stream fingerprint (290), exported binding summary, quality defect summary, component summary table (220), quality summary, evidence status summary, manual review status, and exported time; wherein, the exported time is not included in the first stage status summary (200), second stage status summary (210), and exported binding summary.

3. The method for verifying the consistency between the stage status and export binding of a professional document as described in claim 1, characterized in that, Generating the first-stage status summary (200) and the second-stage status summary (210) includes: sorting the structured fields according to a preset field order or field name; unifying the line breaks in the text content, deleting invisible control characters and merging consecutive whitespace characters; generating the stage output component summary, the target stage input component summary, the quality gate component summary, the manual editing component summary and the rework record component summary respectively; generating the export binding summary includes: normalizing the second-stage status summary (210), the export file fingerprint (280) and the document assembly configuration fingerprint (300) according to a preset field order.

4. The method for verifying the consistency between the stage status and export binding of a professional document as described in claim 1, characterized in that, Determining the set of retention stages includes: reading the impact judgment record, which includes the candidate downstream stage set, the affected stage set, the retention stage set, the impact judgment result, the retention stage output fingerprint (190), the target stage input fingerprint (240), and the retention reason; when the impact judgment result indicates that the corresponding stage is not affected by the manual editing event and the target stage input fingerprint (240) has not changed, the corresponding stage is determined as the retention stage.

5. The method for verifying the consistency between the stage status and export binding of a professional document according to claim 1, characterized in that, The set of stage output fingerprints (230) includes both recalculated stage output fingerprints (230) and retained stage output fingerprints (190). When any retained stage output fingerprint (190) is missing, any target stage input fingerprint (240) is missing, the retained stage output fingerprint (190) is inconsistent with the most recent valid output reference, or the target stage input fingerprint (240) is inconsistent with the impact judgment record, the system blocks the export or generates a review task.

6. The method for verifying the consistency between the stage status and export binding of a professional document according to claim 1, characterized in that, The partial recalculation result is first written to the temporary output area, which includes a temporary output reference, a temporary output fingerprint, a temporary quality gate fingerprint (250), and a temporary rework record fingerprint (270). When the quality gate review passes, the system submits the temporary output area as the most recent valid output and writes the temporary rework record fingerprint (270) to the non-intrusive audit list (130). When the quality gate review fails, the system rolls back the temporary output area and maintains the first-stage state summary (200) before the stage submission.

7. The method for verifying the consistency between the stage status and export binding of a professional document according to claim 1, characterized in that, When the second-stage status summary (210) is inconsistent with the first-stage status summary (200), the system compares the stage output component summary, target stage input component summary, quality gate component summary, manual editing component summary and rework record component summary in the component summary table (220) respectively, and outputs the source of stage status inconsistency; when the export binding summary verification fails, the system compares the second-stage status summary (210), export file fingerprint (280) and document assembly configuration fingerprint (300) respectively, and outputs the source of export binding inconsistency.

8. The method for verifying the consistency between the stage status and export binding of a professional document according to claim 1, characterized in that, When the target document is a document package file, the system reads the relevant files in the main text according to the file path order in the package, filters one or more non-main text changes from the creation time, modification time, application version number, compressed package entry order, temporary relationship number and preview thumbnail, and generates an export file fingerprint (280) based on the main text, paragraph level, table content, image reference relationship and export format configuration.

9. The method for verifying the consistency between the stage status and export binding of a professional document according to claim 1, characterized in that, When the target document is a patent application document, the system writes the claim output fingerprint (320), specification support mapping fingerprint (330), embodiment paragraph output fingerprint (340), drawing description fingerprint (350), drawing label consistency check fingerprint (360), abstract output fingerprint (370), quality gate fingerprint (250), exported file fingerprint (280), and document assembly configuration fingerprint (300) into a non-intrusive audit checklist (130); when any of the fingerprints before export is inconsistent with the corresponding component in the first stage status summary (200) or the export binding summary, the system blocks the export or generates a patent document export review task.

10. A system for verifying the consistency between the stage status and export binding of a professional document, comprising employing the method for verifying the consistency between the stage status and export binding of a professional document as described in claims 1 to 9, characterized in that... include: The stage status reading module (100) is used to obtain stage information objects; The retention phase identification module (110) is used to determine the retention phase set based on the impact judgment record; the phase submission control module (120) is used to submit the temporary output area when the quality gate review is passed, and roll back the temporary output area when the quality gate review is not passed; the phase status summary generation module is used to generate the first phase status summary (200), the second phase status summary (210) and the component summary table (220); the audit list generation module is used to generate and save the non-intrusive audit list (130); the export file fingerprint (280) generation module is used to generate the export file fingerprint (280) based on the normalized export file content (310), and generate the export original byte stream fingerprint (290) as an additional verification field; the export binding summary generation module (140) is used to generate the export binding summary based on the second phase status summary (210), the export file fingerprint (280) and the document assembly configuration fingerprint (300); the component comparison module (150) is used to locate the source of inconsistency in the phase status or the source of inconsistency in the export binding; the export verification module (160) is used to block the export or generate an export review task when the summary is inconsistent.

11. An electronic device, characterized in that, It includes a processor and a memory, the memory storing a computer program executable by the processor, the computer program, when executed by the processor, implementing the professional document stage state and export binding consistency verification method according to any one of claims 1 to 9.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the consistency verification method for professional document stage status and export binding as described in any one of claims 1 to 9.

Images