Home / Knowledge / The ideal document flow of SUR

Primary document · 25–29 August 2026

Ideal Document Flow in SUR

A model of the flow of documents, decisions and responsibility within the development management system.

Image of document flow: related documents in a single space
The image of document flow: related documents in a single space. Artistic visualization; source documents are available below.

Brief annotation

About the document

A model of the flow of documents, decisions and responsibility within the development management system.

Presentation

Ideal_Document_Flow_SUR.pptx

Page — from —
Width

Downloading the document...

For viewing prepared PDF-copy of the presentation. PowerPoint animations and transitions are not played.

Scroll through the pages and change the scale on the viewbar.

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

ParameterValue
ObjectFull life cycle of management documents and related evidence
GoalOne-time creation of a reliable document and its repeated legal use without loss of context
Control unitAuthoritative record: content + Metadata + Authority + Version + Signature + Communications + status + storage life
ArchitectureFederated: the original is kept by the authorized owner; SES links identifiers, statuses and evidence
ResultFrom the decision you can go to the base, performer, resource, fact of execution, result and archival fate
BorderThe 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

  1. To approve the development of a target model of the ideal document flow as an outline of the Development Management System.
  2. Determine the state or corporate process of the pilot, the owner of the result and the list of participating information systems.
  3. Approve a single document passport, ID, classifier, status model and mandatory event log.
  4. Ensure legally significant signing through acceptable types of electronic signature and trusted infrastructure.
  5. Exclude creation of parallel originals: one authoritative record, controlled submissions and verifiable copies.
  6. Link the document to the decision, order, project, resource, execution, result indicator and storage period.
  7. 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.

PropertyPractical meaning
AuthenticityYou can prove the origin of the document, author, authority and method of signing
CredibilityThe content correctly reflects the operation, decision or event
IntegrityUnauthorized change detected, versions distinguishable
SuitabilityThe document can be found, opened, understood and used in an acceptable process
ContextRelations with the case, participants, grounds, decisions and events are maintained
TraceabilitySeen 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

PrincipleRule
One originalFor each legally significant state, one authoritative record is determined.
Default ContextDocument does not exist without cause, process, owner, reason and purpose
Authority before signatureChecks not only the certificate, but also the right of the person to make a specific decision
Version as eventEach change creates a new version with a base and author
EventivityThe route is described by an event log, not by moving copies
FederalityData remains with the owners; intersystem exchange is on standard passports
Minimizing accessAccess is issued by role, purpose, information class, phase and deadline
EvidenceExecution ends with confirmation of the result, not a change of status
Archive since creationTerm and archival fate are appointed at registration
ReversibilityCritical actions have stop conditions, rollback and standby mode

ARCHITECTURE

Seven Layers of Target Architecture

LayerPurposeResult
1. NormativePowers, regulations, standards, terms of storageLegal model of the document
2. SemanticClassifiers, ontology, 741, catalog 260Common language and address
3. DocumentalContents, props, versions, presentationsAuthoritative record
4. ProcessRoutes, roles, timelines, escalations, assignmentsControlled movement
5. TrustedIdentification, credentials, EP, time stampsProved will
6. EvidentiaryRelationship of decision, resource, execution and resultFull file
7. Archival and analyticalStorage, value examination, search, re-knowledgeInstitutional memory

LIFE CYCLE

Thirteen phases of the life cycle

CodePhaseBenchmark
D01NeedA task, event, or reason is recorded
D02ClassificationDetermine the type, case, mode, template and shelf life
D03Data collectionVerified sources and previous solutions are connected
D04PreparationA draft and passport of the document is created
D05Factual verificationCheck data, formulas, references and completeness
D06Law and safetyRules, powers, access and risks are checked
D07HarmonizationPositions, comments and resolution of disagreements are recorded
D08Approval and signatureThe expression of will is associated with a specific version
D09RegistrationAssign number, date, status and authoritative storage
D10AdvertiseRecipients receive a verifiable submission and commitment
D11ImplementationThe document is associated with actions, resources and deadlines
D12Acceptance and ValidationConfirmed performance and measurable result
D13Archive, destruction, re-knowledgeThe 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.

