Brief annotation
About the document
A model of the flow of documents, decisions and responsibility within the development management system.
Ideal_Document_Flow_SUR.pptx
Downloading the document...
DOCUMENT → DECISION → EXECUTION → RESULTS → MEMORY
The architecture of transition from files, folders and approvals to a single life cycle of powers, versions, electronic signatures, execution and proof of result
Integration: SUR • KRISTALL741 • EQUILIBRIUM • SFERA • ECO-PPA • SUR-810 • ESG-IR 1.0
Author: Sergey Leonidovich Sokolov
Version 1.0 | 27 August 2026
STATUS
Passport Concept
| Parameter | Value |
|---|---|
| Object | Full life cycle of management documents and related evidence |
| Goal | One-time creation of a reliable document and its repeated legal use without loss of context |
| Control unit | Authoritative record: content + Metadata + Authority + Version + Signature + Communications + status + storage life |
| Architecture | Federated: the original is kept by the authorized owner; SES links identifiers, statuses and evidence |
| Result | From the decision you can go to the base, performer, resource, fact of execution, result and archival fate |
| Border | The system does not replace the powers of authorities, secrecy regimes, official archives and owners of state information systems. |
MAIN
Summary for decision
Modern workflow often optimizes file transfer, but does not eliminate the gap between the content of the document, the author’s authority, version, approval, management decision, execution and proven result. As a result, a digital file exists, and a single decision history is split between mail, folders, departmental systems and reports.
The target model considers the document as an active control object. It has an immutable identifier, metadata passport, owner, status, route, timeline, access rights, digital signatures, links to other documents, and event logs. The approved version becomes an authoritative record, not another copy of the file.
In SUR, the document is linked to the KRISTALL741 balance management system, the indicators of Catalogue 260, EQUILIBRIUM analytics, ECO-PPA project execution, the SUR-810 settlement trail and ESG-IR 1.0 validation. This forms a continuous chain from a signal to archival memory and the reuse of knowledge.
DECISION
Proposed management solution
- To approve the development of a target model of the ideal document flow as an outline of the Development Management System.
- Determine the state or corporate process of the pilot, the owner of the result and the list of participating information systems.
- Approve a single document passport, ID, classifier, status model and mandatory event log.
- Ensure legally significant signing through acceptable types of electronic signature and trusted infrastructure.
- Exclude creation of parallel originals: one authoritative record, controlled submissions and verifiable copies.
- Link the document to the decision, order, project, resource, execution, result indicator and storage period.
- Following the results of the pilot, submit regulatory, organizational, information, archival and economic assessments.
DEFINITION
What is the ideal document flow
The ideal workflow is a system for creating, registering, using, executing, proving, storing and legally destroying documents, in which the authenticity, authenticity, integrity, usability and context of each record are preserved.
| Property | Practical meaning |
|---|---|
| Authenticity | You can prove the origin of the document, author, authority and method of signing |
| Credibility | The content correctly reflects the operation, decision or event |
| Integrity | Unauthorized change detected, versions distinguishable |
| Suitability | The document can be found, opened, understood and used in an acceptable process |
| Context | Relations with the case, participants, grounds, decisions and events are maintained |
| Traceability | Seen full story from creation to execution and archival destiny |
DIAGNOSIS
Why the usual electronic document flow is insufficient
- files are duplicated in mail, messengers, network folders and several EDMS;
- the file name is used instead of a stable ID and passport;
- approval captures the opinion, but does not always check the authority, data and risks;
- the approved version is separated from the order, resource and actual execution;
- event report replaces the proof of change in the result;
- the storage period is determined late or is not associated with the class of the document;
- when changing the system, the context, the log of actions and legal evidence are lost;
- The search returns the documents, but does not explain which one is valid and why.
ARCHITECTURE
The Ten Principles of the System
| Principle | Rule |
|---|---|
| One original | For each legally significant state, one authoritative record is determined. |
| Default Context | Document does not exist without cause, process, owner, reason and purpose |
| Authority before signature | Checks not only the certificate, but also the right of the person to make a specific decision |
| Version as event | Each change creates a new version with a base and author |
| Eventivity | The route is described by an event log, not by moving copies |
| Federality | Data remains with the owners; intersystem exchange is on standard passports |
| Minimizing access | Access is issued by role, purpose, information class, phase and deadline |
| Evidence | Execution ends with confirmation of the result, not a change of status |
| Archive since creation | Term and archival fate are appointed at registration |
| Reversibility | Critical actions have stop conditions, rollback and standby mode |
ARCHITECTURE
Seven Layers of Target Architecture
| Layer | Purpose | Result |
|---|---|---|
| 1. Normative | Powers, regulations, standards, terms of storage | Legal model of the document |
| 2. Semantic | Classifiers, ontology, 741, catalog 260 | Common language and address |
| 3. Documental | Contents, props, versions, presentations | Authoritative record |
| 4. Process | Routes, roles, timelines, escalations, assignments | Controlled movement |
| 5. Trusted | Identification, credentials, EP, time stamps | Proved will |
| 6. Evidentiary | Relationship of decision, resource, execution and result | Full file |
| 7. Archival and analytical | Storage, value examination, search, re-knowledge | Institutional memory |
LIFE CYCLE
Thirteen phases of the life cycle
| Code | Phase | Benchmark |
|---|---|---|
| D01 | Need | A task, event, or reason is recorded |
| D02 | Classification | Determine the type, case, mode, template and shelf life |
| D03 | Data collection | Verified sources and previous solutions are connected |
| D04 | Preparation | A draft and passport of the document is created |
| D05 | Factual verification | Check data, formulas, references and completeness |
| D06 | Law and safety | Rules, powers, access and risks are checked |
| D07 | Harmonization | Positions, comments and resolution of disagreements are recorded |
| D08 | Approval and signature | The expression of will is associated with a specific version |
| D09 | Registration | Assign number, date, status and authoritative storage |
| D10 | Advertise | Recipients receive a verifiable submission and commitment |
| D11 | Implementation | The document is associated with actions, resources and deadlines |
| D12 | Acceptance and Validation | Confirmed performance and measurable result |
| D13 | Archive, destruction, re-knowledge | The fate of the recording is completed and the applicable knowledge is retained |
LIFE CYCLE
Document Status Model
The status of the document is determined by the event and a set of fulfilled conditions. The user should not manually select the status if the system can deduce it from signatures, route and execution facts.
| State | Entry condition | Allowed output |
|---|---|---|
| Project | Passport and first version created | To check or close |
| Under review | Auditing and control issues are assigned | For finalization or approval |
| In agreement | Facts, Law and Security Passed | To sign or resolve a dispute |
| Approved | Signature valid, authorization confirmed | For registration |
| In effect | Registration completed and due to expire | For execution, modification or cancellation |
| Executed | Obligatory actions completed | On reception |
| Verified | Results accepted and validated | To archive or new cycle |
| Replaced / Cancelled | There is a new decision or act of cancellation | To archive |
| Archival | Finished office work, assigned storage mode | Valuation / Destruction |
CLASSIFICATION
Document classes and control modes
| Class | Examples | Feature |
|---|---|---|
| Strategic | Strategy, doctrine, concept, program | Long horizon and inter-documentary links |
| Normative | Regulation, regulation, standard, methodology | Monitoring relevance and scope |
| Managing | Decision, order, order, order | Authority, addressees, time frame and control |
| Project | Passport, plan, assignment, protocol, act | Linkage to stage, resource and result |
| Contractual | Contract, agreement, additional agreement | Commitments, counterparties, versions and signatures |
| Financial | Estimate, limit, account, payment basis | Accounting, control and communication with SUR-810 |
| Science and technology | Report, calculation, model, drawing, data set | Reproducibility and origin |
| Evidentiary | Acceptance certificate, test report, photo, measurement | Independence, time and reference to the criterion |
| Correspondence | Letter, request, reply, appeal | Route, timing and connection to the case |
| Archival complexes | Case, Inventory, Electronic Container | Integrity of the composition and long-term preservation |
CLASSIFICATION
Single ID and document address
| Element | Value |
|---|---|
| SUR-DOC | Object class — SUR document |
| B16 | Financial and investment balance management system |
| L10 | The resource and calculation model phase of KRISTALL741 |
| S1 | Federal scale |
| 2026 | Year of primary registration |
| 000001 | Invariant ordinal identifier |
| V03 | Third version of content |
The identifier does not replace the registration number of a particular system. It serves as the end-to-end address for communication between documentary, project, financial, analytical and archival contours.
METADAN
Universal Document Passport
The passport connects the content of the document with its context, authority, versions, execution and archival fate.
| Group | Required fields |
|---|---|
| Identification | Code, name, type, language, format, date of creation |
| Context | Process, business, balance system, phase, scale, project |
| Responsibility | Author, content owner, result owner, operator |
| Right | Basis, authority, applicable rules, regime of information |
| Version | Number, reason for change, author of change, date, status |
| Harmonization | Route, participants, positions, comments, resolution of disagreements |
| Authorized officer | EP view, certificate, time, inspection result, power |
| Connections | Parent, applications, replaceable documents, decisions, instructions |
| Implementation | Addressee, action, time, resource, reference point |
| Evidence | Acts, measurements, sources, validator, result |
| Access | Class, Roles, Purpose, Term, Copy Limitations |
| Archive | Nomenclature of the case, shelf life, countdown event, fate |
GOVERNANCE
Powers and roles
| Role | Responsibility | Can't. |
|---|---|---|
| Initiator | Formulates the need and expected result | Independently approve outside the authority |
| Author | Creates content and confirms sources | Hide the origin of borrowed data |
| Owner of Content | Responsible for relevance and correctness | Delete Version History |
| Lawyer / Compliance | Checks rights, risks and restrictions | Substitute the owner of the management decision |
| Agreeing | Fixes position within competence | Agree for another participant |
| Approving | Makes a decision and signs a specific version | Delegate signature without legal basis |
| Registrar | Assigns a number and records an authoritative record | Change the approved content |
| Person carrying out the work | Performs action and applies evidence | Independently accept your own result |
| Validator | Independently checks the result | Modifying Primary Evidence |
| Archivist | Manages the case, time and archival fate | Exterminate outside of approved procedure |
GOVERNANCE
Consent without loss of responsibility
The ideal route does not seek to obtain the maximum number of visas. It includes only those participants whose competence is necessary for the quality and legality of the decision.
- The system defines mandatory checks by type of document, risk and information mode.
- Each conciliator receives a list of questions of their competence, rather than a general request to “agree”.
- The comment contains the norm, the risk, the proposal of change and the degree of criticality.
- Parallel agreements are carried out simultaneously; dependent ones - only after the completion of the necessary predecessor.
- Disagreement is not hidden by a new copy: a formal decision on position and basis is created.
- The expired deadline causes an escalation to the process owner, but does not mean automatic consent for critical documents.
TRUST
Versions, changes and cancellations
| Operation | Mandatory fixation | Result |
|---|---|---|
| Black change | Author, time, modified fragments | New working version |
| Substantial revision | Base, comparative report, rechecks | A new agreed version |
| Bug Fix | Error description, influence, decision maker | Fixed version with original version |
| Extension | Legal basis and new date | New version of validity period |
| Replacement | Link to new document and termination date | The previous document receives the status of "replaced" |
| Cancel | Cancellation Act, grounds, date and consequences | Status "cancelled", content saved |
TRUST
Electronic signature and trusted time
The choice of the type of electronic signature is determined by law, the agreement of the participants and the risk of the operation. For each route, a valid type of signature, method of identification, certificate verification, credentials and trusted time are specified in advance.
| Monitoring | Question to be checked |
|---|---|
| Identity | Who owns the key and was the certificate valid at the time of signing? |
| Credentials | Did the person have the right to sign exactly this type of document and the amount/perimeter? |
| Version | What exact set of bytes and applications were signed? |
| Time | When did the signing take place and what source confirmed the time? |
| Integrity | Did the document change after signing? |
| Long-term verification | Are the data required to verify the signature after the certificate expires? |
| Introduction | Does the visual form match the signed content and structured data? |
PROOF
Origin Metadata and Event Log
Metadata should tell the story of the document: who, what, when, why, and on what basis did it with a specific digital object. The journal stores events, not just the last values of fields.
| Event | Minimum composition |
|---|---|
| Establishment | Author, source, template, original version, time |
| Change | Previous version, new version, differences, base |
| View / Unload | Subject, role, purpose, object, time, channel |
| Harmonization | Position, competence, comment, signature, time |
| Approval | Person, power, version, signature, trusted time |
| Registration | Number, system, registrar, authoritative repository |
| Implementation | Action, executor, resource, deadline, proof |
| Verification | Method, validator, result, limitations |
| Archival Action | Case, term, value examination, transfer or destruction |
PROOF
End-to-end evidence chain
- each relationship has a type, author, time, reason and direction;
- loss of mandatory communication creates a quality signal and can block the route;
- the proof cannot be considered a result without the acceptance criterion and validator;
- the archive record saves not only the file, but also the necessary verification context;
- The search does not show a list of similar documents, but an existing authoritative chain.
SUR INTEGRATION
A document in KRISTALL741
Each management document receives an address of the balance system, phase and scale. This allows you to understand not only the theme of the file, but also its function in a closed control loop.
| Code | Document Function | Example |
|---|---|---|
| B01–B19 | Balance Management System | B12 - water balance |
| L01–L13 | Management cycle phase | L09 - Legal Expertise and Security |
| S1–S3 | Scale | S2 - Regional / Interregional |
| DOC | Object class | Document, application, proof, data set |
| Vxx | Version | V04 - The fourth substantial version |
SUR INTEGRATION
Roles of the ecosystem
| Component | Document role | Withdrawal |
|---|---|---|
| EQUILIBRIUM | Sources, models, scenarios and analytical findings | Verifiable basis of the decision |
| GASMP | Observation events and early signals | Primary Signal with Origin |
| SFERA | Registration of initiatives and public feedback | Initiative card and route |
| KRISTALL741 | Classification of the document by system, phase and scale | Cross address |
| ECO-PPA | Passports, agreements and resource commitments | Executable project package |
| SPECZASHCHITA | Executive documents and primary evidence | Fact of action |
| SUR-810 | Relationship of the document with the obligation and the ruble settlement event | Calculated footprint |
| ESG-IR 1.0 | Methodology, acceptance and independent validation | Confirmed result |
INFORMATION MODEL
Minimum set of registers
| Register | Key objects |
|---|---|
| Documents | Identifier, type, version, status, owner, storage |
| Cases and processes | Process, case, stage, relationships, timing |
| Participants and credentials | Person, organization, role, power of attorney, limit |
| Classifiers | 741, 260, types of documents, modes, nomenclature of cases |
| Routes | Checks, approvals, signatures, escalation |
| Decisions and instructions | Decision, addressee, action, deadline, control |
| Projects and resources | Project, commitment, limit, settlement status |
| Evidence | Source, method, criterion, result, validator |
| Events | Action, Subject, Object, Time, Basis, Result |
| Archival fate | Term, countdown event, examination, transfer, destruction |
INFORMATION MODEL
Formats, Compatibility and Migration
- Content and metadata are shared separately but linked by a single identifier.
- structured data is stored together with human-readable representation;
- the exchange format includes the versions of the scheme, mandatory fields and verification rules;
- Migration confirms the number of objects, checks, connections and results of the check;
- long-term storage does not depend on a single application software product;
- each integration has an owner, SLA, backup mode and error handling protocol;
- The replacement of the information system should not change the identifier and legal history of the document.
SAFETY
Access, protection and minimization
The decision on access is formed by five dimensions: the role of the subject, the business purpose, the information class, the process phase and the allowable period. The fact of access does not mean the right to copy, distribute or modify.
| Monitoring | Requirement |
|---|---|
| Identification | Confirmed account and multi-factor authentication |
| Authorization | Minimum authority over role and case |
| Segmentation | Separation of open, service, confidential and special contours |
| Copy | Control of discharge, marking of submissions and watermarks as necessary |
| Encryption | Protection during transfer and storage by information class |
| Journaling | Unchangeable access trail and critical actions |
| Review | Automatic termination of access when changing role, case or term |
| Response | Signals, isolation, investigation, recovery and notifications |
SAFETY
Personal data, privacy and critical infrastructure
| Category | Project requirement |
|---|---|
| Personal data | Legal basis, minimization, purpose of processing, localization when applicable, deadline and deletion |
| A trade secret | List of information, regime, marking, accounting of persons and contractual obligations |
| Official information | Departmental rules, restriction of distribution and registration of extradition |
| State secrets | Separate protected contour and compliance with the established mode |
| KII | Categorization, safety requirements and interaction with the competent authorities, if applicable |
| Archival documents | Maintain access restrictions along with document and metadata |
ARCHIVE
Archival fate begins at registration
- When classifying a document, it receives the position of the case nomenclature and a preliminary storage period.
- The system records the event from which the term is calculated: completion of the case, termination of the contract, dismissal, replacement of the document or other grounds.
- The document is bundled with metadata, signatures, applications, and the necessary verification context.
- At the end of the process, an electronic case is formed with the control of completeness and integrity.
- The value examination determines permanent, long-term, temporary storage or destruction.
- Destruction is performed by act, after expiration of deadlines and removal of locks, with the event log.
- Knowledge that is no longer valid can be reused only with an explicit label of status and origin.
AUTOMATION
Artificial Intelligence in Document Management
| AI | AI should not be on its own |
|---|---|
| classify the document and propose a route | Making a legally significant decision |
| extract details and check completeness | Signing for an Authorized Person |
| find contradictions, duplicates and outdated links | hide uncertainty or source of output |
| compare versions and summarize comments | Modify the approved version |
| propose related documents and precedents | Expand access to private data |
| control timing and generate early signals | Automatically close critical order |
| prepare a draft dossier and archival inventory | determine the archival fate without an authorized procedure |
AUTOMATION
Automatic Routing Rules
| Signal | Automatic action |
|---|---|
| No required props | Return to author before start of approval |
| Invalid or outdated link | Prevention and appointment of factual verification |
| No confirmed authority | Signature Blocking |
| Changed content after approval | Cancellation of dependent approvals |
| Critical disagreement | Transfer to the owner of the process; prohibition of automatic approval |
| Expiration date | Escalation to the owner of the result and fixation of the deviation |
| The proof is not related to the criterion | Prohibition of closure of the order |
| Expires on storage | Start examination; not automatic destruction |
| Infringed integrity | Site isolation and security incident |
MEASUREMENT
Indicators of ideal document flow
[M] values are model pilot targets, not government regulations. After two months of observation, they are specified on the basis of the baseline.
| Indicator | Model threshold | Meaning |
|---|---|---|
| Authoritative record is defined | 100% | No competing originals |
| Completeness of mandatory metadata | ≥99,5% [M] | Document can be understood and verified |
| Confirmed powers of signatories | 100% | Barrier to legal significance |
| Agreement without sending copies | ≥95% [M] | Working with one version |
| End-to-end solution - result | ≥99% [M] | Full evidentiary file |
| Search for the current version, P95 | ≤30 seconds [M] | Fast availability of knowledge |
| Formation of a complete dossier, P95 | ≤15 Minutes [M] | Readiness for control |
| Overdue critical orders | 0 | Stop-indicator |
| Unauthorized changes | 0 | Stop-indicator of integrity |
| Documents without archival fate | 0 | Managed Storage |
IMPLEMENTING
Pilot: 30 / 100 / 365 days
| Timeframe | Works | Gateway Result |
|---|---|---|
| 0–30 days | Process selection; map of systems; inventory of documents, credentials, signatures, archival requirements | Borders, owner and base line approved |
| 31–100 days | Single passport, ID, classifier, statuses, route, access model, prototype | Go / revise / stop for a working pilot |
| 101–180 days | Shadow mode: parallel comparison with the current process without changing the legal contour | Completeness and correctness confirmed |
| 181–300 days | Limited working mode, trusted signature, execution register, evidence | Stop conditions and KPI are met |
| 301–365 days | Archival completion, stress test, recovery, independent evaluation and scaling package | Decision on termination, revision or scale |
IMPLEMENTING
Road map to 2030
| Stage | Focus | Result |
|---|---|---|
| 2026 | Methodology and legal model | Passport, classifier, rules of trust and pilot regulations |
| 2027 | Limited pilot | Verified chain of document, execution and archive |
| 2028 | Intersystem compatibility | Federal Registers, API, common event dictionary |
| 2029 | Scaling to portfolios | Standard routes for strategic and project documents |
| 2030 | Managed Document Environment for SDS | Cross-linking goals, decisions, resources, results and memory |
RISKS
Key risks and measures
| Risk | Manifestation | Measure |
|---|---|---|
| Parallel originals | Some "final" versions | Authoritative record and register of submissions |
| Formal digitalization | Scan Instead of Managed Recording | Passport, Events and Structured Data |
| Signature without credentials | Certificate valid, decision invalid | Automatic role and limit testing |
| Excess approvals | Deceleration without quality gain | Matrix of mandatory competencies |
| Leakage | A single search reveals private information | Federal index and minimization of extradition |
| AI-hallucination | Incorrect fact or reference | Origin, confidence and human verification |
| Dependence on supplier | Inability to migrate | Open export schemes and regular testing |
| The Archive Gap | Signature or format not verified years later | Long-term Validation and Migration |
| Substitution of result | Status "executed" without effect | Acceptance criteria and independent validation |
DRAFT DECISION
Draft instruction
Proposed wording for further legal development:
- Prepare proposals for the creation of a pilot outline of the ideal document flow as part of the Development Management System of the Russian Federation.
- Determine the owner of the result, operator, pilot object, participating bodies and information systems.
- Within a period of up to 100 days, develop a single document passport, identifier, classifier, status model, event log and archive fate rules.
- Ensure the use of electronic signature, verification of authority, integrity and trusted time in accordance with applicable requirements.
- Establish the principle of one authoritative record and prohibit the uncontrolled formation of parallel originals.
- Link the pilot’s documents with decisions, instructions, resources, execution, evidence, and measurable results.
- Conduct an independent legal, informational, archival and cybernetic assessment.
- Following the results of 12 months to submit proposals for the termination, revision or scaling of the model.
PLAN OF ACTION
The first 100 days: ten results
| Result | Acceptance criterion |
|---|---|
| Mandate and boundaries | There is a customer, the owner of the result, the process and the list of systems |
| Map of current status | Fixed documents, copies, routes, deadlines and problems |
| Legal model | Qualified documents, signatures, data and archival requirements |
| Classifier | Defined types, 741-address, modes and nomenclature of cases |
| Passport document | Mandatory metadata and quality rules approved |
| Status model | Every transition has an event, conditions, role and prohibition |
| Trusted route | Verify version, signature, authority and time |
| Evidence-based model | The document is related to the order, resource, action and result |
| Archival model | Appointed date, countdown event, case and completion procedure |
| Prototype and Gateway | Shown end-to-end script and decided go / revise / stop |
CONCLUSION
Final position
The ideal workflow transforms a document from a file and an administrative footprint into a manageable medium of authority, decision, action, and institutional memory. It does not start with the purchase of a new EDMS: it begins with a single model of authoritative record, responsibility, metadata, events, and evidence.
In the SUR architecture, each document is assigned a place in one of the 19 balance management systems, a life-cycle phase and a scale of KRISTALL741. Catalogue 260 sets measurable requirements; EQUILIBRIUM provides the analytical basis; ECO-PPA, the project commitment; SUR-810, the settlement trail; and ESG-IR 1.0, validation of the result.
The ideal document doesn’t just exist. He explains who created him and why, what he changed, how he was executed, and what result he left behind.
ANNEX A
Official sources and standards
1. GOST R 7.0.97-2025 - requirements for the preparation of organizational and administrative documents
2. GOST R ISO 15489-1-2019 - document management: concepts and principles
3. GOST R 7.0.101-2018 / ISO 30301 — document management systems: requirements
4. GOST R ISO 30302-2022 — Guide for the implementation of the document management system
5. ISO 23081-1-2008 - metadata for documents
6. Federal Law No. 63-FZ "On Electronic Signature"
7. Federal Law No. 149-FZ "On Information, Information Technologies and Information Protection"
8. Federal Law No. 152-FZ "On Personal Data"
9. Federal Law No. 125-FZ "On Archival Affairs in the Russian Federation"
10. Federal Law No. 187-FZ "On the Security of Critical Information Infrastructure of the Russian Federation"
11. Order of Rosarchiv No236 — list of standard management archival documents and storage periods
12. ISO 23081 — metadata for records
ANNEX B
Glossary
| Term | Definition |
|---|---|
| Authoritative record | Document, which is given the status of an official and controlled copy by the established rules |
| Document | Information and related context created or received as evidence and business asset |
| Introduction | A human-readable or machine form of authoritative writing that does not create a new original |
| Passport document | Structured Metadata Set Required for Management and Verification |
| Event | The recorded action of a subject or system over a particular object |
| Version | Condition of detention resulting from controlled change |
| Credentials | Confirmed right of a person to perform a specific action within the specified limits |
| Trusted time | Event time confirmed by an acceptable source and suitable for verification |
| Electronic case | A set of interrelated documents, metadata, and events of a single process or issue |
| Archival fate | The established term and procedure for storing, transferring or destroying the record |
| Evidentiary dossier | Linked set of grounds, decisions, execution, resources and confirmation of the result |
ANNEX C
Methodological reservations
- The concept describes the target model and does not replace the survey of a specific process and information systems.
- The term “perfect” refers to the completeness of the management cycle, not the absence of errors or absolute automation.
- The unified architecture is compatible with federated storage and does not require the centralization of restricted access documents.
- The electronic signature is applied only in the permissible legal and contractual regime.
- AI supports classification, search and control, but does not replace authority and legal liability.
- Model KPI [M] are specified after the baseline and are not normative or promise effect.
- Storage periods and archival fate are determined according to the current lists, nomenclature of cases and expertise of value.
- Scaling is allowed after independent verification of the right, security, portability, archival integrity and actual result.
End of document
Source materials
Originals and versions of the document
- Ideal_Document_Flow_SUR.docxDOCX · main document
- Ideal_Document_Flow_SUR.pptxPPTX · related version
Other editions in web format
Each version is disclosed separately; the sequence of the source document is saved.
THE PERFECT DOCUMENTWORKIdeal_Document_Flow_SUR.pptx · web text+
National system of managed documents and evidence
AUTHORITY
RECORDS
DOCUMENT → DECISION → EXECUTION → RESULTS → MEMORY
Unified life cycle of powers, versions, electronic signatures, execution and evidence of the result
Author: Sokolov Sergey Leonidovich | version 1.0 | 27 August 2026
Not “without paper”, but without a break in responsibility
DECISION
Normal electronic circulation
The ideal document flow
Moves files, records visas, and stores copies. But context, authority, version, execution, and archival destiny often live apart.
Manages the authoritative record: who and on what basis created, approved, performed, checked and saved the result.
Solution: to design the outline of the managed documents and evidence of the SDS
Sokolov Sergey Leonidovich
The file moves — the management sense is broken
DIAGNOSIS
COPY
FILE NAME
VISA
REPORTS
Mail • Messengers • Folders
Instead of a sustainable address
without verification of authority
Instead of proof of result
When a system changes, connections, event logs, and legally relevant context are lost.
Targeted transition: from sending files to managing responsible records
Sokolov Sergey Leonidovich
The formula of authoritative record
DEFINITION
Contents
Context
Credentials
Version
Authorized officer
Connections
Status
Archive
Evidence
Document = Contents + context + Authority + Version + Signature + Communications + status + storage life + evidence
Sokolov Sergey Leonidovich
One original - multiple controlled performances
TRUST
Work
Editable form
You can't
AUTHORITY
RECORDS
create multiple independent "final" files without a common address and history
Signed
Unchanged version
Printable
visual representation
Machine
The new version does not erase the old one - it becomes its proven successor.
Structured data
Sokolov Sergey Leonidovich
Thirteen Phases - One Closed Circuit
LIFE CYCLE
D01
D02
D03
D04
D05
D06
D07
Need
Classification
Data collection
Preparation
Fact check
Law and protection
Harmonization
D08
D09
D10
D11
D12
D13
Authorized officer
Registration
Advertise
Implementation
Acceptance
Archive / Knowledge
Result D12 and knowledge D13 become input for new need D01
Sokolov Sergey Leonidovich
Status is determined by the event, not the folder name
STATE
Project
Verified
Agreed
Approved
In effect
Executed
Verified
Archival
Created a passport
verified facts
Allowed Positions
signed version
delivered to the addressees
there is evidence
result validated
Fate is appointed
You cannot delete or rewrite the approved version: only replace it with the same base
Sokolov Sergey Leonidovich
Passport turns a file into a manageable document
METADAN
IDENTIFICATION
CONTACTS
RESPONSIBILITY
LAW
code • type • format • date
Process • Balance • Phase • Project
Author • Owner • Operator
Base • Power • Mode
VERSION AND SIGNATURES
LINKS
EXECUTION
ACCESS AND ARCHIVES
Change • certificate • time
Solution • Order • Application
address • term • resource • result
Role • Term • Destiny
Minimum: without a passport, the file remains an information object, but not an authoritative record
Sokolov Sergey Leonidovich
A single identifier connects all contours
ADDRESS
SUR-DOC-B16-L10-S1-2026-000001-V03
SUR-DOC
B16
L10
2026
000001
V03
Class
Balance
phase 741
scale
Year
Room
Version
The identifier does not replace the EDMS number - it creates a through address between systems
Sokolov Sergey Leonidovich
The right to be checked before signing
CREDENTIALS
Identity
Role
Basis
Who is acting
In what capacity
Why he has the right
Limit
Version
Time
What decisions are acceptable
What exactly is signed
When and for how long
A valid electronic signature does not correct a lack of authority or a false document
Sokolov Sergey Leonidovich
Examination is distributed - approval personally
Alignment
FACT
LAW
SAFETY
FINANCE
Sources • calculations
norm • power
mode • access
Resource • Commitment
CONFIRMING
Decide on a specific version
The disagreement is fixed and allowed - a new copy does not hide it
Sokolov Sergey Leonidovich
The event magazine explains the history of the document
ORIGIN
Created by
CHANGES
VERIFIED
SIGNED
PERFORMED
ARCHIVED
Author • source
Version • Base
Control • result
certificate • time
Action • Resource
term • fate
Minimum Event Composition
Who • What • When • Why • On what basis • with which version • What result
Sokolov Sergey Leonidovich
The document links the decision with the result
PROOF
Basis
Data
Project
Expertise
Credentials
Authorized officer
The Commission
Resource
Implementation
Acceptance
Result
Archive
The control question is: is it possible to restore the complete dossier of the solution in 15 minutes?
Sokolov Sergey Leonidovich
Seven Layers - Uniform Rules Without a Single Monolithic Base
ARCHITECTURE
NORMATIVE
Authority • Standards
SEMANTIC
Classifiers • ontology
DOCUMENTARY
Content •
PROCESS
Routes •
TRUSTED
identity • signature
EXPLANATORY
performance • result
ARCHIVE
term • fate
Sokolov Sergey Leonidovich
KRISTALL741 defines the address — the document proves the action
SUR INTEGRATION
19 BALANCES
CATALOGUE 260
what is managed
What type and rule
CONTROLLED
DOCUMENT
KRISTALL741
SUR-810
Where and in what phase
What a calculated trail.
EQUILIBRIUM Confirms the balance • ESG-IR 1.0 Confirms the result
Sokolov Sergey Leonidovich
Minimum set of general information
REGISTERS
Documents
Cases and processes
Participants
Classifiers
ID • status
Context • Term
Roles •
741 • 260 • types
Routes
Events
Evidence
Archival fate
• Approval
who • that • when
source • validator
Term • Destruction
Integration is based on a common data contract, not the same software
Sokolov Sergey Leonidovich
Access is defined by role, purpose and time
PROTECTION
IDENTITY
AUTHORIZATION
SEGMENTATION
Confirmed Subject
Role and Authority
contour and class
WRITING
JOURNAL
RESPONSE
during transfer and storage
Invariable footprint
Isolation and Recovery
A single search does not mean a single view: the result is disclosed only within the legitimate purpose
Sokolov Sergey Leonidovich
Archival fate begins at registration
ARCHIVE
Case • List • Mode • Provisional
Classification
Case completion • contract termination • record replacement
Countdown Event
Metadata • Signatures • Application • Version
Completeness control
Permanent • Long • Temporary Storage
Examination of value
Transfer • re-knowledge • act of destruction
Fulfillment of destiny
The archive is not a warehouse: it provides long-term provability and controlled reuse
Sokolov Sergey Leonidovich
AI Helps — the person saves the decision
ARTIFICIAL INTELLIGENCE
AI
AI can not independently
Classify • retrieve details • look up contradictions • compare versions • offer route • prepare draft response
Sign • Approve • Change the source • Hiding the risk • Destroy the document • Making a legally significant decision
Each recommendation AI stores the model, version, input, time, confidence and decision of the person
Sokolov Sergey Leonidovich
30 / 100 / 365 days
PILOT
One complete interdepartmental process with solution, resource, execution and archive
0–30
101–180
301–365
DESIGN
PARALLEL MODE
INDEPENDENT EVALUATION
Process • Right • Role • Base Line
comparison • quality • load
stop • finish • scale
31–100
181–300
WORKING CONTOUR
EXPANSION
passport • statuses • signature • API
documents • proof • archive
The first scale is to prove the full cycle, not to connect the maximum number of users
Sokolov Sergey Leonidovich
KPI Test manageability, not activity
MEASUREMENT
100%
100%
Authoritative record is defined
completeness of mandatory metadata
Signatories are verified
The decision is related to the result.
≤30 sec
≤15 min
search for the current version
Full Decision File
Lost evidence
Unauthorized copies
Stop conditions: violation of law, security, integrity or archival provability
Sokolov Sergey Leonidovich
The first 100 days - ten mandatory results
DRAFT DECISION
Mandate and boundaries
Status map
Legal model
Classifier
Passport document
Status model
Trusted route
The Evidence Module
Archival model
Prototype and base line
Proposed action
Run 100- day design and 12A month-long pilot in one full interdepartmental process
Sokolov Sergey Leonidovich
Sources indicated in the presentation 12
- Author's concept "Perfect workflow", version 1.0, 27.08.2026.
- [/Sources]
- GOST R ISO 15489-1-2019 — https://protect.gost.ru/gost/details/2497916a-b91d-4248-a025-f898920fa001
- ISO 23081 — https://committee.iso.org/sites/tc46sc11/home/projects/published/iso-23081-metadata-for-records.html
- Federal Law No.63-FZ "On Electronic Signature" — https://pravo.gov.ru/proxy/ips/?docbody=&nd=102146610
- GOST R 7.0.101-2018 / ISO 30301 — https://protect.gost.ru/gost/details/a2fe605e-7c73-428b-b519-4fa57f633907
- GOST R ISO 30302-2022 — https://protect.gost.ru/gost/details/4bf6db6d-3ced-47f0-b982-436add643e86
- Federal Law No152-FZ — https://pravo.gov.ru/proxy/ips/?docbody=&nd=102108261
- Federal Law No187-FZ — https://publication.pravo.gov.ru/document/view/0001201707260023
- Rosarchiv, order No236 — https://www.archives.gov.ru/documents/prik236_2019.shtml
- Federal Law No125-FZ — https://pravo.gov.ru/proxy/ips/?docbody=&nd=102089692
- GOST R 7.0.97-2025 — https://protect.gost.ru/gost/details/360994e3-9a70-47b9-ab3a-cf21809e26ed