StateEntry conditionAllowed output
ProjectPassport and first version createdTo check or close
Under reviewAuditing and control issues are assignedFor finalization or approval
In agreementFacts, Law and Security PassedTo sign or resolve a dispute
ApprovedSignature valid, authorization confirmedFor registration
In effectRegistration completed and due to expireFor execution, modification or cancellation
ExecutedObligatory actions completedOn reception
VerifiedResults accepted and validatedTo archive or new cycle
Replaced / CancelledThere is a new decision or act of cancellationTo archive
ArchivalFinished office work, assigned storage modeValuation / Destruction

CLASSIFICATION

Document classes and control modes

ClassExamplesFeature
StrategicStrategy, doctrine, concept, programLong horizon and inter-documentary links
NormativeRegulation, regulation, standard, methodologyMonitoring relevance and scope
ManagingDecision, order, order, orderAuthority, addressees, time frame and control
ProjectPassport, plan, assignment, protocol, actLinkage to stage, resource and result
ContractualContract, agreement, additional agreementCommitments, counterparties, versions and signatures
FinancialEstimate, limit, account, payment basisAccounting, control and communication with SUR-810
Science and technologyReport, calculation, model, drawing, data setReproducibility and origin
EvidentiaryAcceptance certificate, test report, photo, measurementIndependence, time and reference to the criterion
CorrespondenceLetter, request, reply, appealRoute, timing and connection to the case
Archival complexesCase, Inventory, Electronic ContainerIntegrity of the composition and long-term preservation

CLASSIFICATION

Single ID and document address

ElementValue
SUR-DOCObject class — SUR document
B16Financial and investment balance management system
L10The resource and calculation model phase of KRISTALL741
S1Federal scale
2026Year of primary registration
000001Invariant ordinal identifier
V03Third 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.

GroupRequired fields
IdentificationCode, name, type, language, format, date of creation
ContextProcess, business, balance system, phase, scale, project
ResponsibilityAuthor, content owner, result owner, operator
RightBasis, authority, applicable rules, regime of information
VersionNumber, reason for change, author of change, date, status
HarmonizationRoute, participants, positions, comments, resolution of disagreements
Authorized officerEP view, certificate, time, inspection result, power
ConnectionsParent, applications, replaceable documents, decisions, instructions
ImplementationAddressee, action, time, resource, reference point
EvidenceActs, measurements, sources, validator, result
AccessClass, Roles, Purpose, Term, Copy Limitations
ArchiveNomenclature of the case, shelf life, countdown event, fate

GOVERNANCE

Powers and roles

RoleResponsibilityCan't.
InitiatorFormulates the need and expected resultIndependently approve outside the authority
AuthorCreates content and confirms sourcesHide the origin of borrowed data
Owner of ContentResponsible for relevance and correctnessDelete Version History
Lawyer / ComplianceChecks rights, risks and restrictionsSubstitute the owner of the management decision
AgreeingFixes position within competenceAgree for another participant
ApprovingMakes a decision and signs a specific versionDelegate signature without legal basis
RegistrarAssigns a number and records an authoritative recordChange the approved content
Person carrying out the workPerforms action and applies evidenceIndependently accept your own result
ValidatorIndependently checks the resultModifying Primary Evidence
ArchivistManages the case, time and archival fateExterminate 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.

  1. The system defines mandatory checks by type of document, risk and information mode.
  2. Each conciliator receives a list of questions of their competence, rather than a general request to “agree”.
  3. The comment contains the norm, the risk, the proposal of change and the degree of criticality.
  4. Parallel agreements are carried out simultaneously; dependent ones - only after the completion of the necessary predecessor.
  5. Disagreement is not hidden by a new copy: a formal decision on position and basis is created.
  6. The expired deadline causes an escalation to the process owner, but does not mean automatic consent for critical documents.

TRUST

Versions, changes and cancellations

OperationMandatory fixationResult
Black changeAuthor, time, modified fragmentsNew working version
Substantial revisionBase, comparative report, rechecksA new agreed version
Bug FixError description, influence, decision makerFixed version with original version
ExtensionLegal basis and new dateNew version of validity period
ReplacementLink to new document and termination dateThe previous document receives the status of "replaced"
CancelCancellation Act, grounds, date and consequencesStatus "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.

MonitoringQuestion to be checked
IdentityWho owns the key and was the certificate valid at the time of signing?
CredentialsDid the person have the right to sign exactly this type of document and the amount/perimeter?
VersionWhat exact set of bytes and applications were signed?
TimeWhen did the signing take place and what source confirmed the time?
IntegrityDid the document change after signing?
Long-term verificationAre the data required to verify the signature after the certificate expires?
IntroductionDoes 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.

EventMinimum composition
EstablishmentAuthor, source, template, original version, time
ChangePrevious version, new version, differences, base
View / UnloadSubject, role, purpose, object, time, channel
HarmonizationPosition, competence, comment, signature, time
ApprovalPerson, power, version, signature, trusted time
RegistrationNumber, system, registrar, authoritative repository
ImplementationAction, executor, resource, deadline, proof
VerificationMethod, validator, result, limitations
Archival ActionCase, 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.

CodeDocument FunctionExample
B01–B19Balance Management SystemB12 - water balance
L01–L13Management cycle phaseL09 - Legal Expertise and Security
S1–S3ScaleS2 - Regional / Interregional
DOCObject classDocument, application, proof, data set
VxxVersionV04 - The fourth substantial version

SUR INTEGRATION

Roles of the ecosystem

ComponentDocument roleWithdrawal
EQUILIBRIUMSources, models, scenarios and analytical findingsVerifiable basis of the decision
GASMPObservation events and early signalsPrimary Signal with Origin
SFERARegistration of initiatives and public feedbackInitiative card and route
KRISTALL741Classification of the document by system, phase and scaleCross address
ECO-PPAPassports, agreements and resource commitmentsExecutable project package
SPECZASHCHITAExecutive documents and primary evidenceFact of action
SUR-810Relationship of the document with the obligation and the ruble settlement eventCalculated footprint
ESG-IR 1.0Methodology, acceptance and independent validationConfirmed result

INFORMATION MODEL

Minimum set of registers

RegisterKey objects
DocumentsIdentifier, type, version, status, owner, storage
Cases and processesProcess, case, stage, relationships, timing
Participants and credentialsPerson, organization, role, power of attorney, limit
Classifiers741, 260, types of documents, modes, nomenclature of cases
RoutesChecks, approvals, signatures, escalation
Decisions and instructionsDecision, addressee, action, deadline, control
Projects and resourcesProject, commitment, limit, settlement status
EvidenceSource, method, criterion, result, validator
EventsAction, Subject, Object, Time, Basis, Result
Archival fateTerm, 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.

MonitoringRequirement
IdentificationConfirmed account and multi-factor authentication
AuthorizationMinimum authority over role and case
SegmentationSeparation of open, service, confidential and special contours
CopyControl of discharge, marking of submissions and watermarks as necessary
EncryptionProtection during transfer and storage by information class
JournalingUnchangeable access trail and critical actions
ReviewAutomatic termination of access when changing role, case or term
ResponseSignals, isolation, investigation, recovery and notifications

SAFETY

Personal data, privacy and critical infrastructure

CategoryProject requirement
Personal dataLegal basis, minimization, purpose of processing, localization when applicable, deadline and deletion
A trade secretList of information, regime, marking, accounting of persons and contractual obligations
Official informationDepartmental rules, restriction of distribution and registration of extradition
State secretsSeparate protected contour and compliance with the established mode
KIICategorization, safety requirements and interaction with the competent authorities, if applicable
Archival documentsMaintain access restrictions along with document and metadata

ARCHIVE

Archival fate begins at registration

  1. When classifying a document, it receives the position of the case nomenclature and a preliminary storage period.
  2. 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.
  3. The document is bundled with metadata, signatures, applications, and the necessary verification context.
  4. At the end of the process, an electronic case is formed with the control of completeness and integrity.
  5. The value examination determines permanent, long-term, temporary storage or destruction.
  6. Destruction is performed by act, after expiration of deadlines and removal of locks, with the event log.
  7. Knowledge that is no longer valid can be reused only with an explicit label of status and origin.

AUTOMATION

Artificial Intelligence in Document Management

AIAI should not be on its own
classify the document and propose a routeMaking a legally significant decision
extract details and check completenessSigning for an Authorized Person
find contradictions, duplicates and outdated linkshide uncertainty or source of output
compare versions and summarize commentsModify the approved version
propose related documents and precedentsExpand access to private data
control timing and generate early signalsAutomatically close critical order
prepare a draft dossier and archival inventorydetermine the archival fate without an authorized procedure

AUTOMATION

Automatic Routing Rules

SignalAutomatic action
No required propsReturn to author before start of approval
Invalid or outdated linkPrevention and appointment of factual verification
No confirmed authoritySignature Blocking
Changed content after approvalCancellation of dependent approvals
Critical disagreementTransfer to the owner of the process; prohibition of automatic approval
Expiration dateEscalation to the owner of the result and fixation of the deviation
The proof is not related to the criterionProhibition of closure of the order
Expires on storageStart examination; not automatic destruction
Infringed integritySite 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.

IndicatorModel thresholdMeaning
Authoritative record is defined100%No competing originals
Completeness of mandatory metadata≥99,5% [M]Document can be understood and verified
Confirmed powers of signatories100%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 orders0Stop-indicator
Unauthorized changes0Stop-indicator of integrity
Documents without archival fate0Managed Storage

IMPLEMENTING

Pilot: 30 / 100 / 365 days

TimeframeWorksGateway Result
0–30 daysProcess selection; map of systems; inventory of documents, credentials, signatures, archival requirementsBorders, owner and base line approved
31–100 daysSingle passport, ID, classifier, statuses, route, access model, prototypeGo / revise / stop for a working pilot
101–180 daysShadow mode: parallel comparison with the current process without changing the legal contourCompleteness and correctness confirmed
181–300 daysLimited working mode, trusted signature, execution register, evidenceStop conditions and KPI are met
301–365 daysArchival completion, stress test, recovery, independent evaluation and scaling packageDecision on termination, revision or scale

IMPLEMENTING

Road map to 2030

StageFocusResult
2026Methodology and legal modelPassport, classifier, rules of trust and pilot regulations
2027Limited pilotVerified chain of document, execution and archive
2028Intersystem compatibilityFederal Registers, API, common event dictionary
2029Scaling to portfoliosStandard routes for strategic and project documents
2030Managed Document Environment for SDSCross-linking goals, decisions, resources, results and memory

RISKS

Key risks and measures

RiskManifestationMeasure
Parallel originalsSome "final" versionsAuthoritative record and register of submissions
Formal digitalizationScan Instead of Managed RecordingPassport, Events and Structured Data
Signature without credentialsCertificate valid, decision invalidAutomatic role and limit testing
Excess approvalsDeceleration without quality gainMatrix of mandatory competencies
LeakageA single search reveals private informationFederal index and minimization of extradition
AI-hallucinationIncorrect fact or referenceOrigin, confidence and human verification
Dependence on supplierInability to migrateOpen export schemes and regular testing
The Archive GapSignature or format not verified years laterLong-term Validation and Migration
Substitution of resultStatus "executed" without effectAcceptance criteria and independent validation

DRAFT DECISION

Draft instruction

Proposed wording for further legal development:

  1. 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.
  2. Determine the owner of the result, operator, pilot object, participating bodies and information systems.
  3. Within a period of up to 100 days, develop a single document passport, identifier, classifier, status model, event log and archive fate rules.
  4. Ensure the use of electronic signature, verification of authority, integrity and trusted time in accordance with applicable requirements.
  5. Establish the principle of one authoritative record and prohibit the uncontrolled formation of parallel originals.
  6. Link the pilot’s documents with decisions, instructions, resources, execution, evidence, and measurable results.
  7. Conduct an independent legal, informational, archival and cybernetic assessment.
  8. 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

ResultAcceptance criterion
Mandate and boundariesThere is a customer, the owner of the result, the process and the list of systems
Map of current statusFixed documents, copies, routes, deadlines and problems
Legal modelQualified documents, signatures, data and archival requirements
ClassifierDefined types, 741-address, modes and nomenclature of cases
Passport documentMandatory metadata and quality rules approved
Status modelEvery transition has an event, conditions, role and prohibition
Trusted routeVerify version, signature, authority and time
Evidence-based modelThe document is related to the order, resource, action and result
Archival modelAppointed date, countdown event, case and completion procedure
Prototype and GatewayShown 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

TermDefinition
Authoritative recordDocument, which is given the status of an official and controlled copy by the established rules
DocumentInformation and related context created or received as evidence and business asset
IntroductionA human-readable or machine form of authoritative writing that does not create a new original
Passport documentStructured Metadata Set Required for Management and Verification
EventThe recorded action of a subject or system over a particular object
VersionCondition of detention resulting from controlled change
CredentialsConfirmed right of a person to perform a specific action within the specified limits
Trusted timeEvent time confirmed by an acceptable source and suitable for verification
Electronic caseA set of interrelated documents, metadata, and events of a single process or issue
Archival fateThe established term and procedure for storing, transferring or destroying the record
Evidentiary dossierLinked 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

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